"Richard B. Gilbert" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Nick Bright wrote:
>> ntpq> pe >> remote refid st t when poll reach delay offset >> ================================================================= >> 217.160.254.116 0.0.0.0 16 u - 128 0 0.000 0.000 >> 75.144.70.35 0.0.0.0 16 u - 128 0 0.000 0.000 >> 72.232.254.202 0.0.0.0 16 u - 128 0 0.000 0.000 >> 208.75.88.4 0.0.0.0 16 u - 128 0 0.000 0.000 [...] > Assuming that you waited at least 30 minutes before printing that > ntpq "banner", the servers you have configured are unreachable. Poll interval is at 128. It's been trying for some time, and already backing off. > [...] AFAIK there is no good reason to block port 123. Your paranoia is slipping. The default state is closed, then if somebody comes asking you open a port... maybe. My firewall has a port 123 hole for the secondary server _only_ (which doesn't even use it, incidentally). The other hosts can get time from the firewall and its slave. I'm certainly not letting through NTP traffic for them. Groetjes, Maarten Wiltink _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
