[ntp:questions] Odd reachability with local clock on XP

David Woolley david at ex.djwhome.demon.invalid
Sat Oct 12 11:53:37 UTC 2013


On 10/10/13 00:28, Philip Prindeville wrote:

> *10.9.160.101    .GPS.            1 u   10   16  377    0.289   -0.112   0.016
>   127.127.1.0     .LOCL.          10 l  77m   16    0    0.000    0.000   0.000
>
> Not really sure why only the first packet gets through and no subsequent ones do.

Packets never get through to the local clock driver.  It is a fiction 
designed to meet a special purpose, a purpose that doesn't apply in your 
case.  As it, by definition, only ever replies with zero offset and zero 
delay there is no need for it to be actually polled to know the result.

That you get a reachability when it is actually being identified as the 
peer to downstream systems, will be an artifact of the internal way in 
which switching it on as the last resort system peer identity works.




More information about the questions mailing list