Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 9 Mar 2024 10:37:46 +0100
From:      Andrea Venturoli <ml@netfence.it>
To:        Paul Procacci <pprocacci@gmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: ping acting strangely on 13.3
Message-ID:  <e8f736aa-b9ad-465f-8cac-2b21937d1acd@netfence.it>
In-Reply-To: <CAFbbPugzSeSsxPSv0OtA0P%2BRAwvFhXio1YUOKzNdxUizzQZdaw@mail.gmail.com>
References:  <c53ff6b9-6183-45a8-be61-f400f466c2d7@netfence.it> <CAFbbPugzSeSsxPSv0OtA0P%2BRAwvFhXio1YUOKzNdxUizzQZdaw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 3/9/24 04:17, Paul Procacci wrote:

> This is less likely a change to `ping` and more likely a change to the 
> resolver.
>  From ping(8):
> 
> "When invoked with a hostname, the version to which the target is resolved
>       first is used."

I tried following ping with gdb, but I guess I'll need to recompile it 
without optimizations and I'm out of time now.



> If you haven't already, set ipv6_activate_all_interfaces="NO"

Tried setting this and rebooted, but nothing chanegd.
Does it make sense without INET6 in the kernel?



> it makes sense 
> that if there's no transport for ipv6 available, it shouldn't provide 
> you with an answer that requires ipv6.

I opened bug 277592.


  bye & Thanks
	av.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e8f736aa-b9ad-465f-8cac-2b21937d1acd>