Date: Wed, 11 Sep 2019 09:56:56 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Pierre Dupond <76nemo76@gmx.ch> Cc: Matthew Seaman <matthew@FreeBSD.org>, freebsd-questions@freebsd.org Subject: Re: ping6 www.freebsd.org hangs Message-ID: <44blvrhr6f.fsf@be-well.ilk.org> In-Reply-To: <20190911122523.9b94cd45533279bf46592e94@gmx.ch> (Pierre Dupond's message of "Wed, 11 Sep 2019 12:25:23 %2B0200") References: <20190906192931.d5735e1602f98d6b9a2906c0@gmx.ch> <b710de87-756e-6e6f-654c-aa41e84b36e0@FreeBSD.org> <20190911122523.9b94cd45533279bf46592e94@gmx.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
Pierre Dupond <76nemo76@gmx.ch> writes: > Thanks for the tip. Finally I was able to reproduce the > problem (which arise from time to time). > > The ping6 command failed either with the IPv6 address (or > the name). The result is the same for an other address (like google) > but at the same time I can reach these address from other machines. > > It is also possible to reach (with ping6) the external router of my organisation > (passing few intermediate routers). > > What is curious however is that the command "traceroute6" succeed > and then the command "ping6" works again. > > It sounds like a strange fragmentation problem. By default traceroute uses UDP and ping uses ICMP. Could be a stateful firewall somewhere. You could test that by using ICMP with traceroute if it happens again.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44blvrhr6f.fsf>