LARTC - Feb 2003 - interface level b/w capping using HTB

hi all

           the following is the setup i have done.

eth0    globals ip
eth1 internal ip 10.1.1.0/24  --->>>shd be capped to max 256Kbit
linux 8.0 with htb 3.6

tc qdisc add dev eth1 root handle 1:0 htb default 2
tc class add dev eth1 parent 1:0 classid 1:1 htb rate 250Kbit ceil 250Kbit
tc class add dev eth1 parent 1:1 classid 1:2 htb rate 128Kbit ceil 250Kbit

then i created leaves from 1:5 to 1:50 each getting 16Kbit and ceil 20Kbit
a range of 50 ipes
e.g. 
tc class add dev eth1 parent 1:2 classid 1:5 htb rate 16Kbit ceil 20Kbit
tc filter add dev eth1 parent 1:0 protocol ip pref 5 u32 match dst 10.1.1.5/32
flowid 1:5

like that....

although for sometime this setup works fine but suddenly it goes totally
unbouded.
i have gone thru the pages at docum.org and found out that if sum of child
calsses exceed parent rate then parent rate is not respected.

then what shd i do if i have to cap outgoing b/w on eth1 stricktly to 256Kbit
only.
hope to get an early response.


regds
hm

On Wednesday 05 February 2003 10:09, hm wrote:
> hi all
>
>            the following is the setup i have done.
>
> eth0    globals ip
> eth1 internal ip 10.1.1.0/24  --->>>shd be capped to max 256Kbit
> linux 8.0 with htb 3.6
Cool.  Linux 8.0.  Where can I download it?  I thought they are working on 
getting 2.5.x stable and now they already is 8.0 :)
> tc qdisc add dev eth1 root handle 1:0 htb default 2
> tc class add dev eth1 parent 1:0 classid 1:1 htb rate 250Kbit ceil 250Kbit
> tc class add dev eth1 parent 1:1 classid 1:2 htb rate 128Kbit ceil 250Kbit
Why rate = 158 Kbit ??
> then i created leaves from 1:5 to 1:50 each getting 16Kbit and ceil 20Kbit
> a range of 50 ipes
> e.g.
> tc class add dev eth1 parent 1:2 classid 1:5 htb rate 16Kbit ceil 20Kbit
> tc filter add dev eth1 parent 1:0 protocol ip pref 5 u32 match dst
> 10.1.1.5/32 flowid 1:5
>
> like that....
>
> although for sometime this setup works fine but suddenly it goes totally
> unbouded. i have gone thru the pages at docum.org and found out that if sum
> of child calsses exceed parent rate then parent rate is not respected.
>
> then what shd i do if i have to cap outgoing b/w on eth1 stricktly to
> 256Kbit only. hope to get an early response.
Solution is easy.  Make sure sum of child rates = parent rates.  
So if you have 45 classes (from 1:5 to 1:50) and a total rate of 256kbit, then 
use rate = 256kbit/45.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/