>Number:         17899
>Category:       bin
>Synopsis:       ntpd says connection re-estabished, even if server is unreachable
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri Aug 09 11:56:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     dive
>Release:        NetBSD 1.6E
>Organization:
>Environment:
System: NetBSD eros.endersgame.net 1.6E NetBSD 1.6E (EROS) #361: Wed Aug 7 14:43:33 EDT 2002 dive@eros.endersgame.net:/disk2/a/cvs/netbsd/current/src/sys/arch/i386/compile/EROS i386
Architecture: i386
Machine: i386
>Description:
ntpd will say that a connection has been re-established, even if the ntp
server it is trying to contact is not currently reachable.
For example, I run ntpd on a machine here, and my cable modem was out for
twelve hours. many times during this period, ntpd told me:
Aug  9 10:17:53 eros ntpd[251]: Connection re-established to 192.5.41.40
Aug  9 10:20:31 eros ntpd[251]: Connection re-established to 192.5.41.41
Aug  9 10:22:44 eros ntpd[251]: Connection re-established to 137.78.160.48
Aug  9 10:34:58 eros ntpd[251]: sendto(192.5.41.40): No route to host
Aug  9 10:37:35 eros ntpd[251]: sendto(192.5.41.41): No route to host
Aug  9 10:39:50 eros ntpd[251]: sendto(137.78.160.48): No route to host

Thus, it tells me re-established, even when it is no such thing.
>How-To-Repeat:
Run ntpd, set it up to contact a server somewhere, then remove all
connectivity to that server and wait for it to try and sync.
>Fix:
ntpd should not say re-established if it has not actually done so.
"Attempting to re-establish connection" or something of the like would be
better.
>Release-Note:
>Audit-Trail:
>Unformatted: