From mboxrd@z Thu Jan 1 00:00:00 1970 From: "hm" Date: Wed, 05 Feb 2003 09:21:31 +0000 Subject: [LARTC] interface level b/w capping using HTB MIME-Version: 1 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0036_01C2CD24.64F50090" Message-Id: List-Id: To: lartc@vger.kernel.org This is a multi-part message in MIME format. ------=_NextPart_000_0036_01C2CD24.64F50090 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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.=20 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 ------=_NextPart_000_0036_01C2CD24.64F50090 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

hi all

= the=20 following is the setup i have done.

eth0 globals = ip

eth1 internal ip 10.1.1.0/24 =20 --->>>shd be capped to max 256Kbit

linux 8.0 with htb 3.6

tc qdisc add dev eth1 root handle 1:0 = htb default=20 2

tc class add dev eth1 parent 1:0 = classid 1:1 htb=20 rate 250Kbit ceil 250Kbit

tc class add dev eth1 parent 1:1 = classid 1:2 htb=20 rate 128Kbit ceil 250Kbit

then i created leaves from 1:5 to 1:50 = each getting=20 16Kbit and ceil 20Kbit

a range of 50 ipes

e.g.

tc class add dev eth1 parent 1:2 = classid 1:5 htb=20 rate 16Kbit ceil 20Kbit

tc filter add dev eth1 parent 1:0 = protocol ip pref=20 5 u32 match dst 10.1.1.5/32 flowid 1:5

like that....

although for sometime this setup works = fine but=20 suddenly it goes totally unbouded.

i have gone thru the pages at docum.org = and found=20 out that if sum of child calsses exceed parent rate then parent rate is = not=20 respected.

then what shd i do if i have to cap = outgoing b/w on=20 eth1 stricktly to 256Kbit only.

hope to get an early = response.

regds

------=_NextPart_000_0036_01C2CD24.64F50090-- _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/