On 10/09/2020 13.15, Per Jessen wrote:
Carlos E. R. wrote:
On 10/09/2020 09.26, Per Jessen wrote:
I still find it interesting that I cannot reproduce the behaviour. Have you enabled more verbose logging or something like that?
No, I changed nothing.
Maybe you do not get in the default pool IPv6 addresses.
2.opensuse.pool.ntp.org - four IPv6 addresses.
office24:~ # host 2.opensuse.pool.ntp.org 2.opensuse.pool.ntp.org has address 195.186.1.101 2.opensuse.pool.ntp.org has address 62.202.141.23 2.opensuse.pool.ntp.org has address 162.159.200.123 2.opensuse.pool.ntp.org has address 193.33.30.39 2.opensuse.pool.ntp.org has IPv6 address 2001:470:b6d6:4::12 2.opensuse.pool.ntp.org has IPv6 address 2001:620:0:fffc::123:47 2.opensuse.pool.ntp.org has IPv6 address 2606:4700:f1::1 2.opensuse.pool.ntp.org has IPv6 address 2606:4700:f1::123
I have just switched my main laptop (Leap 15.2) to ipv4-only and chrony, same thing, no such messages. What does 'ip -6 route show' say on your machine, with ipv6 enabled? I would expect 2 entries, ::1 for loopback and fe80::/64 for eth0.
thinkpadE15:~ # ip -6 route show ::1 dev lo proto kernel metric 256 pref medium fe80::/64 dev wlan1 proto kernel metric 600 pref medium thinkpadE15:~ # But those are not routable. The laptop is neither switched for -4 or -6. It has whatever network manager decides based on the router given information, automatically.
Well, chrony does seem to handle the situation, but IMO it should not even try IPv6 as there is no routable IPv6 interface in the machine.
An application has to try it to find out, that's the point. Same for IPv4 for that matter.
thinkpadE15:~ # ping 2001:470:b6d6:4::12 connect: Network is unreachable thinkpadE15:~ # ping6 2001:470:b6d6:4::12 connect: Network is unreachable thinkpadE15:~ # Instant answer. No need to waste half an hour trying (chrony tries for half an hour). -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)