Objectives Verify connectivity among devices before firewall configuration. Use ACLs to ensure remote access to the routers is available only from management station PC- C. Configure ACLs on R1 and R3 to mitigate attacks. Verify ACL functionality.
Introduction Access to routers R1, R2, and R3 should only be permitted from PC-C, the management station. PC-C is also used for connectivity testing to PC-A, a server providing DNS, SMTP, FTP, and HTTPS services. Standard operating procedure is to apply ACLs on edge routers to mitigate common threats based on source and/or destination IP address. In this activity, you create ACLs on edge routers R1 and R3 to achieve this goal. You then verify ACL functionality from internal and external hosts. The routers have been pre-configured with the following: Enable password: ciscoenpa55 Password for console: ciscoconpa55 Username for VTY lines: SSHadmin Password for VTY lines: ciscosshpa55 IP addressing Static routing
Task 1: Verify Basic Network Connectivity
Verify network connectivity prior to configuring the IP ACLs.
Step 1. From the PC-C command prompt, ping the PC-A server.
Step 2. From the PC-C command prompt, SSH to the router R2 Lo0 interface. Exit the SSH session.
Step 3. From PC-C, open a web browser to the PC-A server (using the IP address) to display the web page. Close the browser on PC-C.
Step 4. From the PC-A server command prompt, ping PC-C.
Task 2: Secure Access to Routers
Step 5. Configure ACL 10 to block all remote access to the routers except from PC-C. Use the access-list command to create a numbered IP ACL on R1, R2, and R3. R1(config)# access-list 10 permit 192.168.3.3 0.0.0.0
On R3, block all packets containing the source IP address from the following pool of addresses: 127.0.0.0/8, any RFC 1918 private addresses, and any IP multicast address.
Step 8. Configure ACL 100 to block all specified traffic from the outside network. You should also block traffic sourced from your own internal address space if it is not an RFC 1918 address (in this activity, your internal address space is part of the private address space specified in RFC 1918). Use the access-list command to create a numbered IP ACL. R3(config)# access-list 100 deny ip 10.0.0.0 0.255.255.255 any R3(config)# access-list 100 deny ip 172.16.0.0 0.15.255.255 any R3(config)# access-list 100 deny ip 192.168.0.0 0.0.255.255 any R3(config)# access-list 100 deny ip 127.0.0.0 0.255.255.255 any R3(config)# access-list 100 deny ip 224.0.0.0 15.255.255.255 any R3(config)# access-list 100 permit ip any any
Step 9. Apply the ACL to interface Serial 0/0/1.
Use the ip access-group command to apply the access list to incoming traffic on interface Serial 0/0/1. R3(config)# interface s0/0/1 R3(config-if)# ip access-group 100 in
Step 10. Confirm that the specified traffic entering interface Serial 0/0/1 is dropped. From the PC-C command prompt, ping the PC-A server. The ICMP echo replies are blocked by the ACL since they are sourced from the 192.168.0.0/16 address space.(phản hồi bị chặn bởi ACL vì lấy IP từ 192.168..0.0/16)
Step 11. Remove the ACL from interface Serial 0/0/1.
Remove the ACL. Otherwise, all traffic from the outside network (being addressed with private source IP addresses) will be denied for the remainder of the PT activity. (Loại bỏ ACL. Nếu không, tất cả lưu lượng truy cập từ mạng bên ngoài (được đánh địa chỉ bằng địa chỉ IP nguồn riêng) sẽ bị từ chối trong phần còn lại của hoạt động PT.) Use the no ip access-group command to remove the access list from interface Serial 0/0/1.(xoá d.sách truy cập khỏi Serial) R3(config)# interface s0/0/1 R3(config-if)# no ip access-group 100 in
Note: In order for the PT activity to score 100 percent, the ACL needs to be grouped to the interface at the end of the activity:
R3(config)# interface s0/0/1
R3(config-if)# ip access-group 100 in
Task 4: Create a Numbered IP ACL 110
Deny all outbound packets with source address outside the range of internal IP addresses. (Từ chối tất cả các gói gửi đi có địa chỉ nguồn nằm ngoài dải địa chỉ IP nội bộ.)
Step 12. Configure ACL 110 to permit only traffic from the inside network. Use the access-list command to create a numbered IP ACL. R3(config)# access-list 110 permit ip 192.168.3.0 0.0.0.255 any
Use the ip access-group command to apply the access list to incoming traffic on interface F0/1. R3(config)# interface fa0/1 R3(config-if)# ip access-group 110 in
Create a Numbered IP ACL 120
Permit any outside host to access DNS, SMTP, and FTP services on server PC-A, deny any outside host access to HTTPS services on PC-A, and permit PC-C to access R1 via SSH.
Step 14. Verify that PC-C can access the PC-A via HTTPS using the web browser. Be sure to disable HTTP and enable HTTPS on server PC-A.
Step 15. Configure ACL 120 to specifically permit and deny the specified traffic. Use the access-list command to create a numbered IP ACL. R1(config)# access-list 120 permit udp any host 192.168.1.3 eq domain R1(config)# access-list 120 permit tcp any host 192.168.1.3 eq smtp R1(config)# access-list 120 permit tcp any host 192.168.1.3 eq ftp R1(config)# access-list 120 deny tcp any host 192.168.1.3 eq 443 R1(config)# access-list 120 permit tcp host 192.168.3.3 host 10.1.1.1 eq 22
Step 16. Apply the ACL to interface S0/0/0.
Use the ip access-group command to apply the access list to incoming traffic on interface S0/0/0. R1(config)# interface s0/0/0 R1(config-if)# ip access-group 120 in
Step 17. Verify that PC-C cannot access PC-A via HTTPS using the web browser.
Task 5: Modify An Existing ACL
Permit ICMP echo replies and destination unreachable messages from the outside network (relative to R1); deny all other incoming ICMP packets.
Step 18. Verify that PC-A cannot successfully ping the loopback interface on R2.
Step 19. Make any necessary changes to ACL 120 to permit and deny the specified traffic. Use the access-list command to create a numbered IP ACL. R1(config)# access-list 120 permit icmp any any echo-reply R1(config)# access-list 120 permit icmp any any unreachable R1(config)# access-list 120 deny icmp any any R1(config)# access-list 120 permit ip any any
Step 20. Verify that PC-A can successfully ping the loopback interface on R2.
Step 21. Check results.
Your completion percentage should be 100%. Click Check Results to see feedback and verification of which required components have been completed.
