From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] u32 filter
Date: Tue, 06 May 2003 17:27:33 +0000 [thread overview]
Message-ID: <marc-lartc-105224240732586@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103920065528929@msgid-missing>
On Tuesday 06 May 2003 13:10, Vitor Carlos Flausino wrote:
> Hi all.
>
> I have the following queue:
>
>
> tc qdisc add dev eth0 root handle 1:0 htb default 15
>
>
> tc class add dev eth0 parent 1:0 classid 1:1 htb rate 100mbit ceil 100mbit
>
> tc class add dev eth0 parent 1:1 classid 1:7 htb rate 64kbit ceil 64kbit
> tc class add dev eth0 parent 1:1 classid 1:15 htb rate 102336kbit ceil
> 100mbit
>
> tc qdisc add dev eth0 parent 1:7 handle 10:0 sfq perturb 10
> tc qdisc add dev eth0 parent 1:15 handle 20:0 sfq perturb 10
>
> Now, my question is, the filter should be:
>
> tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip
> 57.227.234.22 flowid 1:7
>
> or,
>
> tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip
> 57.227.234.22 flowid 10:0
>
> ?
>
> What about the default?
The default is the minor number, so the second number in 1:15. So 15 like you
did.
For the filter, 10:0 is connected to 1:7. So all traffic placed in 1:7 flows
through 10:0. So the filter should point to 1:7. So the first filter rule
is the one you need.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-05-06 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 18:53 [LARTC] u32 filter Kaustubh Phanse
2003-05-06 11:10 ` Vitor Carlos Flausino
2003-05-06 12:07 ` Michael Yuan
2003-05-06 17:27 ` Stef Coene [this message]
2003-05-23 9:57 ` Esteban
2003-05-23 13:14 ` Harkisoon Sharan (CCI-Gainesville)
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-105224240732586@msgid-missing \
--to=stef.coene@docum.org \
--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.