Hello,
On Sun, 28 Feb 2016 22:38:05 +0000 Jamie Heilman <ja...@audible.transient.net>
wrote:
> Noah Meyerhans wrote:
> > I cannot reproduce this on a host with no ipv6 connectivity. Does
> > 'ping -4 127.0.0.1' work any differently?
>
> Yeah, that works.
Same here. 'ping -4 <ipv4_address>' works fine but 'ping <ipv4_address>'
doesn't (I tried with 127.0.0.1, with the address of a local Ethernet
interface, with the address of a host I can ssh to on the local
network...).
> > By "no ipv6 support", do you mean you're running a custom kernel with a
> > different configuration than provided by Debian?
For me, the kernel is that from linux-image-4.4.0-1-amd64 version
4.4.2-3 (recently updated from unstable), rebuilt with one tiny patch
that is not network-related in any way, and which I have been using
since June 2015 without any problem: it is just reverting upstream Linux
kernel commit 79346d620e9de87912de73337f6df8b7f9a46888 ("HID: input:
force generic axis to be mapped to their user space axis"; I
unfortunately have to apply this patch to every kernel release since
then, because nobody bothered to even answer bug #785606 despite my
'git bisect'ing it).
Apart from that, I use:
GRUB_CMDLINE_LINUX="init=/bin/systemd ipv6.disable=1"
in /etc/default/grub, which effectively disables IPv6, AFAICT.
My aptitude.log shows:
[UPGRADE] iputils-ping:amd64 3:20121221-5+b2 -> 3:20150815-1
on Fri, Feb 26 2016 20:48:43 +0100, and I only noticed the problem
today.
Thanks for considering!
--
Florent
