From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Soltys Date: Fri, 07 Sep 2007 16:17:06 +0000 Subject: Re: [LARTC] tc filter syntax (and general noobness) Message-Id: <46E17982.802@ziu.info> List-Id: References: <46E162F3.7010301@vadtec.net> In-Reply-To: <46E162F3.7010301@vadtec.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org 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&m7569441229800&w=2 _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc