Using the
Filter Objects
Filter Objects
Filter objects define classes of traffic based on a combination of one or more attributes. IP traffic that matches the class of traffic defined by a filter gets processed by the policy that the filter is attached to. A filter can only be attached to multiple policies, but can only be attached to one policy per adapter. A filter is effectively ignored if it is not attached to any policy.
Table
Table | Attributes Associated with Filter Objects | |
|
|
|
Object Type |
| Attributes |
|
|
|
Filter |
| unique name |
|
| source addresses |
|
| destination addresses |
|
| source port numbers |
|
| destination port numbers |
|
| network protocol number (0x800 or 0x86DD) |
|
| transport protocol number (tcp or udp) |
|
| destination physical address |
|
| DSCP(s) |
|
| priority |
|
| status |
|
|
|
Filter Overlap
A filter is said to overlap another filter if:
—both filters are associated with the same adapter
—the priority attribute of the filter is of equal or greater priority than the other
—the filter defines a set of traffic that is a superset of the traffic defined by the other filter (complete overlap), or has an intersection with the traffic defined by the other filter (partial overlap)
30 | Chapter 2 |