On Mon, Mar 06, 2006 at 10:53:13AM +1000, Russell Stuart wrote: > I can verify it doesn't. I have implemented this in real > life, and the class is limited to the "rate". Thanks for pointing it out. > The revised class structure is now: > > htb class parent 1: classid 1:10 rate 80% ceil 100% > htb class parent 1:10 classid 1:11 rate 100% ceil 100% > htb class parent 1:11 classid 1:19 rate 30% ceil 100% prio 0 [VOIP leaf] > htb class parent 1:10 classid 1:20 rate 70% ceil 100% > htb class parent 1:20 classid 1:21 rate 20% ceil 100% prio 1 [interactive leaf] > htb class parent 1:20 classid 1:22 rate 50% ceil 100% prio 2 [other leaf] Interesting analysis, although it kind of defies my HTB logic (which is just an inaccurate model). If the 1:10 class is limited to the rate as you said above (which would be 80%), how can a child class have a rate of 100%? I still don't understand what to make of a root class with different rate / ceil settings. It's either limited to rate, or to ceil all the time; if it isn't, it decides to jump over it's rate under which circumstances? Regards Andreas Klauer _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
