[ntp:questions] Re: maxpoll >=14 causes other clients to reject server

Richard B. Gilbert rgilbert88 at comcast.net
Sun Mar 12 20:05:17 UTC 2006


David D. Hagood wrote:
> I have an NTP server at my firewall, synced to various sources on the 
> Internet. Being a good netizen I want to poll those servers no more than 
> needed, so I set the maxpoll high so that once my server is synced, it 
> should poll its sources very infrequently.
> 
> However, if I set maxpoll to 14 or more, then my computers on the inside 
> will occasionally reject the firewall server as not being synced because 
> it has not synced recently enough.
> 
> I am assuming the firewall server is reporting that it hasn't synced 
> recently enough, and that is why the clients are rejecting it. Fair 
> enough, but then shouldn't the server go sync again, even though it has 
> not reached the maxpoll interval? Alternatively, should not the server 
> just say "I'm OK, I have synced within my programmed time, all is well"? 
> Or lastly, shouldn't the server say "maxpoll >=14 is not valid"?
> 
> All machines in this discussion are Fedora Core machines running 
> ntp-4.2.0a.
> 
> _______________________________________________
> questions mailing list
> questions at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/questions
> 

I think you have carried good netizenship to an extreme! The clients 
polling at MAXPOLL=10=2^10=1024 seconds are not the ones killing the 
servers; it's the clients polling once per second that cause the 
problems.  If you know anyone who's doing that, kindly cut his throat 
and call it a mercy killing!  Some Netgear routers do this; use a sledge 
hammer and call it mercy killing.




More information about the questions mailing list