From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] why isn't 1:1 getting the traffic? [filter question]
Date: Sat, 25 Feb 2006 11:45:50 +0000 [thread overview]
Message-ID: <4400436E.20901@dsl.pipex.com> (raw)
In-Reply-To: <20060224175729.GF3794@mandriva.com>
Andreas Hasenack wrote:
> With the below script, whenever I ping 10.0.16.10 (which matches the
> only filter I have), traffic still get's sent to the default 1:2 class
> instead of 1:1 and I don't know why... Any hints?
>
> (kernel 2.6.12, iproute2-2.6.15)
>
> tc qdisc del dev eth0 root > /dev/null 2>&1
> tc qdisc add dev eth0 handle 1: root htb default 2
> tc class add dev eth0 classid 1:1 parent 1: htb rate 100kbps ceil 100kbps quantum 1500
> tc class add dev eth0 classid 1:2 parent 1: htb rate 90mbit ceil 90mbit quantum 1500
> tc qdisc add dev eth0 handle 2: parent 1:2 sfq perturb 10
> tc class add dev eth0 classid 1:10 parent 1:1 htb prio 0 rate 30kbps quantum 1500
> tc qdisc add dev eth0 handle 10: parent 1:10 sfq perturb 10
> tc class add dev eth0 classid 1:11 parent 1:1 htb prio 0 rate 70kbps ceil 100kbps quantum 1500
> tc qdisc add dev eth0 handle 20: parent 1:11 sfq perturb 10
> tc class add dev eth0 classid 1:12 parent 1:1 htb rate 60kbps ceil 100kbps quantum 1500
> tc qdisc add dev eth0 handle 30: parent 1:12 sfq perturb 10
> tc filter add dev eth0 parent 1:0 prio 1 protocol ip u32 \
> match ip dst 10.0.16.10/32 \
> flowid 1:1
It's because 1:1 isn't a leaf, you need more filters with parent 1:1 to
filter to the leaves.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-02-25 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 17:57 [LARTC] why isn't 1:1 getting the traffic? [filter question] Andreas Hasenack
2006-02-24 21:19 ` Andreas
2006-02-24 23:01 ` Andreas Klauer
2006-02-25 3:36 ` gypsy
2006-02-25 11:45 ` Andy Furniss [this message]
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=4400436E.20901@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox