Hi-- On Apr 23, 2010, at 4:16 PM, Philipp Winkler wrote: > I just modified the config file and restarted the ntpd on ntp.ia21.de. > > Currently my settings are: > restrict -4 default kod notrap nomodify > restrict -6 default kod notrap nomodify > > Is this okay and safe?
The only change I might make is to add "nopeer", but I have yet to hear of anyone actually doing something malicious to ntpd in terms of forging time, although I suppose the possibility exists. Here's what I'm seeing now: # ntpq -c rv -p ntp.ia21.de assID=0 status=0674 leap_none, sync_ntp, 7 events, event_peer/strat_chg, version="ntpd [email protected] Fri Dec 4 19:16:58 UTC 2009 (1)", processor="x86_64", system="Linux/2.6.24-27-xen", leap=00, stratum=2, precision=-8, rootdelay=15.011, rootdispersion=17.975, peer=49526, refid=192.53.103.104, reftime=cf7caa9a.9e89905d Fri, Apr 23 2010 19:24:10.619, poll=7, clock=cf7caaf6.b1a70a81 Fri, Apr 23 2010 19:25:42.693, state=4, offset=6.208, frequency=88.858, jitter=4.115, noise=4.414, stability=0.022, tai=0 remote refid st t when poll reach delay offset jitter ============================================================================== +ntp1.rrze.uni-e .DCFp. 1 u 29 128 377 23.699 4.582 3.906 xalarich.online- 192.53.103.108 2 u 33 128 377 192.288 33.204 67.813 *ptbtime2.ptb.de .PTB. 1 u 93 128 377 15.011 6.636 3.906 +ntp2.rrze.uni-e .PPS. 1 u 32 128 377 24.258 6.299 4.531 -timekeeper.isi. .GPS. 1 u 91 128 177 175.231 11.817 7.704 +clock.via.net .GPS. 1 u 96 128 377 161.028 4.291 4.511 -rrcs-64-183-56- .GPS. 1 u 31 128 377 174.476 1.074 3.906 You're seeing quite high delays in reaching many of the timeservers you are talking to. Try to pick some timeservers closer to your box, preferably with delays of less than 50 ms. alarich.online has a high offset and lower stratum, it's being rejected as a falseticker.... Regards, -- -Chuck _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
