👉 🔥 CLICK HERE! 🔥 👈

(pak it) (n.) A piece of a message transmitted over a packet-switching network. See under packet switching. One of the key features of a packet is that it contains the destination address in addition to the data. In IP networks, packets are often called datagrams. Topology Addressing Table Device Interface IP Address Subnet Mask Default Gateway R1 G00 10.0.0.1 255.0.0.0 NA G01 172.16.0.1 255.255.0.0 NA G02 192.168.0.1 255.255.255.0 NA Server1 NIC 172.16.255.254 255.255.0.0 172.16.0.1 Server2 NIC 192.168.0.254 255.255.255.0 192.168.0.1 Server3 NIC 10.255.255.254 255.0.0.0 10.0.0.1 L1 NIC 172.16.0.2 255.255.0.0 172.16.0.1 L2 NIC 192.168.0.2 255.255.255.0 192.168.0.1 L3 NIC 10.0.0.2 255.0.0.0 10.0.0.1 Part 1: Troubleshoot ACL Issue 1 Part 2: Troubleshoot ACL Issue 2 Part 3: Troubleshoot ACL Issue 3 This networkis meant to have the following three policies implemented: Donot allow hosts from the LAN1 (10.0.0.08) network access to the LAN2 (172.16.0.016)network. Permit all other access.Donot allow host L2 in LAN2 (172.16.0.016) network access to the LAN3(192.168.0.024). Permit all other access.Onlypermit host L3 in LAN3 (192.168.0.024) network access to the LAN1 (10.0.0.08). No other restrictions should be in place. Unfortunately,the rules that have been implemented are not working correctly. Your task is tofind and fix the errors related to the access lists on R1. Note: To attainfull marks in this lab, it is best to remove and re-enter ACLs. It is also bestto remove and re-enter any invalid ipaccess-group command. Do not allow hosts from the LAN1 (10.0.0.08) networkaccess to LAN2 (172.16.0.016) network. Permit all other access. This is notcurrently the case. Determine the ACL problem. As you perform thefollowing tasks, compare the results to what you would expect from the ACL. Using L1,open the Command Prompt and ping Server2 using the ping –t 172.16.255.254 command. As expected, the pings should notbe successful. However, hosts in LAN3 should be able to access LAN2. Using L3,open the Command Prompt and ping Server2. The pings should be successful. View the running configuration on R1. Examine access list DENY-LAN1 ACL and its placement on theinterfaces. Is there any statement in the list that permits or denies trafficto other networks? Are the statements in the correct order? Is the access listconfigured on the correct interface and in the correct direction? Perform other tests, as necessary. Make the necessary adjustments to the DENY-LAN1 ACL or to its placement, to fix the problem. Verify that the problem is resolved and documentthe solution. If the problem is resolved, document the solution; otherwisereturn to Step 1. All traffic is beingdenied because of deny any ACE. An implicitly denies traffictherefore a permit any is required. Removing and re-entering the ACL correctly fixes theproblem. You should have 33% completed. Do not allow host L2 in LAN2 (172.16.0.016) networkaccess to the LAN3 (192.168.0.024). Permit all other access. This is notcurrently the case. Determine the ACL problem. As you perform thefollowing tasks, compare the results to what you would expect from the ACL. Using L2,open the Command Prompt and ping Server3 using the ping –t 192.168.0.254 command. The pings should not be successful.However, other hosts in LAN2 should be able to access LAN3. Using Server2,open the Command Prompt and ping Server3. The pings should be successful. View the running configuration on R1. Examine access list DENY-L2 ACL and its placement on theinterfaces. Is there any statement in the list that permits or denies trafficto other networks? Are the statements in the correct order? Is the access listconfigured on the correct interface and in the correct direction? Perform other tests, as necessary. Make the necessary adjustments to the DENY-L2 ACL or to its placement, to fix the problem. Verify that the problem is resolved and documentthe solution. If the problem is resolved, document the solution;otherwise return to Step 1. The first ACE in theDENY-L2 ACL permits all traffic. Therefore, the 2nd ACE is never matched. The order of ACEstatements should be reversed. Removing and re-entering the ACL correctly fixesthe problem. You should have 66% completed. Only permit host L3 in LAN3 (192.168.0.024) networkaccess to the LAN1 (10.0.0.08). This is not currently the case. Determine the ACL problem. As you perform thefollowing tasks, compare the results to what you would expect from the ACL. Using L3,open the Command Prompt and ping L1 using the ping –t 10.0.0.2 command. The pings should be successful. Using Server3,open the Command Prompt and ping L1. The pings should not be successful. View the running configuration on R1. Examine access list PERMIT-L3 ACL and its placement on theinterfaces. Is there any statement in the list that permits or denies trafficto other networks? Are the statements in the correct order? Is the access listconfigured on the correct interface and in the correct direction? Perform other tests, as necessary. Make the necessary adjustments to the PERMIT-L3 ACL or to its placement, to fix the problem. Verify that the problem is resolved and documentthe solution. If the problem is resolved, document the solution;otherwise return to Step 1. All traffic was being denied because the ip access group command on interface GigabitEthernet 00was being applied in the wrong direction. It should be applied outbound. Removing and re-entering the ip access-group command correctlyfixes the problem. You should have 100% completed. Access-lists pose a logical problem which often has morethan one solution. Can you think of a different set of rules or placements thatwould yield the same required access filtering? Answers will vary. Question Location Possible Points Earned Points Documentation Score 10 Packet Tracer Score 100 Total Score 100 !————————-—— !Initial Network !————————-—— !R1 Initial NET ———– enable configure terminal hostname R1 interfaceGigabitEthernet00 description Link to LAN 1 ip address 10.0.0.1 255.0.0.0 no shut ! interfaceGigabitEthernet01 description Link to LAN 2 ip address 172.16.0.1 255.255.0.0 no shut ! interfaceGigabitEthernet02 description Link to LAN 3 ip address 192.168.0.1 255.255.255.0 no shut ip access-liststandard DENY-LAN1 deny 10.0.0.0 0.255.255.255 permit any interfaceGigabitEthernet01 ip access-group DENY-LAN1 out ip access-liststandard DENY-L2 deny host 172.16.0.2 permit any interfaceGigabitEthernet02 ip access-group DENY-L2 out ip access-liststandard PERMIT-L3 permit host 192.168.0.2 interfaceGigabitEthernet00 ip access-group PERMIT-L3 out !————————-—— !Correcting ACL1 !————————-—— !R1 conf t no ip access-liststandard DENY-LAN1 ip access-liststandard DENY-LAN1 deny 10.0.0.0 0.255.255.255 permit any !Correcting ACL 2 !————————-—— !R1 conf t no ip access-list standard DENY-L2 ip access-liststandard DENY-L2 deny host 172.16.0.2 permit any !Correcting ACL 3 !————————-—— !R1 conf t interfaceGigabitEthernet00 no ip access-group PERMIT-L3 in ip access-group PERMIT-L3 out

Items