From: <oarmas@mpsnet.net.mx>
To: lartc@vger.kernel.org
Subject: [LARTC] tc not working
Date: Sat, 06 Oct 2001 17:31:59 +0000 [thread overview]
Message-ID: <marc-lartc-100238958132380@msgid-missing> (raw)
I have a computer with RH 7.1 and want to control bandwith to a set of
networks.
This is the configuration:
Internet
|
eth0: 200.39.191.182
eth1: 200.39.178.129
|
client network (200.39.178.128/26)
I use the next script:
--------------------begin-----------------------
tc qdisc add dev eth0 root handle 10: cbq bandwidth 10Mbit avpkt 1000
tc class add dev eth0 parent 10:0 classid 10:1 cbq bandwidth 10Mbit rate \
10Mbit allot 1514 weight 1Mbit prio 8 maxburst 20 avpkt 1000
tc class add dev eth0 parent 10:1 classid 10:64 cbq bandwidth 10Mbit rate
\
64Kbit allot 1514 weight 6Kbit prio 5 maxburst 20 avpkt 1000 bounded
tc class add dev eth0 parent 10:1 classid 10:128 cbq bandwidth 10Mbit rate
\
128Kbit allot 1514 weight 12Kbit prio 5 maxburst 20 avpkt 1000 bounded
tc class add dev eth0 parent 10:1 classid 10:256 cbq bandwidth 10Mbit rate
\
256Kbit allot 1514 weight 25Kbit prio 5 maxburst 20 avpkt 1000 bounded
tc class add dev eth0 parent 10:1 classid 10:512 cbq bandwidth 10Mbit rate
\
512Kbit allot 1514 weight 51Kbit prio 5 maxburst 20 avpkt 1000 bounded
tc class add dev eth0 parent 10:1 classid 10:1024 cbq bandwidth 10Mbit
rate \
1024Kbit allot 1514 weight 102Kbit prio 5 maxburst 20 avpkt 1000 bounded
tc qdisc add dev eth0 parent 10:64 sfq quantum 1514b perturb 15
tc qdisc add dev eth0 parent 10:128 sfq quantum 1514b perturb 15
tc qdisc add dev eth0 parent 10:256 sfq quantum 1514b perturb 15
tc qdisc add dev eth0 parent 10:512 sfq quantum 1514b perturb 15
tc qdisc add dev eth0 parent 10:1024 sfq quantum 1514b perturb 15
tc filter add dev eth0 parent 10:0 protocol ip prio 100 u32 match ip dst
200.39.178.128/26 flowid 10:256
-------------------------end----------------------------
It shoud limit this network to 256, but it does not.
When I test it, it shows no bandwidth limit, since I get rates higher
than the allowed from the client side(32kB/s should be maximum).
Example:
ncftp / > put redhat-6.2-i386.iso
redhat-6.2-i386.iso: 0.59/ 2.10 MB 83.03 kB/s
For both, outgoing and incoming trafic.
Any idea of what can be wrong?
--
Omar
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next reply other threads:[~2001-10-06 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-06 17:31 oarmas [this message]
2001-10-08 15:27 ` [LARTC] tc not working bert hubert
2001-10-08 17:24 ` Omar Armas Aleman
2001-10-12 6:51 ` Stef Coene
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-100238958132380@msgid-missing \
--to=oarmas@mpsnet.net.mx \
--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