In HPE Aruba Networking AOS-10 and AOS-8 architectures, user-role access control lists (ACLs) are processed sequentially using top-down first-match evaluation logic. Once a packet matches all criteria specified in an ACE (source, destination, protocol, and port), the defined action (permit or deny) is immediately executed, bypassing all subsequent rules.
Evaluating Packet 1: The client initiates a TCP connection on port 8086 destined for 10.0.3.75.
* Rule 1 matches DHCP (`svc-dhcp`), which does not apply.
* Rule 2 targets `host1` (10.0.6.8) for DNS, which does not match.
* Rule 3 targets `net1` (10.0.0.0/22, covering 10.0.0.0 to 10.0.3.255) for HTTPS (TCP 443); while the destination IP falls within the range, the destination port 8086 does not match.
* Rule 4 matches traffic to `net2` (10.0.3.0/24, covering 10.0.3.0 to 10.0.3.255) on `tcp 8086`. Because 10.0.3.75 falls within 10.0.3.0/24 and the port matches, the packet is explicitly permitted.
Evaluating Packet 2: The client sends HTTPS traffic (TCP 443) destined for 10.0.7.24.
* Rules 1 and 2 do not match.
* Rule 3 matches `net1` (10.0.0.0/22), which covers 10.0.0.0–10.0.3.255; 10.0.7.24 falls outside this subnet.
* Rule 4 matches TCP 8086, failing on port.
* Rule 5 matches destination `net3` (10.0.0.0/21, covering 10.0.0.0 to 10.0.7.255) for `any` service with an action of `deny`. Because 10.0.7.24 falls within 10.0.0.0/21, the packet hits this rule first and is dropped before reaching Rule 6.
Therefore, the first packet is permitted and the second is denied.
[References: AOS-10 Gateway Firewall Policies, Policy Enforcement Firewall (PEF), Netdestination and Service Aliases., , , ]