From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb problem
Date: Mon, 28 Jul 2003 17:49:05 +0000 [thread overview]
Message-ID: <marc-lartc-105941490514168@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100803866815679@msgid-missing>
On Thursday 24 July 2003 16:26, Delcho wrote:
> Hello,
> I have a problem with my htb in linux gateway machine.
> Wana make this borrow to and from internet:
> every user must be shaped to 32Kbit,max number of users are 6 in one
> subnet /29
> and all subnet must be shaped to 92Kbit,e.i every user will download
> with 32Kbit,but when
> all 6 user download do not over 92Kbit! I make some classes /attache
> them/ but every user download with 32Kbit and over many up 92Kbit.
> The script:
>
> tc qdisc add dev eth1 root handle 1: htb default 2
> tc class add dev eth1 parent 1: classid 1:2 htb rate 100Mbit
> ceil 100Mbit burst 1k
> tc class add dev eth1 parent 1:2 classid 1:11 htb rate
> 92Kbit ceil 92Kbit burst 1k
> tc qdisc add dev eth1 parent 1:11 handle 11 sfq perturb 10
> tc class add dev eth1 parent 1:11 classid 1:30 htb rate
> 32Kbit ceil 32Kbit burst 1k
> tc qdisc add dev eth1 parent 1:30 handle 30 sfq perturb 10
> tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32
> match ip dst 192.168.1.17 classid 1:30
> tc class add dev eth1 parent 1:11 classid 1:40 htb rate
> 32Kbit ceil 32Kbit burst 1k
> tc qdisc add dev eth1 parent 1:40 handle 40 sfq perturb 10
> tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32
> match ip dst 192.168.1.18 classid 1:40
> ........
> tc class add dev eth1 parent 1:11 classid 1:80 htb rate
> 32Kbit ceil 32Kbit burst 1k
> tc qdisc add dev eth1 parent 1:80 handle 80 sfq perturb 10
> tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32
> match ip dst 192.168.1.22 classid 1:80
>
> May be there is mistake but where.....?
Take a look at the faq pages on docum.org. There is a section with htb rules.
The problem is that the rate is a minium and the parent ceil is not respected
if the child classes are asking more then the ceil.
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/
next prev parent reply other threads:[~2003-07-28 17:49 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 2:46 [LARTC] HTB problem yangrunhua
2001-12-11 9:21 ` bert hubert
2001-12-11 9:34 ` yangrunhua
2001-12-11 9:35 ` yangrunhua
2001-12-11 11:10 ` bert hubert
2001-12-12 5:47 ` yangrunhua
2001-12-12 10:02 ` yangrunhua
2001-12-12 11:40 ` Martin Devera
2001-12-12 13:50 ` bert hubert
2001-12-12 23:48 ` yangrunhua
2001-12-13 10:07 ` bert hubert
2002-06-26 0:22 ` [LARTC] htb problem Omar Armas
2002-06-26 0:32 ` Tomasz Wrona
2002-12-09 18:19 ` [LARTC] HTB Problem lartc
2002-12-09 18:57 ` Stef Coene
2003-01-23 22:47 ` [LARTC] HTB problem Jay Wineinger
2003-01-24 2:15 ` mingching.tiew
2003-01-24 2:39 ` Jay Wineinger
2003-06-12 19:21 ` [LARTC] htb problem Ratel
2003-06-12 19:23 ` Esteban
2003-06-12 19:35 ` Stef Coene
2003-06-12 20:04 ` Morten Isaksen
2003-06-12 20:51 ` Stef Coene
2003-06-12 20:54 ` Stef Coene
2003-06-12 21:15 ` Stef Coene
2003-06-14 21:46 ` terahz
2003-06-15 18:14 ` Stef Coene
2003-06-25 11:14 ` Ratel
2003-07-24 14:26 ` Delcho
2003-07-28 17:49 ` Stef Coene [this message]
2003-09-30 13:44 ` [LARTC] HTB Problem Guilherme Benkenstein
2003-09-30 19:59 ` Stef Coene
2003-12-02 23:08 ` [LARTC] HTB problem Mihai Tanasescu
2003-12-04 5:16 ` Mihai Tanasescu
2003-12-04 7:40 ` Catalin BOIE
-- strict thread matches above, loose matches on Subject: below --
2004-09-06 21:56 Cow
2004-09-07 11:08 ` zytek
2004-09-07 20:28 ` Cow
2004-09-07 21:16 ` [LARTC] HTB Problem Cow
2004-09-07 21:18 ` [LARTC] HTB problem Cow
2004-09-07 21:53 ` Andreas Klauer
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-105941490514168@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.