From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] filters not doing anything?
Date: Sun, 20 Apr 2003 21:44:38 +0000 [thread overview]
Message-ID: <marc-lartc-105087514026174@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105078585814903@msgid-missing>
On Saturday 19 April 2003 22:55, Frank v Waveren wrote:
> I have the following setup:
>
> tc qdisc del dev eth1 root
> tc qdisc add dev eth1 root handle 1: htb
> tc class add dev eth1 parent 1: classid 1:1 htb rate 80kbit ceil 80kbit
> tc qdisc add dev eth1 parent 1:1 handle 2: prio
> tc qdisc add dev eth1 parent 2:1 handle 3: sfq perturb 10
> tc filter add dev eth1 protocol ip parent 1: prio 2 u32 match u8 0 0x0 at 0
> flowid 3:
>
> (the filter line is not like the one suggested in the howto because my
> version of tc (the most recent with htb patch) barfs on not having any
> rules)
>
> After a while, looking at the stats:
> qdisc sfq 3: dev eth1 limit 128p quantum 1514b perturb 10sec
> Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
> qdisc prio 2: dev eth1 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
> Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
> qdisc htb 1: dev eth1 r2q 10 default 0 direct_packets_stat 476
> Sent 112219 bytes 476 pkts (dropped 0, overlimits 0)
>
> All the traffic went through the top htb (which wasn't limited) and
> went straight out again. Why didn't the filter rule put everything in
> the 3: SFQ, forcing it to trickle through the limited HTB class 1:1?
Qdisc 3: is added to class 2:1. So all traffic flowing in class 2:1 is
handled by qdisc 3:. Also, traffic in class 1:1 is handled by qdisc 2:.
So you have to put the traffic in the class and not the qdisc. So your filter
should be : 1: -> 1:1 and a second filter from 2: -> 2:1.
Or 1: -> 2:1.
The end of a filter is a class, not a qdisc.
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-04-20 21:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 20:55 [LARTC] filters not doing anything? Frank v Waveren
2003-04-19 22:38 ` Frank v Waveren
2003-04-20 21:44 ` Stef Coene [this message]
2003-04-20 21:56 ` Frank v Waveren
2003-04-20 21:59 ` Stef Coene
2003-04-20 22:12 ` Frank v Waveren
2003-04-21 9:20 ` Stef Coene
2003-04-21 14:04 ` Frank v Waveren
2003-04-21 19:33 ` Stef Coene
2003-04-21 20:19 ` Frank v Waveren
2003-04-22 14:41 ` Stef Coene
2003-04-22 17:25 ` Frank v Waveren
2003-04-22 17:55 ` 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-105087514026174@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.