On Tuesday 30 December 2008, David Rawling wrote:
> 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.
I'm still striking out. My conf file now looks like:
server ntp3.cs.wisc.edu #stratum 2
server ntp.sycharlutheran.org #stratum 2
server ntp1.sjbcom.com #stratum 2
server clock.nyc.he.net #stratum 1
#
driftfile /etc/ntp/drift
multicastclient # listen on default 224.0.1.1
broadcastdelay 0.008
Removed the localhost and fudge servers, and all the restrict lines. Running
the process in foreground and -d I'm seeing no obvious (to me) errors, lots
of lines like:
transmit: at 3065 216.160.0.218->76.254.87.122 mode 4
transmit: at 3095 216.160.0.218->173.16.32.174 mode 3
receive: at 3095 216.160.0.218<-173.16.32.174 mode 4 code 1 auth 0
clock_filter: n 8 off 102.806103 del 0.060678 dsp 0.001913 jit 4.235359, age 0
transmit: at 3098 216.160.0.218->209.51.161.238 mode 3
receive: at 3098 216.160.0.218<-209.51.161.238 mode 4 code 1 auth 0
clock_filter: n 8 off 102.850693 del 0.067199 dsp 0.001927 jit 4.205958, age 0
transmit: at 3102 216.160.0.218->128.105.37.11 mode 3
receive: at 3102 216.160.0.218<-128.105.37.11 mode 4 code 1 auth 0
clock_filter: n 8 off 102.907162 del 0.079884 dsp 0.001919 jit 4.258141, age 0
ntpq -pn
remote refid st t when poll reach delay offset jitter
==============================================================================
128.105.37.11 128.105.201.11 2 u 24 64 377 80.324 104815. 4263.40
173.16.32.174 99.150.184.201 2 u 31 64 377 58.081 104711. 4238.76
65.216.242.42 LOCAL(0) 14 u 19 64 377 240.709 104121. 4166.41
209.51.161.238 .CDMA. 1 u 30 64 377 68.340 104730. 4209.06
As I see the troubleshooting faqs, the reach column shows I'm getting
responses, but its never syncing after more than 1 hour, and the time
difference is now > 100 seconds and growing.
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
