Hello,
Noah Meyerhans wrote:
> Confirmed that this breaks ping when run without an explicit address
> family. This is actually already fixed upstream, but not in a tagged
> snapshot. It'll be fixed in the next upload, by cherry-picking that
> commit or syncing a new snapshot.
Control: tags -1 + upstream pending fixed-upstream
On Mon, Feb 29, 2016 at 09:02:02AM +0100, Florent Rougon wrote:
> Apart from that, I use:
>
> GRUB_CMDLINE_LINUX="init=/bin/systemd ipv6.disable=1"
Confirmed that this breaks ping when run without an explicit address
family. This is actually
Hello,
On Sun, 28 Feb 2016 22:38:05 + Jamie Heilman
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 ' works fine but
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.
> By "no ipv6 support", do you mean you're running a custom kernel with a
> different configuration than provided by Debian?
Correct.
--
Control: severity -1 important
On Sun, Feb 28, 2016 at 10:04:13PM +, Jamie Heilman wrote:
> root@cucamonga:~# ping 127.0.0.1
> ping: socket: Address family not supported by protocol (raw socket required
> by specified options).
>
> I actually can't ping anything at all, it all fails with
Package: iputils-ping
Version: 3:20150815-1
Severity: grave
root@cucamonga:~# ping 127.0.0.1
ping: socket: Address family not supported by protocol (raw socket required by
specified options).
I actually can't ping anything at all, it all fails with the above
error message.
I wouldn't be
6 matches
Mail list logo