Perhaps an idea, see http://lartc.org/wondershaper
I added the following 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 > On 04-06-08 18:28, Anthony DeRobertis wrote: >> On Wed, Jun 04, 2008 at 08:29:21AM -0700, Nelson Minar wrote: >>> If you're on an asymmetric link like ADSL there's only so much QoS your >>> router can do. In particular if your lodger is downloading lots of big >>> files via BitTorrent your incoming connection is going to be saturated >>> and your router can't usefully shape incoming traffic. > >> <snip> >> Data coming from the Internet, on the other hand, winds up queued when >> going from the fast 100+ m link to the slower 8m link—that is, on your >> ISP's router. Unfortunately, they do not properly prioritize it[1]. > > Queueing at the ISP is mostly for TCP traffic. You can shape TCP traffic > at > either side. You can shape your incoming bulk TCP traffic by limiting the > number of ACK packets you send back. If you send only one ACK packet back > per second, then (after an initial burst) you will only receive one > incoming > packet per second, which is only 1500byte/s (queued at the sender, waiting > for ACKs instead of queueing at your ISP). With a 8Mbit/s line, you can > handle 500+ packets of 1500 bytes per second, so limiting at 500 ACK/sec > will effectively prevent queueing at your ISP. > > Of course you can then prioritise the ACK packets based on source or > destination port to prioritise your incoming TCP-traffic. Works great on > my > ADSL :-) > > >> [1] Don't know why none of them have offered this service. "Keep web >> browsing fast, even during large downloads!". > > I _have_ fast web browsing (and good VoIP!), even during large downloads > ;-) _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
