Danny Mayer wrote:
I've spent a lot of time debugging this stuff. The fact is that if a
server is not reachable in the first place it won't show up in the
scoreboard and there is no association created. A refid of 0.0.0.0
doesn't mean a lot since we don't know what kind of ntp is responding to
the requests. Other implementations may not even set the refid. We don't
know since that not a piece of information we've been given.
At least through 4.2.0a, as long as a configured server has an address it
will show up on the billboard whether it's reachable or not. The only thing
that keeps it off is a name that doesn't resolve. I really wouldn't want to
see it any other way. Otherwise, if your server happens to be down when you
start, it will never be used.
Depending on the version of ntpd, a server that has not yet been reached
will show one of the following (which is, I think, indistinguishable from
a server that is reachable but that has never been synchronized since
the client ntpd started):
4.2.0a on WinXP:
unreachable .STEP. 16 u - 128 0 0.000 0.000 4000.00
[There IS a bug here, because that server is now reachable AND synchronized.
It wasn't when ntpd started.]
4.2.0 on Tru64
unreachable .INIT. 16 u - 1024 0 0.000 0.000 4000.00
4.1.2 on Linux
unreachable 0.0.0.0 16 u - 1024 0 0.000 0.000 4000.00
3.5f on HP-UX
unreachable 0.0.0.0 16 - - 64 0 0.000 0.000 16000.0
3-5.93e on Solaris
unreachable 0.0.0.0 16 - - 1024 0 0.000 0.000 16000.0
-Tom
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
