[ntpwg] Testing NTP performance

[Steve Kostecke]

"Greg Dowd" said:

>I have also tested the standard performance of linux clients running
>ntpd against our servers.  In that case, one great way is to plug a gps
>receiver into the slave, with appropriate refclock, and run the query
>against the server notrust.

Depending on what version of the NTP Reference Implementation you are
using that may not work the way you think it will.

The behavior of notrust changed between versions 4.1 and 4.2.

* In 4.1 (and earlier) notrust meant "Don't trust this host/subnet for
  time".

* In 4.2 (and later) notrust means "Ignore all NTP packets that are not
  cryptographically authenticated." This forces remote time servers to
  authenticate themselves to your (client) ntpd.

For NTP 4.2.x (and later) use 'noselect' instead of 'notrust' if you
just want to log statistics from a remote time server.

-- 
Steve Kostecke <kostecke at ntp.org>
NTP Public Services Project http://support.ntp.org/
Public Key at http://support.ntp.org/Users/SteveKostecke