for a u16 match. In many cases, there is a field name that can be used for the match, eliminating
the need to specify the offset.
Note that specifying a tcp, udp, or icmp field does not automatically include a match for the
appropriate IP protocol. To insure that only the desired packets are filtered, include a match for
IP protocol as well as the port or type. For example:
u32 match ip protocol 6 0xff match tcp dst 8 0xffff
Or
u32 match ip protocol 17 FF match ip sport 20 0xffff
zqosd
Thus far, tc has been used without zqosd. It is not sufficient to install software rules on the
Ethernet Switch Blade User's Guide
Downloaded from
www.Manualslib.com
Field Match
ip src a.b.c.d/n
ip dst a.b.c.d/n
ip tos <value> <mask>
ip dsfield <value> <mask>
ip protocol <value> <mask>
ip precedence <val> <mask>
ip dport <value> <mask>
ip sport <value> <mask>
ip icmp_type <val> <mask>
ip icmp_code <val> <mask>
udp src <value> <mask>
udp dst <value> <mask>
tcp src <value> <mask>
tcp dst <value> <mask>
icmp type <value> <mask>
icmp code <value> <mask>
Table 7.3: U Match Selectors
manuals search engine
U match selectors
Equivalent
u32 <value> <mask> at 12
u32 <value> <mask> at 16
u8 <value> <mask> at 1
u8 <value> <mask> at 1
u8 <value> <mask> at 9
u8 <val> <mask> at 1
u16 <value> <mask> at 22
u16 <value> <mask> at 20
u8 <val> <mask> at 20
u8 <val> <mask> at 21
u16 <value> <mask> at 20
u16 <value> <mask> at 22
u16 <value> <mask> at 20
u16 <value> <mask> at 22
u8 <value> <mask> at 20
u8 <value> <mask> at 21
release 3.2.2j
page 120