Labs · · 3 min read

Lab sec-03 - Extended ACL (Named)

Lab sec-03 - Extended ACL (Named) - PingLabz Labs article title card

Extended ACLs filter based on source IP, destination IP, protocol, source port, destination port, and various TCP flags. They are the workhorse ACL type in production. Named ACLs (vs numbered) give you a descriptive name and let you insert/remove entries by line number cleanly. This lab configures a named extended ACL on R1 to allow specific inbound traffic and deny everything else.

What you will learn

  • Named ACL syntax with ip access-list extended NAME
  • Matching by protocol (TCP, UDP, ICMP)
  • Matching destination ports (eq, gt, lt, range)
  • The established keyword for stateful-ish filtering
  • Where to apply extended ACLs (close to source)

What this lab does NOT cover

  • Reflexive ACLs (semi-stateful)
  • Object groups (organize ACL entries by name)
  • IPv6 ACL syntax

Topology

Download the CCNA Base Topology .yaml

3 iol-xe routers + 1 alpine + 1 ioll2-xe managed switch + 1 unmanaged switch.

Download CCNA Base Topology

Read next

Terminal card showing a repeating CDP native VLAN mismatch log naming Ethernet0/0 native VLAN 1 against SW2 Ethernet0/0 native VLAN 99
VLANs ·

Native VLAN Mismatch: Read the CDP Log, Fix the Trunk

%CDP-4-NATIVE_VLAN_MISMATCH hands you both interfaces and both native VLANs in one line. The real damage is underneath it: untagged frames get re-homed at the trunk boundary and two VLANs quietly become one. Captured live on IOS XE 17.18.2 in CML.