From: Michal Soltys <nozo@ziu.info>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc filter syntax (and general noobness)
Date: Fri, 07 Sep 2007 16:17:06 +0000 [thread overview]
Message-ID: <46E17982.802@ziu.info> (raw)
In-Reply-To: <46E162F3.7010301@vadtec.net>
Vadtec wrote:
>
> ...
> protocol 6 match u32 0xff534d42 0xffffffff at nexthdr+23 flowid 2:50
> ...
>
Using nexthdr+ in as simple way as above won't work. U32 won't automatically
adjust for the proper offset, you have to do it manually with another u32
filter, using "link" option.
It's very well explained in
http://ace-host.stuart.id.au/russell/files/tc/doc/cls_u32.txt
As a side note - don't forget that you can simply mark the traffic in
iptables and then use fwmark instead of u32 (or with u32 match mark).
Other bits of not so easily to find documentation re. tc, in case you need
it later in other cases:
1) In source tarball, check doc subdirectory for info about extended action
syntax
2) a bit of info about basic classifiers:
http://marc.info/?l=lartc&m\x117569441229800&w=2
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-09-07 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 14:40 [LARTC] tc filter syntax (and general noobness) Vadtec
2007-09-07 16:17 ` Michal Soltys [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=46E17982.802@ziu.info \
--to=nozo@ziu.info \
--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.