[replying to both emails] On Wed, Sep 09, 2015 at 12:11:29PM +0200, Joakim Hernberg wrote:
On Tue, 8 Sep 2015 14:14:31 -0600 Leonid Isaev <leonid.isaev@jila.colorado.edu> wrote:
I tried playing with cmdline options, without any success. ping from [core]/iputils 20140519.fad11dc-1 does work. Is this a bug or a feature, and does anyone know how to make ping work again?
You could create an ip6table firewall that just drops most things and leave ipv6 enabled in the kernel.
All networks on which I have Arch machines are IPv4-only. So I don't need IPv6...
--
Joakim
On Wed, Sep 09, 2015 at 01:49:34PM +0200, Jens Adam wrote:
Tue, 8 Sep 2015 14:14:31 -0600 Leonid Isaev <leonid.isaev@jila.colorado.edu>:
Is this a bug or a feature, and does anyone know how to make ping work again?
Have you tried 'ping -4'? Yes, it's undocumented.
Yep :( ---------- # ping -4 google.com ping: socket: Operation not permitted (raw socket required by specified options). # ping -N ipv4 google.com ping: socket: Operation not permitted (raw socket required by specified options). ---------- Thanks, -- Leonid Isaev GPG fingerprints: DA92 034D B4A8 EC51 7EA6 20DF 9291 EE8A 043C B8C4 C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D