No hosts on either of the Branch LANs should be allowed to access HQ LAN 1. The name of your ACL must match this name exactly. Create a named extended ACL called branch_to_hq. HQ(config-line)#access-class vty_block in HQ(config)#ip access-list standard vty_block Only addresses from the HQ LAN 2 network should be able to access the VTY lines of the HQ router. HQ(config)#interface GigabitEthernet0/0/0 HQ(config)#access-list 111 permit ip any any No hosts on HQ LAN 1 should be able to access the Branch Server. HQ(config)#access-list 101 permit ip any any HQ(config)#access-list 101 deny tcp any host 192.168.1.70 eq ftp No ICMP traffic from the internet should be allowed to any hosts on HQ LAN 1. Explicitly block FTP access to the Enterprise Web Server from the internet. Place your ACLs in the most efficient location and direction. 
Write your ACL statements to address the requirements in the order that they are specified here. Use shorthand ( host and any) whenever possible. Do not use explicit deny any statements at the end of your ACLs. Step 2: Configure Standard and Extended ACLs per Requirements.Ĭonfigure ACLs to meet the following requirements: All hosts should be able to ping all other hosts. Instructions Step 1: Verify Connectivity in the New Company Networkįirst, test connectivity on the network as it is before configuring the ACLs. In this activity you will configure extended, standard named, and extended named ACLs to meet specified communication requirements. Verify the operation of the configured ACLs. Configure the appropriate router interfaces with ACLs in the appropriate direction. Configure an ACL to control access to network device terminal lines. Configure a router with extended ACLs to meet specific communication requirements. 
Configure a router with extended named ACLs. Configure a router with standard named ACLs. 
5.5.1 Packet Tracer – IPv4 ACL Implementation Challenge Addressing Table Device
0 kommentar(er)
