Match order

The rules in an ACL are sorted in a specific order. When a packet matches a rule, the device stops the match process and performs the action defined in the rule. If an ACL includes overlapping or conflicting rules, the matching result and action to take depend on the rule order.

The following ACL match orders are available:


[NOTE: ]

NOTE:

The match order of user-defined or WLAN ACLs can only be config.


ACL category

Sequence of tie breakers

IPv4 basic ACL

  1. VPN instance

  2. More 0s in the source IP address wildcard (more 0s means a narrower IP address range)

  3. Rule configured earlier

IPv4 advanced ACL

  1. VPN instance

  2. Protocol number

  3. More 0s in the source IP address wildcard mask

  4. More 0s in the destination IP address wildcard

  5. Narrower TCP/UDP service port number range

  6. Rule configured earlier

IPv6 basic ACL

  1. VPN instance

  2. Longer prefix for the source IP address (a longer prefix means a narrower IP address range)

  3. Rule configured earlier

IPv6 advanced ACL

  1. VPN instance

  2. Protocol number

  3. Longer prefix for the source IPv6 address

  4. Longer prefix for the destination IPv6 address

  5. Narrower TCP/UDP service port number range

  6. Rule configured earlier

Ethernet frame header ACL

  1. More 1s in the source MAC address mask (more 1s means a smaller MAC address)

  2. More 1s in the destination MAC address mask

  3. Rule configured earlier

A wildcard mask, also called an inverse mask, is a 32-bit binary and represented in dotted decimal notation. In contrast to a network mask, the 0 bits in a wildcard mask represent "do care" bits, and the 1 bits represent "don’t care" bits. If the "do care" bits in an IP address are identical to the "do care" bits in an IP address criterion, the IP address matches the criterion. All "don’t care" bits are ignored. The 0s and 1s in a wildcard mask can be noncontiguous. For example, 0.255.0.255 is a valid wildcard mask.


[NOTE: ]

NOTE:

A simple ACL can include only one rule.