On 3/2/14, 5:25 AM, Rob Janssen wrote:
It seems to me the monitor would never receive stratum 16, but Ask
wrote it does...
It could be that the server being used is not the reference ntpd and
behaves a bit different than
ntpd does.
Since it was my server that started the thread, I can confirm that this
is *not* a stock ntpd. It is entirely custom code running on an embedded
system dedicated to time serving. I had missed the Stratum 16 -> value 0
mapping in the spec and will fix that.
I took a look at the ntpdate code and (I think) it suffers from the 16 /
0 confusion where it checks the validity of the inbound packet. Later
on, it gets the checks correct, but I think that it will try and sync to
a server which reports 0 in the stratum field.
It does appear to get the leap bits checking right.... I will ensure
that incorrect time also causes the leap = 3 condition.
Philip
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
