From: Bruno Maciel Fonseca bruno@avati.com.br
To: lartc@vger.kernel.org
Subject: [LARTC] Traffic shaping
Date: Sat, 06 Jan 2001 09:25:35 +0000 [thread overview]
Message-ID: <marc-lartc-98373940416826@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416818@msgid-missing>
<PRE>Hi,
I'm trying to limit the outgoing traffic. I have a router with two
ethernets and a client that is routered. I can limit the incoming
traffic using u32, but i tried to limit the outgoing but nothing
happened. Then i tried to use ipchains and fw to limit it and again
nothing happened. Here are my configurations:
------------
Client --- eth1| Router |eth0 --- Internet
------------
Router: eth0: 192.168.0.207
eth1: 10.0.1.1
Client: 10.0.1.2
SCRIPT WITH u32:
tc qdisc add dev eth0 root handle 1:0 cbq bandwidth 256Kbit avpkt 1000
cell 8
tc class add dev eth0 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 eth0 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 eth0 parent 1:10 tbf rate 64Kbit buffer 10Kb/8 limit
15Kb mtu 1500
tc filter add dev eth0 parent 1:0 protocol ip prio 100 u32 match ip src
10.0.5.2 flowid 1:10
SCRIPT WITH fw:
ipchains -A forward -s 10.0.5.0/24 -j MASQ -m 0x1
tc qdisc add dev eth0 root handle 1: cbq bandwidth 128Kbit avpkt 1000
tc class add dev eth0 parent 1:0 classid 1:1 cbq bandwidth 128Kbit rate
128Kbit allot 1514 weight 12Kbit prio 8 maxburst 20 avpkt 1000
tc class add dev eth0 parent 1:1 classid 1:2 cbq bandwidth 128Kbit rate
128Kbit allot 1514 weight 12Kbit prio 8 maxburst 20 avpkt 1000
tc class add dev eth0 parent 1:2 classid 1:11 cbq bandwidth 128Kbit rate
128Kbit allot 1514 weight 2Kbit prio 5 maxburst 20 avpkt 1000 split 1:2
tc qdisc add dev eth0 parent 1:11 sfq quantum 1514b perturb 15
tc filter add dev eth0 parent 1:0 protocol ip prio 100 handle 1 fw
classid 1:11
So, does anybody know what is happening?
Thanks,
Bruno
</PRE>
next prev parent reply other threads:[~2001-01-06 9:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 12:22 [LARTC] traffic shaping Wouter
2001-01-04 18:17 ` Sander
2001-01-05 3:52 ` Sander
2001-01-05 11:42 ` Wouter
2001-01-05 13:56 ` Junus
2001-01-05 13:56 ` Junus
2001-01-06 9:25 ` Bruno [this message]
2001-01-07 13:54 ` [LARTC] Traffic shaping Junus
2001-12-25 12:15 ` [LARTC] Traffic Shaping Sahil Gupta - NET4U
2001-12-25 12:27 ` bert hubert
2001-12-25 12:33 ` Sahil Gupta - NET4U
2001-12-25 12:34 ` Sahil Gupta - NET4U
2001-12-25 12:42 ` bert hubert
2002-01-22 4:52 ` [LARTC] traffic shaping Antonis Lazaridis
2002-01-22 7:44 ` Martin Devera
2002-01-23 8:23 ` Martin Devera
2002-01-23 9:42 ` Antonis Lazaridis
2002-01-23 9:51 ` Martin Devera
2002-01-25 8:11 ` Antonis Lazaridis
2002-01-26 23:00 ` Martin Devera
2002-01-27 1:21 ` Re[2]: " Will Lotto
2002-01-27 8:47 ` Stef Coene
2002-02-08 5:17 ` Antonis Lazaridis
2002-02-08 17:22 ` Riaz Mahmood
2006-10-04 20:45 ` Roberto Scattini
2007-05-06 20:14 ` [LARTC] Traffic Shaping Rangi Biddle
2007-05-07 8:25 ` AW: " Simo
2007-05-07 18:06 ` Rangi Biddle
2007-05-08 3:16 ` Rangi Biddle
2007-10-24 18:37 ` [LARTC] Traffic shaping Mohammad Shakir
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-98373940416826@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.