Week 10 · Lab

LAB: ACL Configuration

You have learned what ACLs are, how wildcard masks work, and why order and placement matter. Now you type it all onto a real (or simulated) router: a standard ACL that blocks one subnet at the destination edge, and an extended ACL near the source that stops a specific service. You will prove each rule with ping and read the verdict back from show access-lists.

CCNA 200-301 Domain 5.0 Security Fundamentals Verified 2026-10-11
Learning objectives
Part 1

Overview and goal

Two LANs face each other across a single router’s interfaces. The goal is controlled in three stages: first prove the network works with no ACLs; then add a standard ACL that blocks the entire management subnet from the server LAN; finally add an extended ACL that permits web traffic (HTTP/HTTPS) and denies Telnet to the server while leaving everything else intact. If an ACL change breaks a host that should still pass traffic, your first suspect is direction, your second is ordering, and your third is the missing catch-all.

Definition — this lab’s terms A standard ACL filters by source only and sits near the destination. An extended ACL filters by source, destination, protocol, and port and sits near the source. Both end with implicit deny, so every “allow everything else” policy needs an explicit permit any.
In this lesson · select a part to jump

Key ideas & exam traps · select one

Part 2

Topology

Host A 192.168.1.10 Host M 192.168.2.10 R1 S1 Server 192.168.1.1 /24 (Gi0/0) 10.10.10.1 /24 (Gi0/1) Gi0/0 Gi0/1
The router R1 joins the user LANs to the server LAN. All ACL work happens on R1’s two interfaces; S1 is a plain access switch.
Part 3

Addressing plan

DeviceInterfaceAddress / maskGateway
Host ANIC192.168.1.10 / 255.255.255.0192.168.1.1
Host MNIC192.168.2.10 / 255.255.255.0192.168.2.1
R1Gi0/0192.168.1.1 / 255.255.255.0—
R1Gi0/110.10.10.1 / 255.255.255.0—
ServerNIC10.10.10.10 / 255.255.255.010.10.10.1

Wildcard masks: /24 → 0.0.0.255. The individual hosts use host syntax in the extended ACL.

Reference table · select a row

Part 4

Step 1 — Build and verify connectivity

Start from scratch. Configure the addresses above and a default gateway on each host, then confirm both hosts can reach the server before any ACL exists:

R1(config)# interface gigabitEthernet0/0
R1(config-if)# ip address 192.168.1.1 255.255.255.0
R1(config-if)# no shutdown
R1(config-if)# exit
R1(config)# interface gigabitEthernet0/1
R1(config-if)# ip address 10.10.10.1 255.255.255.0
R1(config-if)# no shutdown
R1(config-if)# end

! From Host A and Host M: the server must answer both pings
C:\> ping 10.10.10.10
Reply from 10.10.10.10: bytes=32 time<1ms TTL=127
Baseline first A functioning network before you add the ACL is worth a hundred guesses later. If a test fails after configuration, you can isolate “the ACL broke it” from “it never worked”.
Part 5

Step 2 — Standard ACL: block one subnet

Policy: 192.168.2.0/24 (Host M’s subnet) may not reach the server LAN at all; 192.168.1.0/24 continues normally. A standard ACL knows only the source, so the textbook placement is on R1’s Gi0/1, outbound — the last router before the server LAN:

R1(config)# access-list 10 deny 192.168.2.0 0.0.0.255
R1(config)# access-list 10 permit any

R1(config)# interface gigabitEthernet0/1
R1(config-if)# ip access-group 10 out
R1(config-if)# end

Note the order: the specific deny comes first, the permit any second. Reverse them and the permit swallows everything. The list is deliberately on Gi0/1: traffic leaving toward the server LAN is filtered; traffic from 192.168.2.0 to anywhere else is untouched.

Part 6

Step 3 — Test the standard ACL

Test from both sides of the rule:

! Host M (192.168.2.10) is blocked
C:\> ping 10.10.10.10
Request timed out.
Request timed out.

! Host A (192.168.1.10) still passes
C:\> ping 10.10.10.10
Reply from 10.10.10.10: bytes=32 time<1ms TTL=127

R1# show access-lists
Standard IP access list 10
    10 deny   192.168.2.0, wildcard bits 0.0.0.255 (matches 4)
    20 permit any (matches 12)
Warning If Host M still pings, you are almost certainly inspecting the wrong exit. The ACL must point out Gi0/1 (toward the server), not Gi0/0 (toward the users). Run show ip interface to confirm which interface actually carries the rule.
Part 7

Step 4 — Extended ACL: control the web ports

New policy: the server provides HTTP and HTTPS to everyone; Telnet to the server is forbidden from the user side; everything else is permitted. An extended ACL can see the destination and ports, so it belongs inbound on Gi0/0 — close to the sources — where the unwanted Telnet traffic is killed before it reaches the server LAN:

! Remove the standard test ACL first, or disable it on the interface
R1(config)# interface gigabitEthernet0/1
R1(config-if)# no ip access-group 10 out
R1(config-if)# exit

R1(config)# access-list 101 deny tcp any host 10.10.10.10 eq 23
R1(config)# access-list 101 permit tcp any host 10.10.10.10 eq 80
R1(config)# access-list 101 permit tcp any host 10.10.10.10 eq 443
R1(config)# access-list 101 permit icmp any any
R1(config)# access-list 101 permit ip any any

R1(config)# interface gigabitEthernet0/0
R1(config-if)# ip access-group 101 in
R1(config-if)# end

Read each line: deny Telnet (23) to the server; permit HTTP (80) and HTTPS (443); permit ICMP so ping still works for testing; and the final permit ip any any explicitly re-instates everything else that implicit deny would otherwise remove. Order matters absolutely — the deny must precede the broad permits for the same destination.

Part 8

Step 5 — Verify with show access-lists

Now exercise every rule and read the counters. Even for routers without a Telnet client, the pattern holds: ping tests ICMP, an HTTP request tests port 80, and a crafted TCP test to port 23 (or connecting from a host) should be refused:

R1# show access-lists
Extended IP access list 101
    10 deny tcp any host 10.10.10.10 eq telnet (3 matches)
    20 permit tcp any host 10.10.10.10 eq www (5 matches)
    30 permit tcp any host 10.10.10.10 eq 443 (7 matches)
    40 permit icmp any any (4 matches)
    50 permit ip any any (16 matches)

R1# show ip interface gigabitEthernet0/0
GigabitEthernet0/0 is up, line protocol is up
  Inbound  access list is 101
  Outgoing access list is not set
TestExpectedCounter you check
ping from Host A to 10.10.10.10Reply (ICMP permitted)Line 40 increases
Web browser to http://10.10.10.10Page loadsLine 20 increases
Telnet 10.10.10.10 from Host MConnection refused / no promptLine 10 increases
ping from Host M to 10.10.10.10Reply (ICMP is open to all)Line 40 increases

Zero on a line that should be rising is the clue: the packet is either hitting an earlier line (reorder), or crossing a different interface/direction than the one you bound (re-verify).

Exam tip — the ICMP surprise Because this lab permits ICMP explicitly, ping tests succeed even for blocked subnets in the extended phase. Never assume “ping works” proves “the service works” — that is exactly the trap the exam sets: ICMP permitted, Telnet denied, and the candidate tests with ping alone.
Part 9

Troubleshooting guide

Key terms

The vocabulary you need

Every term below appears in the lesson text above. Select one to read its definition, then use the quiz at the end to check what stuck.

Key terms · select a term

Part 10 · Your turn

Review

Check what you have learned with these review questions.

Review · 5 questions

Sources

Sources & references

  1. Cisco. CCNA (200-301) Exam Topics. cisco.com.
  2. IETF. Request for Comments (RFCs). rfc-editor.org.
  3. IANA. Internet Assigned Numbers Authority registries. iana.org.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.