Single value
Multi value
range is not
supported.
Note
Defines a list of {operation, value} pairs used
to match the type field of an ICMP packet.
Values are encoded using a single byte. The
ICMP type and code specifiers evaluate to
FALSE whenever the protocol value is not
ICMP.
Encoding: <type (1 octet), [op, value]+>
Syntax:
match
{
ipv4
}
icmp-type
{
value
|
min-value
-
max-value
}
IPv4 ICMP type
Type 7
Single value
Multi value
range is not
supported.
Note
Defines a list of {operation, value} pairs used
to match the code field of an ICMP packet.
Values are encoded using a single byte.
Encoding: <type (1 octet), [op, value]+>
Syntax:
match
{
ipv4
}
icmp-code
{
value
|
min-value
-
max-value
}
IPv4 ICMP code
Type 8
Bit mask
Bitmask values can be encoded as a 1- or
2-byte bitmask. When a single byte is
specified, it matches byte 13 of the TCP
header, which contains bits 8 through 15 of
the 4th 32-bit word. When a 2-byte encoding
is used, it matches bytes 12 and 13 of the TCP
header with the data offset field having a
"don't care" value. As with port specifier, this
component evaluates to FALSE for packets
that are not TCP packets. This type uses the
bitmask operand format, which differs from
the numeric operator format in the lower
nibble.
Encoding: <type (1 octet), [op, b>
Syntax:
match tcp-flag value bit-mask
mask_value
IPv4 TCP flags (2
bytes include
reserved bits)
Reserved
and NS bit
not
supported
Note
Type 9
Multi value range
Match on the total IP packet length (excluding
Layer 2, but including IP header). Values are
encoded using 1- or 2-byte quantities.
Encoding: <type (1 octet), [op, value]+>
Syntax:
matchpacket length
{
packet-length-value
|
min-value
-
max-value
}
IPv4 Packet length
Type 10
Routing Configuration Guide for Cisco NCS 6000 Series Routers, IOS XR Release 6.4.x
108
Implementing BGP Flowspec
Supported Matching Criteria and Actions