Steve Herber wrote:
I notice this with my DSL line. Normally I have a score of 20 but
randomly the test fails and I get hit with a penality:
http://www.pool.ntp.org/scores/216.39.145.27
www.pool.ntp.org is currently down, so I can't check, but with my own
server there are fails as well.
I think there is occasional packet loss between the probing server and
my system, and probably not on my own link, that causes those "no
response" hits.
It is not very likely that something can be done about it (other than
coding some simple re-try algorithm in the probing server so that single
packet losses are not always blamed on the server being probed)
The solution should be to add traffic shaping to my Linux firewall.
That is one of those projects that I haven't finished yet.
Does anyone have Shorewall configuration files for NTP traffic shaping?
There is no real need for specific handling of NTP (although you could
assign NTP packets a high priority), what is most important is to limit
the upstream bandwidth of the entire link to a value that is slightly
less than you real upstream rate, so that no queue forms inside your modem.
Note that many ADSL providers quote the raw ATM rate instead of the
effective IP rate, so 10-15% should be subtracted.
I have no experience with Shorewall, only with the wellknown
"wondershaper" script for generic Linux boxes. It works quite well.
Rob
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
