Download PNETLab Platform
PNETLAB Store
PNETLab.com
Implement IPv4 ACLs
Topology
Addressing Table
Device Interface IP Address Subnet Mask Default Gateway
E0/0 192.168.13.1 255.255.255.252 N/A
R1
R1
E0/1 192.168.1.1 255.255.255.0 N/A
E0/0 192.168.13.2 255.255.255.252 N/A
R3 E0/1 192.168.2.1 255.255.255.0 N/A
R3
R3
Loopback0 192.168.3.1 255.255.255.0 N/A
D1 VLAN 1 192.168.1.2 255.255.255.0 N/A
D2 VLAN 1 192.168.2.2 255.255.255.0 N/A
PC1 NIC 192.168.1.10 255.255.255.0 192.168.1.1
PC2 NIC 192.168.2.10 255.255.255.0 192.168.2.1
1
Download PNETLab Platform
PNETLAB Store
PNETLab.com
Objectives
Part 1: Build the Network and Configure Basic Device Settings
Part 2: Verify Initial Connectivity
Part 3: Implement Standard ACLs on R3
Part 4: Implement a Named Extended ACL from Area 1 to Area 2
Part 5: Implement a Named Extended ACL from Area 2 to Area 1
Part 6: Implement a Port ACL on D2
Part 7: Implement a VLAN ACL on D2
Background / Scenario
Access control lists (ACLs) are sequential lists of individual access control entries (ACEs) that permit
or deny packets based on predefined conditional matching statements. Finding a match in an ACL
starts at the top with the lowest sequence number and proceeds down the list (higher sequence
numbers) until a matching ACE is found. When a match is found, the preset action (permit or deny) is
applied and processing stops. At the end of every ACL is an implicit deny “any” ACE, which denies all
packets that did not match prior ACEs.
ACLs can be used for packet classification with quality of service (QoS), Network Address Translations
(NAT), and numerous other services.
In this lab, you will configure three different types of ACLs. Router ACL (RACL) is the most common
ACL is the IP-based ACL that are applied to routed interface. The ACL that applies to traffic entering
and leaving a VLAN is a VLAN ACL (VACL). The VACLs can filter traffic based on MAC addresses, IP
addresses, and port numbers. A VACL that is applied to an individual port inside a VLAN is a port-
based ACL (PACL).
The focus of this lab is using IPv4 ACLs for packet filtering.
Required Resources
2 Routers (Cisco 4221 with Cisco IOS XE Release 16.9.4 universal image or comparable)
2 Switches (Cisco 3650 with Cisco IOS XE Release 16.9.4 universal image or comparable)
2 PC (Choice of operating system with a terminal emulation program and a packet capture utility
installed)
Console cables to configure the Cisco IOS devices via the console ports
Ethernet cables as shown in the topology
2
Download PNETLab Platform
PNETLAB Store
PNETLab.com
Instructions
Part 1: Build the Network and Configure Basic Device Settings
In Part 1, you will set up the network topology and configure basic settings and interface addressing
on devices.
Step 1: Cable the network as shown in the topology.
Attach the devices as shown in the topology diagram, and cable as necessary.
Step 2: Configure basic settings for each device.
a. Console into each device, enter global configuration mode, and apply the basic settings. The
startup configurations for each device are provided below.
Open configuration window
Router R1
hostname R1
no ip domain lookup
username admin privilege 15 algorithm-type scrypt secret
cisco123
banner motd # R1, Lab Access Control Lists #
line con 0
exec-timeout 0 0
logging synchronous
exit
interface e0/1
ip address 192.168.1.1 255.255.255.0
no shutdown
exit
interface e0/0
ip address 192.168.13.1 255.255.255.252
no shutdown
exit
router ospf 1
router-id 0.0.0.1
network 192.168.1.0 0.0.0.255 area 1
network 192.168.13.0 0.0.0.3 area 0
exit
line vty 0 4
login local
3
Download PNETLab Platform
PNETLAB Store
PNETLab.com
transport input all
end
Router R3
hostname R3
no ip domain lookup
username admin privilege 15 algorithm-type scrypt secret
cisco123
banner motd # R3, Lab Access Control Lists #
line con 0
exec-timeout 0 0
logging synchronous
exit
interface Loopback0
ip address 192.168.3.1 255.255.255.0
exit
interface e0/1
ip address 192.168.2.1 255.255.255.0
no shutdown
exit
interface e0/0
ip address 192.168.13.2 255.255.255.252
no shutdown
exit
router ospf 1
router-id 0.0.0.3
network 192.168.2.0 0.0.0.255 area 2
network 192.168.3.0 0.0.0.255 area 0
network 192.168.13.0 0.0.0.3 area 0
exit
line vty 0 4
login local
transport input all
end
4
Download PNETLab Platform
PNETLAB Store
PNETLab.com
Switch D1
hostname D1
no ip domain lookup
username admin privilege 15 algorithm-type scrypt secret
cisco123
banner motd # D1, Lab Access Control Lists #
line con 0
exec-timeout 0 0
logging synchronous
exit
interface vlan 1
ip address 192.168.1.2 255.255.255.0
no shut
exit
ip default-gateway 192.168.1.1
line vty 0 4
login local
transport input telnet
end
Switch D2
hostname D2
no ip domain lookup
username admin privilege 15 algorithm-type scrypt secret
cisco123
banner motd # D2, Lab Access Control Lists #
line con 0
exec-timeout 0 0
logging synchronous
exit
interface vlan 1
ip address 192.168.2.2 255.255.255.0
no shut
exit
5
Download PNETLab Platform
PNETLAB Store
PNETLab.com
ip default-gateway 192.168.2.1
line vty 0 4
login local
transport input telnet
end
b. Set the clock on each device to UTC time.
c. Save the running configuration to startup-config.
d. Configure and verify the IP address on PC1 and PC2.
e. Verify ICMP connectivity between all devices and PCs.
Close configuration window
Part 2: Verify Initial Connectivity
It is always advisable to test network connectivity and services before applying ACL filtering. This
ensures that the network is fully functional, and that the loss of connectivity or functionality is due to
the applied ACLs and not a pre-existing network issue.
When testing TCP connectivity some services will prompt for a username/password. The pre-
configured username is admin and password is cisco123.
Step 1: Test Telnet connectivity.
From both PCs test Telnet connectivity to all devices. You should be successful. Troubleshoot as
needed.
PC1#telnet 192.168.1.1
Trying 192.168.1.1 ... Open R1, Lab Access Control Lists
User Access Verification
Username: admin
Password:
R1#show ip interface brief
R1#show ip interface brief
Interface IP-Address OK? Method Status Protocol
Ethernet0/0 192.168.13.1 YES manual up up
Ethernet0/1 192.168.1.1 YES manual up up
Ethernet0/2 unassigned YES unset administratively down down
Ethernet0/3 unassigned YES unset administratively down down
6
Download PNETLab Platform
PNETLAB Store
PNETLab.com
Step 2: Test SSH connectivity.
From both PCs test SSH to R1. You should be successful. Troubleshoot as needed.
R1#ssh -l admin 192.168.1.1
Password:
R1, Lab Access Control Lists
R1#show ip interface brief
Interface IP-Address OK? Method Status Protocol
Ethernet0/0 192.168.13.1 YES manual up up
Ethernet0/1 192.168.1.1 YES manual up up
Ethernet0/2 unassigned YES unset administratively down down
Ethernet0/3 unassigned YES unset administratively down down
Part 3: Implement Standard ACLs on R3
A standard ACL is able to match traffic based on the source IP address. When filtering data traffic
using a standard ACL it is considered best practice to apply the ACL as close to the destination as
possible. ACLs can be configured using a name or number. The standard ACL number range is 1-99
and 1300-1999.
Step 1: Configure a numbered standard ACL on R3 and block data traffic from the
192.168.1.0 /24 network.
a. Create a numbered standard ACL using the number 99 to deny the source network of
192.168.1.0/24.
Open configuration window
R3(config)# access-list 99 deny 192.168.1.0 0.0.0.255
b. Then add a second ACE to permit all other traffic.
Note: 0.0.0.0 255.255.255.255 will be converted to the keyword “any”.
R3(config)# access-list 99 permit 0.0.0.0 255.255.255.255
Step 2: Apply the numbered standard ACL to the correct interface and in the correct
direction.
a. Apply the ACL to the G0/0/1 interface.
R3(config)# interface g0/0/1
R3(config-if)# ip access-group 99 ?
in inbound packets
out outbound packets
b. Specify outbound on G0/0/1 because the data traffic is originating from R1 and exiting G/0/1 to
access the 192.168.2.0/24 network.
R3(config-if)# ip access-group 99 out
R3(config-if)# end
7
Download PNETLab Platform
PNETLAB Store
PNETLab.com
Step 3: Verify that the numbered standard ACL is working properly.
a. From PC1, ping D2, A1, and PC2. The pings should fail. Notice the messages on PC1 is from R3.
b. Issue the show access-lists command on R3. The output shows packets matching the
sequence number 10.
R3# show access-lists
Standard IP access list 99
10 deny 192.168.1.0, wildcard bits 0.0.0.255 (12 matches)
20 permit any
c. Next, from PC1, ping the loopback on R3 at 192.168.3.1. The ping should be successful. This
verifies connectivity to resources on R3. However, ACL 99 denies access to the 192.168.2.0/24
network.
PC1#ping 192.168.3.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.3.1, timeout is 2 seconds: !!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/2 ms
d. Remove the access list from R3 and remove the ip access-group command from interface
G0/0/1 to provide connectivity to 192.168.2.0/24 network.
R3(config)# no access-list 99
R3(config)# interface g0/0/1
R3(config-if)# no ip access-group 99 out
e. Verify that PC1 can ping devices on the 192.168.2.0/24 network.
PC1#ping 192.168.2.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.2.10, timeout is 2 seconds:!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 2/2/3 ms
Step 4: Configure a named standard ACL to limit management traffic to R3.
Create a named standard ACL using the name MGMT-TRAFFIC. The ACL should only permit Telnet
access to the management plane on R3 from PC1. Explicitly deny access from any other IPv4
destination and log the attempts.
R3(config)# ip access-list standard MGMT-TRAFFIC
R3(config-std-nacl)# permit host 192.168.1.10
R3(config-std-nacl)# deny any log
R3(config-std-nacl)# exit
8
Download PNETLab Platform
PNETLAB Store
PNETLab.com
Step 5: Apply the named standard ACL to the correct interface and in the correct
direction.
Use the access-class command to apply the MGMT-TRAFFIC ACL to all inbound vty lines on R3.
Outbound Telnet connections from R3 will still be allowed.
R3(config)# line vty 0 4
R3(config-line)# access-class MGMT-TRAFFIC in
R3(config-line)# end
Step 6: Verify that the named standard ACL is working properly.
a. Test the ACL by initiating a Telnet session from PC1 to the Loopback address (192.168.3.1) on
R3. The results should be successful. Repeat the test from PC2. Telnet connectivity from PC2
should be denied.
b. On R3, you should see the console messages shown below. The first message shows a login
success and the second message shows a denial.
R3#
*Feb 28 20:36:29.495: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: admin]
[Source: 192.168.1.10] [localport: 23] at 20:36:29 UTC Fri Feb 28 2020
*Feb 28 20:37:10.647: %SEC-6-IPACCESSLOGS: list MGMT-TRAFFIC denied
192.168.2.10 1 packet
c. Issue the show access-lists on R3 to view the packet “matches” from each ACE.
R3# show access-lists
Standard IP access list MGMT-TRAFFIC
10 permit 192.168.1.10 (2 matches)
20 deny any log (3 matches)
Close configuration window
Note: During testing, the first packet in a flow will trigger a syslog message. Enabling logging with
the log option in the deny any statement provides insight into the amount of denied traffic.
Unfortunately, ACL logging can be CPU-intensive and can negatively affect other functions of the
network device. There are two primary factors that contribute to the CPU load increase from ACL
logging: process switching of packets that match log-enabled access control entries (ACEs), and
the generation and transmission of log messages. Care should be taken when using the log
option in a production network.
Part 4: Implement a Named Extended ACL from Area 1 to Area 2
Extended ACLs can filter traffic based on more than just source address. Extended ACLs can filter on
protocol, source, and destination IP addresses, and source and destination port numbers. Extended
ACLs may also be used to filter IP packets with header options.
When filtering data traffic using an extended ACL, it is considered best practice to apply the ACL as
close to the source as possible. You can configure both numbered and named extended ACLs. Part 4
of this lab uses a named extended ACL. Review the ACL policy that will be implemented using a
named extended ACL.
On R1, use the following requirements to create a named extended ACL that will filter traffic
originating from OSPF area 1 destined to OSPF area 2. As a result, all traffic from area 2 destined to
area 1 will also be filtered:
Name the extended ACL AREA1_TO_AREA2.
Deny any IP traffic from PC1 with a time-to-live (TTL) value less than 25.
Permit PC1 to send ICMP echo packets to 192.168.2.0/24.
9
Download PNETLab Platform
PNETLAB Store
PNETLab.com
Permit PC1 Telnet access to D2.
Permit 192.168.1.0/24 network to SSH to A1.
Permit PC1 to send HTTP traffic to A1.
Permit PC1 to send HTTPS traffic to A1.
Explicitly deny all other traffic.
Step 1: Configure the named extended ACL on R1.
a. Enter the following to configure the ACL.
Open configuration window
R1(config)# ip access-list extended AREA1_TO_AREA2
R1(config-ext-nacl)# deny ip host 192.168.1.10 any ttl lt 25
R1(config-ext-nacl)# permit icmp host 192.168.1.10 192.168.2.0
0.0.0.255 echo
R1(config-ext-nacl)# permit tcp host 192.168.1.10 host
192.168.2.2 eq 23
R1(config-ext-nacl)# permit tcp 192.168.1.0 0.0.0.255 host
192.168.2.3 eq 22
R1(config-ext-nacl)# permit tcp host 192.168.1.10 host
192.168.2.3 eq 80
R1(config-ext-nacl)# permit tcp host 192.168.1.10 host
192.168.2.3 eq 443
R1(config-ext-nacl)# deny ip any any
R1(config-ext-nacl)# end
b. Issue the show access-list command to verify the creation of the extended named ACL. Notice
the sequence numbers and the top (lower sequence number) to bottom (higher sequence
number) processing of each ACE. Also notice some of the port numbers have been changed to
the IOS keywords. For example, port 80 is now www in the IOS.
R1# show access-lists
Extended IP access list AREA1_TO_AREA2
10 deny ip host 192.168.1.10 any ttl lt 25
20 permit icmp host 192.168.1.10 192.168.2.0 0.0.0.255 echo
30 permit tcp host 192.168.1.10 host 192.168.2.2 eq telnet
40 permit tcp 192.168.1.0 0.0.0.255 host 192.168.2.3 eq 22
50 permit tcp host 192.168.1.10 host 192.168.2.3 eq www
60 permit tcp host 192.168.1.10 host 192.168.2.3 eq 443
70 deny ip any any
Note: Sequence 70 essentially filters all other traffic that does not originate from area 1.
Step 2: Apply the named extended ACL to the correct interface and in the correct
direction.
a. Apply the named ACL to the G0/0/1 interface on R1. Because traffic originates from area 1, apply
the ACL inbound to R1
R1(config)# interface e0/1
R1(config-if)# ip access-group AREA1_TO_AREA2 in
R1(config-if)# end
10
Download PNETLab Platform
PNETLAB Store
PNETLab.com
Step 3: Verify that the AREA1_TO_AREA2 named extended ACL is working properly.
a. Test the first two lines of the ACL. From PC1, you should be able to successfully ping PC2.
b. From PC1, ping PC2 again, but this time set the TTL value to 20 inside the IP header on PC1.
Use the following command on PC1 to set the TTL to 20 for the ICMP packet.
C:\> ping 192.168.2.10 –i 20
The ICMP packets with a TTL value of 20 should be dropped by R1, which is the area border
router (ABR) for area 1. R1 sends error messages to PC1.
c. Continue to test each individual ACE within the ACL.
o From PC1, you should be able to successfully access D2 via Telnet. However, accessing any
other device in area 2 via Telnet should be denied.
o From any device in area 1, you should be able to SSH to A1. However, accessing any other
device on area 2 via SSH should be denied.
o From PC1, you should be able to access the web interface on A1 using either HTTP or
HTTPS. However, all other attempts to access other devices using HTTP and HTTPS should
time out.
d. After testing each ACE, issue the show access-list command. Notice that each ACE has
matches. Your match counts will be different.
R1# show access-lists
Extended IP access list AREA1_TO_AREA2
10 deny ip host 192.168.1.10 any ttl lt 25 (62 matches)
20 permit icmp host 192.168.1.10 192.168.2.0 0.0.0.255 echo (12 matches)
30 permit tcp host 192.168.1.10 host 192.168.2.2 eq telnet (31 matches)
40 permit tcp 192.168.1.0 0.0.0.255 host 192.168.2.3 eq 22 (21 matches)
50 permit tcp host 192.168.1.10 host 192.168.2.3 eq www (15 matches)
60 permit tcp host 192.168.1.10 host 192.168.2.3 eq 443 (92 matches)
70 deny ip any any (49 matches)
Part 5: Implement a Named Extended ACL from Area 2 to Area 1
In this Part, you will configure and verify a named extended ACL to permit specific returning traffic
from area 2. To do this, you will now configure the addressing and port numbers from area 2 as the
source addresses and source ports. Additionally, the established keyword will be set on returning
TCP connections to increase security.
Step 1: Configure the named extended ACL on R1.
a. Use this filtered output from the show run command below to configure the named extended
ACL AREA2_TO_AREA1 on R1.
R1# show run | s AREA2_TO_AREA1
ip access-list extended AREA2_TO_AREA1
permit icmp 192.168.2.0 0.0.0.255 host 192.168.1.10 echo-reply
permit tcp host 192.168.2.2 eq telnet host 192.168.1.10 established
permit tcp host 192.168.2.3 eq 22 192.168.1.0 0.0.0.255 established
permit tcp host 192.168.2.3 eq www host 192.168.1.10 established
permit tcp host 192.168.2.3 eq 443 host 192.168.1.10 established
deny ip any any log
11
Download PNETLab Platform
PNETLAB Store
PNETLab.com
b. Verify your configuration by entering the same show run command. Your output should be same
as shown above.
c. Next, apply the ACL to the G/0/1 interface in the outgoing direction. Because traffic originated
from area 1 and is returning from area 2, configure the ACL going outbound on the G/0/1
interface towards area 1.
R1(config)# interface e0/1
R1(config-if)# ip access-group AREA2_TO_AREA1 out
R1(config-if)# end
Step 2: Verify that the AREA2_TO_AREA1 named extended ACL is working properly.
a. Repeat the tests from Part 4, Step 4. The return traffic permitted in the ACL AREA2_TO_AREA1
should be successful.
b. Issue the show ip access-list AREA2_TO_AREA1 command on R1 to see the matches for the
return traffic from area 2.
R1# show access-lists AREA2_TO_AREA1
Extended IP access list AREA2_TO_AREA1
10 permit icmp 192.168.2.0 0.0.0.255 host 192.168.1.10 echo-reply (4 matches)
20 permit tcp host 192.168.2.2 eq telnet host 192.168.1.10 established (36
matches)
30 permit tcp host 192.168.2.3 eq 22 192.168.1.0 0.0.0.255 established (23
matches)
40 permit tcp host 192.168.2.3 eq www host 192.168.1.10 established (13
matches)
50 permit tcp host 192.168.2.3 eq 443 host 192.168.1.10 established (26
matches)
60 deny ip any any log
Note: The established option allows only TCP responses to traffic that originates from area 1
(192.168.1.0/24) to return. A match occurs if the returning TCP segment has either the ACK or
reset (RST) bit set. Either of these bits indicates that the packet belongs to an established
connection. Therefore, when filtering return traffic, the source port number must be checked.
c. To verify that both ACLs are applied to the G0/0/1 interface on R1, issue the following filtered
show ip interface command.
R1# show ip interface e0/1 | s AREA
Outgoing access list is AREA2_TO_AREA1
Inbound access list is AREA1_TO_AREA2
Close configuration window
Part 6: Implement a Port ACL on D2
Port ACLs (PACLs) are similar to the router ACLs (RACLs) configured previously in this lab.
However, PACLs are supported on Layer 2 switchports. PACLs can be implemented using standard
or extended ACLs but can only be applied inbound. The processing of a PACL is done before a VLAN
ACL (VACL) and RACL.
Step 1: Configure a PACL on D2 using the following requirements:
On D2, create an extended numbered PACL on port 23 which has the following requirements:
o Deny all ICMP messages sent to 192.168.2.3.
o Deny Telnet access to 192.168.2.2.
12
Download PNETLab Platform
PNETLAB Store
PNETLab.com
o Permit all other traffic.
The configuration is as follows:
Open configuration window
D2(config)# access-list 123 deny icmp any host 192.168.2.3
D2(config)# access-list 123 deny tcp any host 192.168.2.2 eq 23
D2(config)# access-list 123 permit ip any any
Step 2: Apply the PACL to an interface on D2.
On D2, apply the ACL inbound on G1/0/23.
D2(config)# interface e0/1
D2(config-if)# ip access-group 123 in
D2(config-if)# end
Step 3: Verify that the PACL is working properly.
From PC2 test each ACE within the PACL.
a. A ping from PC2 to A1 should not be successful. However, a ping from PC2 to D2 should be
successful.
b. Access via Telnet from PC2 to D2 should fail. However, access via Telnet and SSH from PC2 to
A1 should be successful.
c. On D2 issue the show run | s access-list command. Notice the numbered ACL 123 configured
earlier is now converted into the format for an extended named ACL.
D2# show run | s access-list
ip access-list extended 123
deny icmp any host 192.168.2.3 echo
deny tcp any host 192.168.2.2 eq telnet
permit ip any any
close configuration window
Part 7: Implement a VLAN ACL on D2
VLAN ACLs (VACLs) control access to the VLAN of all packets, both bridged and routed. Packets
can enter the VLAN via a Layer 2 switchport or through a Layer 3 interface after being routed. Similar
to PACLs, VACLs can filter traffic within the same VLAN.
Step 1: Configure a VACL on D2 using the following requirements:
Create an extended VACL to support the following requirements:
o Deny pings from 192.168.2.2 to 192.168.2.3.
o Deny Telnet from 192.168.2.2 to 192.168.2.3.
o Permit all other traffic.
a. On D2 create an extended ACL named D2ACL. Notice that in this first configuration step, the
traffic to be blocked is defined in the ACL with a permit statement. That is because in Step1c,
you will configure a vlan access-map to match this permitted traffic and then drop it. All denied
traffic will not match the first vlan access -map statement, but will match the second vlan
access -map statement in Step1d. This second statement will forward all other traffic.
D2(config)# ip access-list extended D2ACL
D2(config-ext-nacl)# permit icmp host 192.168.2.2 host
192.168.2.3
13
Download PNETLab Platform
PNETLAB Store
PNETLab.com
D2(config-ext-nacl)# permit tcp host 192.168.2.2 host 192.168.2.3
eq 22
D2(config-ext-nacl)# deny ip any any
D2(config-ext-nacl)# exit
b. On D2, configure the VLAN access map with the name VACL and sequence 10. Within the VLAN
access map match the access list named D2ACL. Then set the action to drop any packets being
permitted by the D2ACL.
D2(config)# vlan access-map VACL 10
D2(config-access-map)# match ip address D2ACL
D2(config-access-map)# action drop
D2(config-access-map)# exit
c. Like all ACLs, there is an implied “deny any” with a VLAN ACL. To prevent all traffic from being
dropped, create a sequence 20 for the same VLAN access map. Next, set the action to forward.
D2(config)# vlan access-map VACL 20
D2(config-access-map)# action forward
D2(config-access-map)# exit
Step 2: Apply the VACL to a VLAN filter.
To apply a VACL, use the vlan filter vlan-access-map-name vlan-list vlan-list command. The vlan-
list can be a single VLAN, a contiguous range of VLANs (7–10), or a comma separated list of multiple
VLANs (4,9–11,17). Notice a direction is not required because the VLAN filter applies to both intra-
VLAN in inter-VLAN traffic.
D2(config)# vlan filter VACL vlan-list 1
Step 3: Verify that the VACL is working properly.
From D2, test each ACE within the VACL.
a. From D2, ping A1. The ping should fail.
D2# ping 192.168.2.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.2.10, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
b. From D2, use Telnet to access A1. The connection should time out.
D2# telnet 192.168.2.3
Trying 192.168.2.3 ...
% Connection timed out; remote host not responding
c. From D2, ping PC10. The ping should be successful.
D2# ping 192.168.2.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.2.10, timeout is 2
seconds:
!!!!!
14
Download PNETLab Platform
PNETLAB Store
PNETLab.com
Success rate is 100 percent (5/5), round-trip min/avg/max = 2/2/3
ms
d. From D2, SSH to A1. The connection should be successful. Exit the SSH session.
D2# ssh -l admin 192.168.2.3
Password:
A1, Lab Access Control Lists A1#
A1# exit
[Connection to 192.168.2.3 closed by foreign host]
D2#
e. Use the show vlan access-map and show access-list commands to view the VACL
configuration.
D2# show vlan access-map
Vlan access-map "VACL" 10
Match clauses:
ip address: D2ACL
Action:
drop
Vlan access-map "VACL" 20
Match clauses:
Action:
forward
D2# show access-lists D2ACL
Extended IP access list D2ACL
10 permit icmp host 192.168.2.2 host 192.168.2.3
20 permit tcp host 192.168.2.2 host 192.168.2.3 eq telnet
30 deny ip any any
Close configuration window
15
