Re: tc filter syntax (and general noobness)

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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=117569441229800&w=2

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

[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux