Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc filter can target only leaf classes?
Date: Sat, 25 Feb 2006 11:43:06 +0000	[thread overview]
Message-ID: <440042CA.8020207@dsl.pipex.com> (raw)
In-Reply-To: <20060224190143.GA6809@mandriva.com>

Andreas Hasenack wrote:
> (using htb)
> 
> I'm trying to learn tc filter and it seems the flowid parameter can only
> point to leaf classes. Actually, it can point anywhere, but it doesn't
> seem to work unless it points to a leaf class. Is this correct?
> 
> For example, I have this tree:
> 
> 			eth0
> 			|
> 		 +------1:-------+
>                  |               |
>          +------1:10		1:20
>          |       |               |
> 	1:30	1:40		20:
>          |       |
> 	30:	40:
> 
> 1: is htb qdisc, with default pointing to minor 20.
> 
> And this filter:
> 
> iptables -t mangle -A OUTPUT -d $DSTHOST -j MARK --set-mark 1
> tc filter add dev $DEV parent 1:0 prio 1 protocol ip \
>         handle 1 \
>         fw \
>         flowid 1:10
> 
> Now, I only see 1:10 getting the traffic if 1:30 and 1:40 don't exist.
> The moment I add 1:30, 1:40 and their qdiscs, the above filter stops
> working and this same traffic starts going to 1:20, which is the default
> set at 1:'s qdisc. 
> 
> Why does the filter stop working? I was expecting it to keep working and
> then I could further filter this traffic into 1:30 and 1:40 *at* 1:10.

You need other filters with parent 1:10 to send to leafs below 1:10

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2006-02-25 11:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 19:01 [LARTC] tc filter can target only leaf classes? Andreas Hasenack
2006-02-25 11:43 ` Andy Furniss [this message]
2006-02-26 18:22 ` Andreas Hasenack

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=440042CA.8020207@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