From: "Roy" <roy@xxx.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc does'nt limit the bandwidth!
Date: Tue, 13 Apr 2004 22:28:36 +0000 [thread overview]
Message-ID: <00e301c421a6$aae441b0$030aa8c0@t> (raw)
In-Reply-To: <20040413201326.8460.qmail@web20103.mail.yahoo.com>
first you cant use limit of 9 bits /s it is 1 byte /s, so completely
unreasonable speed. set it to 50 bytes/s at least
another popstential problem that you are using independent root classes for
each client
that means they wont share bandwitch. customer a will always get 256 kbits
and others will get their ceil limit all time.
and my suggestion is to NOT touch default or you may have problems
if rate = ceil then just specify rate.
if you want your clients share bandwitch then you need to create one root
class and attach everyone to it.
this will look like this:
tc qdisc add dev eth1 root handle 1: htb default 1
#Classes#
tc class add dev eth1 parent 1: classid 1:5 htb
rate 230kbps #root (set rate to 80-90% of link capacity)
tc class add dev eth1 parent 1:5 classid 1:100 htb
rate 9bps ceil 9bps #ICMP
tc class add dev eth1 parent 1:5 classid 1:100 htb
rate 144kbps ceil 230kbps #customer A
tc class add dev eth1 parent 1:5 classid 1:101 htb
rate 16kbps #customer B
tc class add dev eth1 parent 1:5 classid 1:111 htb
rate 32kbps #customer C
tc class add dev eth1 parent 1:5 classid 1:121 htb
rate 32kbps #customer D
b,c and d will get always and only rate amount of trafic
----- Original Message -----
From: "segun adesina" <digihall7@yahoo.com>
To: <lartc@mailman.ds9a.nl>
Sent: Tuesday, April 13, 2004 11:13 PM
Subject: [LARTC] tc does'nt limit the bandwidth!
>
> Hi, good people!
>
> I wanted to limit my 4 customers to 144, 16, 32, and
> 32kbps.
> I used the following tc commands BUT IT FAILED TO
> LIMIT each and everyone of them to its bandwidth.
> What am I doing wrong:
>
> My tc scripts are:
>
> tc qdisc add dev eth1 root handle 1: htb default 1
> #Classes#
> tc class add dev eth1 parent 1: classid 1:1 htb
> rate 9bps ceil 9bps #Default
> tc class add dev eth1 parent 1: classid 1:100 htb
> rate 9bps ceil 9bps #ICMP
>
>
> tc class add dev eth1 parent 1: classid 1:5 htb
> rate 144kbps ceil 256kbps #customer A
> tc class add dev eth1 parent 1: classid 1:101 htb
> rate 16kbps ceil 16kbps #customer B
> tc class add dev eth1 parent 1: classid 1:111 htb
> rate 32kbps ceil 32kbps #customer C
> tc class add dev eth1 parent 1: classid 1:121 htb
> rate 32kbps ceil 32kbps #customer D
>
> Can anyone help me on how to limit the the bandwidth
> to these customers.
> Regards.
>
> Digihall7.
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Tax Center - File online by April 15th
> http://taxes.yahoo.com/filing.html
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-04-13 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 20:13 [LARTC] tc does'nt limit the bandwidth! segun adesina
2004-04-13 20:38 ` Jason Boxman
2004-04-13 21:26 ` Corey Hickey
2004-04-13 22:28 ` Roy [this message]
2004-04-14 17:12 ` segun adesina
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='00e301c421a6$aae441b0$030aa8c0@t' \
--to=roy@xxx.lt \
--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.