
Configuring IP Inbound Traffic Filters Using the BCC
308645-14.00 Rev 00
8-9
Example - Creating a Traffic Filter Without Using a Template
This example creates a traffic filter named telnet2 with no traffic filter template.
The system calculates the next highest precedence value.
ip/192.32.35.17/255.255.255.0# traffic-filter telnet2
traffic-filter/telnet2/192.32.35.17#
For information about specifying match criteria, see “Specifying Match Criteria
for IP Inbound Traffic Filters and Templates” on page 8-9
. For information about
specifying the filter action, see “Specifying the Action of Inbound Traffic Filters
and Templates” on page 8-16
.
Specifying Match Criteria for IP Inbound Traffic Filters and
Templates
The match criteria in a filter specify which fields in the IP header of each packet
must contain the values that you specify. You can also specify certain fields in the
headers of TCP and UDP packets contained in the IP data field of IP packets.
To prepare to specify the filtering criteria, navigate to the filter template prompt
(for example,
box; ip; filter-template/telnet-in) or to the traffic filter prompt
(
box; eth 2/1; ip/192.32.35.17/255.255.255.0; traffic-filter/telnet-in) and enter:
match
You can specify match criteria for filters as described in the following sections:
Topic Page
Source and destination network 8-10
Source and destination TCP and UDP port 8-10
Protocol type 8-13
Type of service 8-15
Established TCP ports 8-15
User-defined criteria 8-16
Comentários a estes Manuais