"Michael B Allen" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] [...] > # ntpq -p > s0.foo.net: timed out, nothing received > ***Request timed out > > No response.
NTP is not running. > I reduced the ntp.conf to: > > # cat ntp.conf > server 192.168.2.15 > driftfile /var/lib/ntp/drift > > and get a response now but of course I don't know what association IDs > are or if I need them: > > # ntpq -p > No association ID's returned NTP is running, but it's not getting time from anywhere. > # ntpq -p 192.168.2.15 > remote refid st t when poll reach delay offset > ====================================================================== > *felix.headdown. 62.119.40.98 2 u 807 1024 377 120.066 0.864 > +petrel.telecom. 192.36.143.150 2 u 737 1024 377 142.054 2.234 > +ohno.mrbill.net 192.43.244.18 2 u 708 1024 377 60.775 -1.755 > LOCAL(0) LOCAL(0) 10 l 4 64 377 0.000 0.000 (Jitter column removed to prevent wrapping.) Looks good. Three servers, all three credible (*/+), all three ramped up to maxpoll (1024), no samples missed the last 8 times around (377 octal), delay is lousy but the offsets are low. Excellent. Pool servers? It's working *good*. You, on the other hand, have Problems. With the cut down config file, at least NTP is now starting, but you're not getting any traffic even without the restrictions. Review your firewall again, this time under the assumption that you do have one. Groetjes, Maarten Wiltink _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
