From: Matteo Brusa <miagi@tiscali.it>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: Shaping incoming traffic on the other interface
Date: Thu, 10 Jun 2004 16:54:21 +0000 [thread overview]
Message-ID: <40C8923D.2070305@tiscali.it> (raw)
In-Reply-To: <87u0xjtma8.fsf@stark.xeocode.com>
Greg Stark wrote:
> Hm, I just did exactly the same thing here. I don't see this.
>
> What do your filters look like?
Thanks for your quick answer. My config doesn't look so different:
tc qdisc add dev eth0 root handle 1: htb default 20
tc class add dev eth0 parent 1: classid 1:1 htb rate 2000kbit
tc class add dev eth0 parent 1:1 classid 1:10 htb rate 2000kbit prio 1
tc class add dev eth0 parent 1:1 classid 1:20 htb rate 50kbit ceil 2000kbit prio 2
tc qdisc add dev eth0 parent 1:10 handle 10: sfq perturb 10
tc qdisc add dev eth0 parent 1:20 handle 20: sfq perturb 10
tc filter add dev eth0 parent 1:0 prio 0 protocol ip handle 10 fw flowid 1:10
tc filter add dev eth0 parent 1:0 prio 0 protocol ip handle 20 fw flowid 1:20
The packets are marked in the POSTROUTING chain of the mangle table, as usual.
I'm running kernel 2.4.20-30.9 custom and iptables v1.2.7a. HTB is reported as 3.10.
Note that the problem raises when i hit the ceil throuput.
Thanks,
MatB
_______________________________________________
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-06-10 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 16:23 [LARTC] Re: Shaping incoming traffic on the other interface Greg Stark
2004-06-10 16:54 ` Matteo Brusa [this message]
2004-06-10 20:07 ` Greg Stark
2004-06-10 20:30 ` Jason Boxman
2004-06-10 20:33 ` Andreas Klauer
2004-06-11 5:13 ` Greg Stark
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=40C8923D.2070305@tiscali.it \
--to=miagi@tiscali.it \
--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.