
Configuring Traffic Filters and Protocol Prioritization
8-6
308645-15.0 Rev 00
For every packet that matches the filter criteria, the router sends an entry to
the system event log. You can specify the log action in combination with other
actions.
In addition to the accept, drop, and log actions common to all inbound traffic
filters, you can also specify the following actions:
• Forward to next hop
• Drop if next hop is unreachable
• Forward to IP address
• Forward to next-hop interfaces
• Forward to first up next-hop interface
• Detailed logging
For information about changing IP actions for traffic filters and templates, see
“Specifying the Action of Inbound Traffic Filters and Templates” on page 8-16.
Extended and Nonextended Filtering Modes
By default, the router operates in nonextended filtering mode upon initial boot-up.
In nonextended mode, you can configure from 1 through 31 traffic filters per IP
interface.
Using the Technician Interface, you can enable extended filtering mode by setting
the MIB variable wfIpBaseExtendedTrafficFilterSupport to enable. The router
restarts the IP protocol, reading currently configured IP traffic filters into the
router’s configuration. You use extended filtering mode only when you need to
configure more than 31 traffic filters on a single IP interface.
The BCC automatically turns on extended filtering mode when you configure the
thirty-second traffic filter on the same interface. After extended filtering mode is
enabled, the system remains in that mode; it does not revert back to nonextended
filtering mode if the number of filters on an interface drops below 32.
Using the Technician Interface, you can set the mode back to nonextended, but be
aware that the router reads back only up to 31 filters into the configuration. The
router does not retain more than 31 filters unless you first save them to a
configuration file.
Commentaires sur ces manuels