ACL Drill Set 2

By certskills July 24, 2015 09:05

Here’s another ACL drill set. What’s that? Check out this post that explains the details. No stopwatch, no speed requirement for these, unlike the subnetting speed practice. Just focus on getting the right answer. For this post, you will create a small but complete ACL, with one or more ACEs (commands) per ACL. This post has three such exercises. Questions are below the fold!

First, use this same figure as the backdrop:

Here are the requirements. Your job: create a numbered ACL, with one or more lines, and enabled on the correct interface, to implement the requirements.

1) Host C ( attempts to connect to Telnet server S3 ( Your ACL will be applied outbound on R2’s S0/0/1 interface. Permit traffic from host C to telnet services on S3. However, also prevent access from Host C to Telnet server S4 (, as well as telnet services on all servers in that same subnet. Permit all other traffic.

2) Host B ( pings the four servers in the network: S1 (, S2 (, S3 (, and S4 ( The configuration will enabled an ACL on R1’s F0/0 interface, inbound. Configure an ACL so that host B can still successfully ping servers in the same subnets as S1 and S4, but filter so that the pings to servers in the same subnet as S2 and S3 fail.

3) Repeat #1, but for an ACL that will be placed on R1’s F0/1 as an inbound ACL, and match all packets in Host C’s subnet and in servers S3’s subnet.

Answer to an Earlier STP Question
Answers: ACL Drill Set 2
By certskills July 24, 2015 09:05
Write a comment


  1. RN March 3, 19:15

    Hi Wendell,

    Aren’t B and S1 suppose to be on the same subnet?



    Reply to this comment
    • CCENTSkills March 7, 10:30

      They are indeed! 🙂 There’s no need to permit traffic going to the subnet where B and S1 reside, because the router doesn’t process those packets.

      Reply to this comment
View comments

Write a comment

Comment; Identify w/ Social Media or Email


Subscribe to our mailing list and get interesting stuff and updates to your email inbox.

Thank you for subscribing.

Something went wrong.