retitle 293793 ntpdate tries IPv6 even when not available -- [4.2.1]
retitle 294636 ntpdate tries IPv6 even when not available -- [4.2.1]
severity 293793 important
merge 293793 294636
tags 293793 = fixed-upstream patch ipv6 upstream
thanks
Hi,
On sam, fév 05, 2005, Rémi Denis-Courmont wro
forwarded 293793 http://bugzilla.ntp.org/show_bug.cgi?id=389
thanks
Hi,
On jeu, fév 17, 2005, Rémi Denis-Courmont wrote:
> Below is a patch for this problem. It should fix bug #294636 as well.
I'm Cc:ing the submitter of #294636. Eduard Bloch, could you please
test if Rémi's patch in
tags 285316 + patch upstream ipv6 important
thank
Below is a patch for this problem. It should fix bug #294636 as well.
It might be a good idea to forward it upstream.
--
Rémi Denis-Courmont
http://www.simphalempin.com/home/
diff -ru ntp-4.2.0a+stable.orig/ntpdate/ntpdate.c ntp-4.2.0a+stable/nt
In fact, it looks like ntpdate fails if IPv6 is not compiled in the
kernel/if the IPv6 module is disabled.
That makes the program completely unusable with any NTP server which
advertise any IPv6 address from IPv4-only client. It assumes that a
server has only one address. It seem fairly complex
Package: ntpdate
Version: 1:4.2.0a+stable-2
Severity: normal
ntpdate fails to query a NTP server when the server's hostname resolves
to both IPv6 and IPv4 addresses, if the client has ipv6 kernel module
loaded but no IPv6 connectivity.
As specified per RFC 2553, it should fallback to using IPv4
5 matches
Mail list logo
