Stef Coene wrote:
On Thursday 07 August 2003 14:42, Steffen Moser wrote:
Here, you should specify the physical bandwidth of your underlaying
device (eth0), i.e. 100Mbit. You can't slow down the device at this
position.
The bandwidth parameter is used in the internal calculations of cbq and it
must be the real NIC bandwidth. It has nothing to do with the bandwidth you
want to manage on your link. So bandwidth paramter is 10 or 100 mbit.
How can I get the real NIC bandwidth for a particular interface through
a script or code....??
Altough you set a maximum rate of 500Kbit for the BE class, this class
borrowed additional bandwidth, of course, not from your EF class (which
is isolated), but from the parent qdisc, which offers 100Mbit (because
the underlaying device offers that much).
Be warned, isolated can break the cbq setup. I did some tests with cbq
classes and as long as you don't specify the isolated parameter eveything was
fine.
So, I've added one more class to your script - so my resulting script is:
I have 1 remark : the weight parameter. Take weight = rate / 10.
Stef
_______________________________________________
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
