Package: openntpd Version: 3.6.1p1-2 Severity: normal I have a system with a dynamic IP address (PPPoE ADSL line; once in every 24 hours my ISP drops the connection and then gives me a different IP address when reconnection - a usual practice these days).
I found that after the IP address of the system is reconfigured, openntpd still keeps using the old local IP address when sending out UDP packets, which ends up in tons of EINVALs in sendto(). (This is not openntpd's fault, it is just a feature of UDP sockets that the local address is set at connect().) Because of the wrong local socket addresses, openntpd cannot send any packets, thus it stops keeping the time accurate (and the clock slowly drifts away - this was how I found the bug). Since dynamic IP addresses are rather widespread, it will cause trouble for many. The perfect solution would be to fix openntpd source to have it clear the local socket addresses (using connect() again) when EINVAL is encountered with sendto(). I haven't checked whether the problem is still present in testing. BTW, the comment received for #330587 at Wed, 1 Mar 2006 09:13:25 -0500 seems to be the same or similar problem. norbi -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.16 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages openntpd depends on: ii adduser 3.63 Add and remove users and groups ii libc6 2.3.2.ds1-22sarge4 GNU C Library: Shared libraries an ii libssl0.9.7 0.9.7e-3sarge4 SSL shared libraries -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
