
Configuring Traffic Filters and Protocol Prioritization
1-12
Actions
The filter action determines what happens to packets that match a filter criterion’s
ranges. Traffic filter actions are mutually exclusive, except the Log action.
In addition to the common traffic filter actions described in this section, there are
protocol-specific actions, described in Chapter 3.
Filtering Actions
You can apply the following actions to any traffic filter:
• Accept — The router processes any packet that matches the filter criteria and
ranges.
• Drop — The router does not route any packet that matches the filter criteria
and ranges.
• Log — For every packet that matches the filter criteria and ranges, the router
sends an entry to the system Events log. You can specify the Log action in
combination with other actions.
Prioritizing Actions
Outbound traffic filters for WAN protocols also include the following actions for
directing matching traffic into circuit-based protocol priority queues:
• High — Packets that match the filter criteria and ranges are processed in the
high queue.
• Low — Packets that match the filter criteria and ranges are processed in the
low queue.
• Length — For packets that match the filter criteria, the packet length
determines the priority queue into which it is placed.
Note: Specify the Log action only to record abnormal events; otherwise, the
Events log will fill up with filtering messages, leaving no room for critical log
messages.
Note: Site Manager does not support protocol prioritization on outbound LAN
traffic filters.
Comentários a estes Manuais