On Sun, May 28, 2006 at 12:11:10AM +0200, Stefano Mainardi wrote:
> >> If B don't make traffic, 7/8 of 20Mb/s must be assigned to A and all the
> >> rest at B
>
> Sorry, "all the rest at A" :)
So, in other words, A is allowed to take bandwidth from B.
B and C stick to their bandwidth limits.
A tree like this could probably accomplish this:
HTB qdisc
|
\--- HTB root class (100mbit)
|
\--- HTB class (90mbit|90mbit)
| |
| \--- HTB class A (70mbit|90mbit)
| \--- HTB class B (20mbit|20mbit)
|
\--- HTB class C (10mbit|10mbit)
This way, C and B never borrow any bandwidth (as they have rate==ceil),
and if A borrows, it will be from B, as the parent class (which has
rate==ceil as well) will never borrow from C.
> We have tested this script with CEIL=RATE, and CEIL=100Mbit, but i view that
> the data-rate calculated for each PC is not proportional to the traffic
> assigned at Firewall.
HTB expects to be able to use the full specified rate at any point
of time, so you probably should use something lower than 100mbit
as a base value. Even in 100mbit networks, you never actually get
this rate, due to overhead, collisions, etc.
Other than that, are there really just these three classes of traffic
going out on eth1? The setup should work, as long as the classification
is working properly.
Regards
Andreas Klauer
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
