I run Bert's wondershaper (see http://lartc.org) for several years now with the extra line:
# NTP (UDP protocol 17, port 123) tc filter add dev $DEV parent 1:0 prio 10 u32 match udp dst 123 0xffff match ip protocol 17 0xff flowid 1:10 >> Only thing I see is the high jitter (100+ ms) for external clocks; this >> is caused by the (partially!) used ADSL line (torrents). >> >> The firewall labels the NTP traffic as low latency etc. >> Would a wondershaper have any extra benefit? > > If you can somehow enforce QoS or prioritize NTP, that will help. > > I run bittorrent on my ADSL (often near the full capacity of the line) > with no ill effect on my scores, but I've also constructed my service > classes carefully. NTP takes priority over nearly everything else > (it's tied for 1st place with DNS) and has a guaranteed 10kbps > (roughly 3 queries+responses per sec). Next comes interactive ssh and > various chat protocols that I'd rather not have all laggy. After that > comes bulk traffic like web, ftp, mail, and ssh without > IPTOS_LOWDELAY. After all of that, any unclassified traffic, like > bittorrent. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
