[ntpwg] Testing NTP performance

[Greg Dowd]

You're absolutely correct.  I'm showing my ntp age :-)

  
Greg Dowd
gdowd at symmetricom dot com (antispam format)
Symmetricom, Inc.
www.symmetricom.com
"Everything should be made as simple as possible, but no simpler" Albert
Einstein
 

> -----Original Message-----
> From: ntpwg-bounces+gdowd=symmetricom.com at lists.ntp.org 
> [mailto:ntpwg-bounces+gdowd=symmetricom.com at lists.ntp.org] On 
> Behalf Of Steve Kostecke
> Sent: Friday, May 02, 2008 8:58 AM
> To: ntpwg at lists.ntp.org
> Subject: Re: [ntpwg] Testing NTP performance
> 
> "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
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.org
> https://lists.ntp.org/mailman/listinfo/ntpwg
>