Your message dated Sat, 29 Jul 2006 22:04:14 +0200
with message-id <[EMAIL PROTECTED]>
and subject line ntp IPv6 support fixed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: ntp-server
Version: 1:4.2.0a+stable-8
Severity: important
ntpd segfaults when using specific servers, e.g. chime5.surfnet.nl. I
suspect that it is caused by some ipv6 problem.
chime5.surfnet.nl has both an ipv4 and ipv6 address:
[EMAIL PROTECTED]> host chime5.surfnet.nl
chime5.surfnet.nl has address 194.171.167.130
chime5.surfnet.nl has IPv6 address 2001:610:1:400a:194:171:167:130
My machine doesn't have an ipv6 link, but it does have ipv6 support in
the kernel (as a module actually, but it is automatically loaded by
ifupdown or something).
The problem disappears if I manually put the ipv4 address in /etc/hosts
An strace of ntpd shows that it connect to my DNS and get the address
of chime5.surfnet.nl, and tries to connect over ipv6.
After that, ntpd reads /etc/services a few times and segfaults. (full
strace log is attached)
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-ac6
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages ntp-server depends on:
ii ntp 1:4.2.0a+stable-8 Network Time Protocol: network uti
ii ntp-simple 1:4.2.0a+stable-8 Network Time Protocol: daemon for
-- no debconf information
ntp.trace.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 1:4.2.2+dfsg-1
Crashes caused by lack of IPv6 support in some part of the system have
been addressed in 4.2.2, which should take care of this bug.
--- End Message ---
