From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] interface level b/w capping using HTB
Date: Wed, 05 Feb 2003 21:17:50 +0000 [thread overview]
Message-ID: <marc-lartc-104454825430537@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104443615622000@msgid-missing>
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/
prev parent reply other threads:[~2003-02-05 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 9:21 [LARTC] interface level b/w capping using HTB hm
2003-02-05 21:17 ` Stef Coene [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-104454825430537@msgid-missing \
--to=stef.coene@docum.org \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox