Date: Tue, 10 May 2016 09:30:33 -0700 From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp> To: Dmitry Sivachenko <trtrmitya@gmail.com> Cc: FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: ping6: failed to get receiving hop limit Message-ID: <CAJE_bqfUhDatoQYjSBtBoWbuYaDDQE0sQhFt%2BHxMDrEepK_%2BOA@mail.gmail.com> In-Reply-To: <D46419B0-C9A1-4B16-8A4B-75E9CD69B4F3@gmail.com> References: <D46419B0-C9A1-4B16-8A4B-75E9CD69B4F3@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At Tue, 10 May 2016 10:26:59 +0300, Dmitry Sivachenko <trtrmitya@gmail.com> wrote: > Sometimes ping6 command writes the following warning to stderr: > > ping6: failed to get receiving hop limit > > I can easily reproduce this with > for n in `jot - 1 1000` ; do /sbin/ping6 -n -c 5 $HOST > /dev/null ; done > > It is very likely that even 100 repetitions is enough to catch this. > > Other than this warning IPv6 network seems to work properly. > > What does it mean? That should mean the IPV6_RECVHOPLIMIT socket option somehow didn't work as expected: the kernel didn't provide the information in the ancillary data chain. I have no idea about how this could happen - it's quite likely to be some kind of kernel bug, but I have no specific idea. -- JINMEI, Tatuya
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJE_bqfUhDatoQYjSBtBoWbuYaDDQE0sQhFt%2BHxMDrEepK_%2BOA>