SWRU455M February 2017 – October 2020 CC3120 , CC3120MOD , CC3130 , CC3135 , CC3135MOD , CC3220MOD , CC3220MODA , CC3220R , CC3220S , CC3220SF , CC3230S , CC3230SF , CC3235MODAS , CC3235MODASF , CC3235MODS , CC3235MODSF , CC3235S , CC3235SF
The filter ID contains the ID of the parent filter; filters can be organized in a tree hierarchy.
The parent filter can be from the same layer or a layer lower than the child filter.
The following defines the filter layer of each rule.
Filter layers: The header rules can be specified in a tree form, but the rules must also preserve a layered approach.
Therefore, a filter on a transport layer field (such as TCP or UDP source or destination ports) cannot be a parent of a filter on a MAC header field (such as frame type).
Table 12-6 presents which groups of header rule types can be parents of other header rule types. The general guideline is that the lower the communication layer to which the header rule filter applies, the more filters can depend on this filter.
When a filter contains a drop action, it cannot be a parent of any other filter, because if a packet is dropped the tree traversal is stopped.
Group | Rule Field | Can Be Parent of Rules from Group |
---|---|---|
A | FRAME_TYPE FRAME_SUBTYPE BSSID_ADDRESS MAC_SRC_ADDRESS MAC_DST_ADDRESS FRAME_LENGTH | A, B, C, D |
B | ETHER_TYPE IP_VERSION Multicast destination IPs (V4 and V6) L1_PAYLOAD | B, C, D |
C | Source IP (V4 and V6) Unicast destination IP (V4 and V6) IP PROTOCOL field (UDP, TCP, ICMP, IGMP, and so forth) | C, D |
D | Source port (UDP/TCP) Destination port (UDP/TCP) L4_PAYLOAD | D |