> TC_UPLINK_RATE="100" > TC_RATE[0]=50 > TC_CEIL[0]=110 So this class has ceil = 110kbit, but the parent class has ceil = 100kbit. The parent ceil is not respected so this class can use 110kbit if it wants. I don't think this is what you want.
> TC_RATE[1]=15 > TC_CEIL[1]=60 > TC_RATE[2]=10 > TC_CEIL[2]=60 > TC_RATE[3]=5 > TC_CEIL[3]=30 There is also a drawbeck if you use prio to improve latency. Devik did some testing. A lower prio is good for delays IF the class with the lower prio never sends more then it's rate (so it's never overlimited). If it do so, other classes are served first and the delays will be very bad. I haven't test it myself, but you can find it in the user guide of htb chapter 7 (http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm#prio). You can force a class to never exceeds its rate if you use a policer in the filter so packets that exceeds the rate are dropped by the filter. But again, I haven't test it. Stef -- [EMAIL PROTECTED] "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net _______________________________________________ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
