[ntp:questions] nptq -p slowness

Danny Mayer mayer at ntp.isc.org
Thu Feb 8 12:57:20 UTC 2007

mills at udel.edu wrote:
> Danny,
> I don't understand your problem. The reference ID for the server is 
> unambiguous.

My problem is that this is not really true or rather that the same
machine can have multiple refid's none of which may be an IPv4 address.
A reference ID may be unique (outside of refclocks which won't be) but
since each machine can have multiple refid's you end up with a situation
where you are not detecting loops which is contrary to the design goal
of refids. We would be far better off having each machine have exactly
one refid. Unfortunately that may not be simple to implement.

 As specified, it is the refetence ID of the reference clock
> (stratum 1) or source (remote) address/hash of the system peer (stratum 
>  > 1), however that is determined. It has nothing to do with the 
> destination (local) address, whichever NIC is involved. You might be 
> concerned about which local address to use as a client, but that is not 
> an NTP issue. That's why the Autokey is so picky about knowing which one 
> to use before launching the first packet.

It's not picking which is the local address to use that I'm concerned
about but that there's more than one to choose from in the first place.


More information about the questions mailing list