From: "Bob Puff" <bob@nleaudio.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: Order of 'tc filer'
Date: Sat, 17 Feb 2007 18:33:23 +0000 [thread overview]
Message-ID: <20070217183246.M70798@nleaudio.com> (raw)
In-Reply-To: <e208f5d10702171014w6bbec280g5f48c49eb6909f57@mail.gmail.com>
This is the reverse of what I believe I have read - you may want to continue
looking. Prio 0 is supposed to be the highest, i believe.
Bob
---------- Original Message -----------
From: "Martin Schiøtz" <malinux@gmail.com>
To: lartc@mailman.ds9a.nl
Sent: Sat, 17 Feb 2007 19:14:46 +0100
Subject: [LARTC] Re: Order of 'tc filer'
> OK - I solved the thing. Using 'prio 0' actually gives the filter a
> low priority.
>
> I just used 'prio 1' instead and know I can control the order :-)
>
> - Martin
>
> On 2/17/07, Martin Schiøtz <malinux@gmail.com> wrote:
> > Hi
> >
> > How can I control which filter a packet will meet first?
> >
> > I have tried changing the order of applying the tc filter scripts and
> > switching flowid number, but 'protocol ip u32 match ip src <ip net>
> > match ip src 0.0.0.0/0' always kicks in first?
> >
> > From my script
> > --------------------
> > # All traffic - Priority: Low
> > tc filter add dev eth0 parent 1:0 prio 2 protocol ip u32 match ip src
> > <ip net> match ip src 0.0.0.0/0 flowid 1:21
> > # Traffic between offices (IPSEC) - Priority: High
> > tc filter add dev eth0 parent 1:0 prio 0 protocol ip u32 match ip src
> > <ip net> match ip protocol 50 0xff flowid 1:22
> >
> >
> > # tc -s filter show dev eth0
> > ----------------------------------
> > filter parent 1: protocol ip pref 2 u32
> > filter parent 1: protocol ip pref 2 u32 fh 800: ht divisor 1
> > filter parent 1: protocol ip pref 2 u32 fh 800::802 order 2050 key ht
> > 800 bkt 0 flowid 1:21 (rule hit 428 success 426)
> > match c0000000/e0000000 at 16 (success 426 )
> > match 00000000/00000000 at 12 (success 426 )
> > filter parent 1: protocol ip pref 49151 u32
> > filter parent 1: protocol ip pref 49151 u32 fh 803: ht divisor 1
> > filter parent 1: protocol ip pref 49151 u32 fh 803::800 order 2048 key
> > ht 803 bkt 0 flowid 1:22 (rule hit 3 success 0)
> > match c0000000/e0000000 at 16 (success 0 )
> > match 00320000/00ff0000 at 8 (success 0 )
> >
> > - Martin
> >
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
------- End of Original Message -------
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-02-17 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 18:14 [LARTC] Re: Order of 'tc filer' Martin Schiøtz
2007-02-17 18:33 ` Bob Puff [this message]
2007-02-17 21:39 ` Martin Schiøtz
2007-02-17 22:45 ` Georgy Zhukov
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=20070217183246.M70798@nleaudio.com \
--to=bob@nleaudio.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 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.