Ryan Tucker wrote:
>Brian Foddy wrote:
>> restrict ntp3.cs.wisc.edu nomodify
>> restrict ntp.sycharlutheran.org nomodify
>> restrict clock.nyc.he.net nomodify
>
>I'm also not 100% sure, but I believe "nomodify" would cause the NTP
>daemon to not allow these peers to modify your clock, even if they are
>specifically listed as servers to poll.
I don't have specific restrict lines in my ntp.conf for the servers I
use, but I do have the following:
restrict -4 default kod notrap nomodify nopeer noquery
restrict -6 default kod notrap nomodify nopeer noquery
This would seem to impose the same (or worse) restrictions on the servers
I use, yet my time is working fine:
$ ntpq -pn
remote refid st t when poll reach delay offset jitter
==============================================================================
+202.60.94.11 128.250.36.3 2 u 32 64 377 24.366 2.052 21.450
-150.101.221.106 192.189.54.17 3 u 17 64 367 41.435 -9.189 0.772
+203.17.251.1 130.95.128.58 3 u 59 64 377 80.118 3.055 0.812
*203.23.237.200 128.250.36.2 2 u 13 64 377 25.366 0.461 0.518
(Hmm, poll of 64? That server's been up for 122 days ...)
Dave.
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
