9.2.2.7 Lab - Configuring and Verifying Standard ACLs
9.2.2.7 Lab - Configuring and Verifying Standard ACLs
Topology
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 1 of 9
Addressing Table
Device
R1
Interface
IP Address
Subnet Mask
Default Gateway
G0/1
192.168.10.1
255.255.255.0
N/A
Lo0
192.168.20.1
255.255.255.0
N/A
S0/0/0 (DCE)
10.1.1.1
255.255.255.252
N/A
S0/0/0
10.1.1.2
255.255.255.252
N/A
S0/0/1 (DCE)
10.2.2.2
255.255.255.252
N/A
Lo0
209.165.200.225
255.255.255.224
N/A
G0/1
192.168.30.1
255.255.255.0
N/A
Lo0
192.168.40.1
255.255.255.0
N/A
S0/0/1
10.2.2.1
255.255.255.252
N/A
S1
VLAN 1
192.168.10.11
255.255.255.0
192.168.10.1
S3
VLAN 1
192.168.30.11
255.255.255.0
192.168.30.1
PC-A
NIC
192.168.10.3
255.255.255.0
192.168.10.1
PC-C
NIC
192.168.30.3
255.255.255.0
192.168.30.1
ISP
R3
Objectives
Part 1: Set Up the Topology and Initialize Devices
Background / Scenario
Network security is an important issue when designing and managing IP networks. The ability to configure
proper rules to filter packets, based on established security policies, is a valuable skill.
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 2 of 9
Required Resources
3 Routers (Cisco 1941 with Cisco IOS Release 15.2(4)M3 universal image or comparable)
2 Switches (Cisco 2960 with Cisco IOS Release 15.0(2) lanbasek9 image or comparable)
2 PCs (Windows 7, Vista, or XP with terminal emulation program, such as Tera Term)
Console cables to configure the Cisco IOS devices via the console ports
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 3 of 9
Configure the management interface IP address as shown in the Topology and Addressing Table.
ospf 1
network 192.168.10.0 0.0.0.255 area 0
network 192.168.20.0 0.0.0.255 area 0
network 10.1.1.0 0.0.0.3 area 0
ospf 1
network 209.165.200.224 0.0.0.31 area 0
network 10.1.1.0 0.0.0.3 area 0
network 10.2.2.0 0.0.0.3 area 0
b. After configuring OSPF on R1, ISP, and R3, verify that all routers have complete routing tables listing all
networks. Troubleshoot if this is not the case.
From PC-C, ping PC-A and the loopback interface on R1. Were your pings successful?
d. From R3, ping PC-A and the loopback interface on R1. Were your pings successful?
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 4 of 9
a. Configure the ACL on R3. Use 1 for the access list number.
R3(config)#
R3(config)#
R3(config)#
R3(config)#
access-list
access-list
access-list
access-list
1
1
1
1
What command would you use to see where the access list was applied and in what direction?
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 5 of 9
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 6 of 9
Looking at the first permit ACE in the access list, what is another way to write this?
Is there any difference between this ACL on R1 with the ACL on R3? If so, what is it?
3) Test the ACL. From the command prompt on PC-C, ping PC-As IP address. Were the pings
successful?
4) Test the ACL to ensure that only the PC-C host is allowed access to the 192.168.10.0/24 network.
You must do an extended ping and use the G0/1 address on R3 as your source. Ping PC-As IP
address. Were the pings successful?
5) Test the ACL to see if it allows traffic from the 192.168.40.0/24 network access to the
192.168.10.0/24 network. You must perform an extended ping and use the loopback 0 address on R3
as your source. Ping PC-As IP address. Were the pings successful?
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 7 of 9
b. Add two additional lines at the end of the ACL. From global config mode, modify the ACL, BRANCHOFFICE-POLICY.
R1#(config)# ip access-list standard BRANCH-OFFICE-POLICY
R1(config-std-nacl)# 30 permit 209.165.200.224 0.0.0.31
R1(config-std-nacl)# 40 deny any
R1(config-std-nacl)# end
c.
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 8 of 9
Reflection
1. As you can see, standard ACLs are very powerful and work quite well. Why would you ever have the need for
using extended ACLs?
2. Typically, more typing is required when using a named ACL as opposed to a numbered ACL. Why would you
choose named ACLs over numbered?
Ethernet Interface #1
Ethernet Interface #2
Serial Interface #1
Serial Interface #2
1800
1900
2801
2811
2900
Note: To find out how the router is configured, look at the interfaces to identify the type of router and how many
interfaces the router has. There is no way to effectively list all the combinations of configurations for each router
class. This table includes identifiers for the possible combinations of Ethernet and Serial interfaces in the device.
The table does not include any other type of interface, even though a specific router may contain one. An
example of this might be an ISDN BRI interface. The string in parenthesis is the legal abbreviation that can be
used in Cisco IOS commands to represent the interface.
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 9 of 9