Lab 9

Time allotted 3 hours.

Lab Submission (score) Marks

7.2.1.6 100/100 (pka only) 20
7.2.1.7 100/100 (pka only) 20
7.2.3.3 111/111 (pka only) 20
7.3.2.4 (pdf only) 15
7.4.1.2 60/60 (pkaonly) 25

Concepts I learned from the following 5 Labs Performed:

 7.2.1.6:
• I learnt how to set up numbered standard IPv4 ACLs in this lab.
• For the first phase of the implementation, I designed an ACL implementation
by investigating the supplied network setup, evaluating two network policies,
and planning ACL implementations.
• On R2 and R3, I configured and implemented a number of standard ACLs in
step 2 of the implementation.
 7.2.1.7:
• I learned how to configure named standard IPv4 ACLs in this lab.
• The goal at hand was to construct a named ACL to block clients from a
certain network or workstation from accessing a file server.
•In order to complete this lab, I configured and applied the specified standard
ACL, which I did by using several commands in the router R1 to configure and
apply the named ACL.
• After that, I checked to see if the named ACL was operating properly by
seeing if the workstations could ping the web server.

 7.2.3.3:
• I learned how to configure an ACL on VTY lines in this lab. The goal of this lab
is to learn how to remotely access a router while keeping it hidden from other
network users. As a result, an ACL must be set to enable PC access to telnet
lines while denying access to all other source IP addresses. I confirmed telnet
access before setting an ACL throughout the implementation. After that, I
created a named standard ACL and a numbered standard ACL on the router.

• Finally, after doing all of this, I checked to see whether ACL was functioning
properly. I did this by checking whether both machines could ping the router.

 7.3.2.4:
• I learned how to troubleshoot typical IPv4 ACLs in this lab.
 The first thing I did was look over the situations and devise a strategy
for dealing with them.
 Then I figured out what was wrong with the ACL and came up with a
remedy.
 7.4.1.2:
• I learned how to set up an addressing scheme, establish routing, and
implement named access control lists in this lab.
• First, I separated 172.16.128.0/19 into two equal subnets for usage on
Branch, assigning the final useable address of the second subnet to the Gigabit
Ethernet 0/0 interface, and documenting the addressing in the Addressing
Table.
•The specifications for the settings to be created have already been provided,
and I setup the HQ and Branch routers exactly according to them.
• I set up RIPv2 routing on the routers, created a default route on router HQ,
and created a named list for both routers.