On Friday 04 April 2003 02:45, lartc@xxxxx wrote: > Hello! > I read a post on LARTC mailing list ( > http://mailman.ds9a.nl/pipermail/lartc/2002q3/004827.html ) ...and I found > a script called "Games Script"! I need to know....what I have done wrong in > my scripts(see below) ! When the bandwith it's FULL (of downloads), > CounterStrike lag it's very very high(practically unplayable) > > [Counter Strike transfer its UDP on Destination Port 27015 and Source Port > 27005] Sorry for this huge e-mail but I want to know I've done wrog! I have some remarks on the script. First of all, you have to create 1 class (1:1) attached to the root qdisc with rate = ceil = $TOTAL like you did, BUT that's the only class you may attach to that root qdisc. In your script, you also have class 1:60, 1:70, 1:71 and 1:71 attached to it. An other remark is the different prio's you use for the classes. A class with a low prio has a low latency ONLY if you don't overlimit that class. So if you send more data in that class then the configure rate, you will get a very high latency. And don't you get any errors from the kernel about "quantum is too big"? You have to raise r2q to avoid these messages. You never said what your maximum bandwidth is. If this is 320 kbit for eth0, then you should make sure that you never send more data then your link can handle. So you better limit the traffic to 310 kbit or so. And also keep in mind that parent ceil is not respected. So if all you classes are sending as much as they can, they will send 50+50+50+50+50+240+80+80+240 and this is more then 320kbit. So you will overlimit your router. So the router will queue the packets in a big queue. And all traffic shaping you did is gone. The rest of the script itself is ok (I think). Stef -- stef.coene@xxxxxxxxx "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net
