[ntp:questions] Re: refid on client differs from refid on local server
David L. Mills
mills at udel.edu
Sat Dec 17 17:48:06 UTC 2005
The ntpq already does display one of the "other" types, in particular if
a reference clock or kiss code is involved. This was a recent change to
avoid the misleading IP address for reference clocks operated at an
elevated stratum. Note that in orphan mode the refid displayed is the
loopback address, but this is entirely legit.
Danny Mayer wrote:
> David L. Mills wrote:
>>I'm not aware of any mission calculated to "change my mind," much less
>>whether to attempt DNS deconstruction of the refid field, on which I
>>have no opinion. If the reference stratum is 0 or 16 or a reference
>>clock, the refid is reported as a string, otherwise the opaque value.
>>What ntpq or ntpdc does with that is opaque to me, but they would have
>>to figure out which to print based on the same criteria.
>>The common problem occurs when running a reference clock driver at
>>elevated stratum, in which case the refid used to look like a mangled IP
>>address, but now reveals the clock type instead. This should have
>>nothing to do with DNS. Is this what you meant by "change my mind?"
> Sorry, I should have explained what I meant. I want to change the
> display of the refid so it doesn't look like an IP address when it's not
> one of the "other" types like a refclock. The refid is not an IP
> address, but an identifier of some kind.
> questions mailing list
> questions at lists.ntp.isc.org
More information about the questions