From: Bruno Maciel Fonseca bruno@avati.com.br
To: lartc@vger.kernel.org
Subject: [LARTC] Traffic Shapping
Date: Mon, 08 Jan 2001 10:51:16 +0000 [thread overview]
Message-ID: <marc-lartc-98373940416833@msgid-missing> (raw)
<PRE>Hi Junus Junarto D,
I still have the same problem of limiting the outgoing traffic.
I'm limiting the incoming traffic perfectily with the script:
tc qdisc add dev eth1 root handle 1:0 cbq bandwidth 256Kbit avpkt 1000 cell 8
tc class add dev eth1 parent 1:0 classid 1:1 cbq bandwidth 256Kbit rate \
256Kbit weight 20Kbit prio 8 allot 1514 cell 8 maxburst 20 avpkt 1000
tc class add dev eth1 parent 1:1 classid 1:10 cbq bandwidth 256Kbit rate \
64Kbit weight 6Kbit prio 5 allot 1514 cell 8 maxburst 20 avpkt 1000 bounded
tc qdisc add dev eth1 parent 1:10 tbf rate 64Kbit buffer 10Kb/8 limit 15Kb \
mtu 1500
tc filter add dev eth1 parent 1:0 protocol ip prio 100 u32 match ip dst \
10.0.5.2 flowid 1:10
But when I try to limit the incoming traffic I still have the same problem
that it does not limit. And I still doesn't know why. I used your and my
script and everything happens like there is no shaper...
The outgoing traffic script is:
tc qdisc add dev eth0 root handle 2:0 cbq bandwidth 256Kbit avpkt 1000 \
cell 8
tc class add dev eth0 parent 2:0 classid 2:1 cbq bandwidth 256Kbit rate \
256Kbit weight 20Kbit prio 8 allot 1514 cell 8 maxburst 20 avpkt 1000
tc class add dev eth0 parent 2:1 classid 2:10 cbq bandwidth 256Kbit rate \
64Kbit weight 6Kbit prio 5 allot 1514 cell 8 maxburst 20 avpkt 1000
bounded
tc qdisc add dev eth0 parent 2:10 tbf rate 64Kbit buffer 10Kb/8 limit \
15Kb mtu 1500
tc filter add dev eth0 parent 2:0 protocol ip prio 100 u32 match ip src \
10.0.5.2 flowid 2:10
But, thanx a lot...
Bruno
</PRE>
reply other threads:[~2001-01-08 10:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-98373940416833@msgid-missing \
--to=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.