FINAL PROJECT
Cybersecurity Fundamentals
Linux & Basic Networking
Practical Lab Assignment
PREPARED BY
Name : Mohamed Ashraf Samir Yasin
Code : 202420291
. Overview & Objectives
This lab implements and verifies a small, routed network in Cisco Packet Tracer, covering:
Switch hardening (hostname, console security, enable secret, MOTD banner)
PC IP configuration (address, subnet mask, default gateway)
Layer 2 connectivity and MAC address table verification
Layer 3 static routing between three separate LANs
End-to-end reachability testing
ARP table investigatio
IP Addressing Scheme
Network Purpose Gateway
[Link]/24 PC1 & PC2 LAN [Link] (R1
Gi0/0/0)
[Link]/24 PC3 & PC4 LAN [Link] (R1
Gi0/0/1)
[Link]/24 PC5 & PC6 LAN [Link] (R2
Gi0/0/0)
[Link]/24 Router-to-Router link Serial0/1/0 — .1 / .2
PC IP Address Subnet Mask Default Gateway
PC1 [Link] [Link] [Link]
PC2 [Link] [Link] [Link]
PC3 [Link] [Link] [Link]
PC4 [Link] [Link] [Link]
PC5 [Link] [Link] [Link]
PC6 [Link] [Link] [Link]
Fig. 1 — Full topology in Cisco Packet Tracer: SW1 (PC1–PC2) and SW2
(PC3–PC4) uplink to
R1; R1 connects to R2 over the [Link]/24 serial link; R2 uplinks
to SW3 (PC5–PC6)
2. Switch Configuration
Each of the three 2960-24TT switches was hardened with a hostname, a
privileged EXEC secret, console-line password protection, and an authorized-
access banner, then saved to NVRAM
enable
configure terminal
hostname SW1
enable secret class
line console 0
password cisco
login
exit
banner motd # WARNING: Authorized Access Only! #
exit
copy running-config startup-config
Identical configuration applied to SW2 and SW3 with their respective hostnames.
Console Verification sw1 / sw2 / sw3
SW 1. CONFIGURATION OUTPUT
Switch> enable
Switch# configure terminal
Switch (config)# hostname SW1
SW1(config)# line console 0
SW1(config-line) # password cisco
SW1(config-line) # login
SW1(config-line) # exit
SW1(config)# enable secret cisco123
SW1(config)# banner motd # Unauthorized Access Prohibited #
SW1(config)# exit
SW1# copy running-config startup-config
SW2 . CONFIGURATION OUTPUT
Switch> enable
Switch# configure terminal
Switch(config)# hostname SW2
SW2(config)# line console 0
SW2(config-line) # password cisco
SW2(config-line) # login
SW2(config-line) # exit
SW2(config)# enable secret cisco123
SW2(config)# banner motd # Unauthorized Access Prohibited #
SW2(config)# exit
SW2# copy running-config startup-config
SW3. CONFIGURATION OUTPUT
Switch> enable
Switch# configure terminal
Switch(config)# hostname SW3
SW3(config)# line console 0
SW3(config-line) # password cisco
SW3(config-line) # login
SW3(config-line) # exit
SW3(config)# enable secret cisco123
SW3(config)# banner motd # Unauthorized Access Prohibited #
SW3(config)# exit
SW3# copy running-config startup-config
Router 1 (R1) Configuration
R1 connects the [Link]/24 and [Link]/24 LANs and hands off to R2 over a
serial link on [Link]/24. R2 connects the [Link]/24 LAN and reaches the
remote LANs through static routes pointed at R1.
interface GigabitEthernet0/0/0
Ip address [Link] [Link]
no shutdown
!
interface GigabitEthernet0/0/1
Ip address [Link] [Link]
no shutdown
!
interface Serial0/1/0
Ip address [Link] [Link]
no shutdown
!
Ip route [Link] [Link] [Link]
Router> enable
Router# configure terminal
Router(config)# hostname R1
R1(config)# interface GigabitEthernet0/0/0
R1(config-if) # ip address [Link] [Link]
R1(config-if) # no shutdown
R1(config-if) # exit
R1(config)# interface GigabitEthernet0/0/1
R1(config-if) # ip address [Link] [Link]
R1(config-if) # no shutdown
R1(config-if) # exit
R1(config)# interface Serial0/1/0
R1(config-if) # ip address [Link] [Link]
R1(config-if) # no shutdown
R1(config-if) # exit
R1(config)# Ip route [Link] [Link] [Link]
R1(config)# exit
R1# copy running-config startup-config
Fig. 5 — R1 interface configuration: both LAN interfaces and the serial uplink come up,
followed by the static route to [Link]/24 via [Link].
R2
interface GigabitEthernet0/0/0
Ip address [Link] [Link]
no shutdown
!
interface Serial0/1/0
Ip address [Link] [Link]
no shutdown
!
Ip route [Link] [Link] [Link]
Ip route [Link] [Link] [Link]
Router> enable
Router# configure terminal
Router(config)# hostname R2
R2(config)# interface GigabitEthernet0/0/0
R2(config-if) # Ip address [Link] [Link]
R2(config-if) # no shutdown
R2(config-if) # exit
R2(config)# interface Serial0/1/0
R2(config-if) # Ip address [Link] [Link]
R2(config-if) # no shutdown
R2(config-if) # exit
R2(config)# Ip route [Link] [Link] [Link]
R2(config)# Ip route [Link] [Link] [Link]
R2(config)# exit
R2# copy running-config startup-config
Fig. 6 — R2 interface configuration and the two static routes back to the 10.0/24 and
20.0/24 LANs via [Link]
Note: the serial link initially reports changed state to down in isolation because it depends
on the peer's Serial0/1/0 also being enabled — the link comes up once both R1 and R2
finish their interface configuration.
4. Routing Table Verification
The show Ip route output on both routers confirms that the connected LANs and the static
routes to the remote networks are correctly installed in the routing table.
R1 Routing Table
R1# show Ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
I - IS-IS, L1 - IS-IS level 1, L2 - IS-IS level 2, IA - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is not set
C [Link]/24 is directly connected, GigabitEthernet0/0/0
C [Link]/24 is directly connected, GigabitEthernet0/0/1
C [Link]/24 is directly connected, Serial0/1/0
S [Link]/24 [1/0] via [Link]
Fig. 7 — R1 shows [Link]/24 and [Link]/24 as directly connected (C),
[Link]/24 as the connected serial link, and a static route (S) to [Link]/24 via
[Link].
R2 Routing Table
R1# show Ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
I - IS-IS, L1 - IS-IS level 1, L2 - IS-IS level 2, IA - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is not set
C [Link]/24 is directly connected, GigabitEthernet0/0/0
C [Link]/24 is directly connected, GigabitEthernet0/0/1
C [Link]/24 is directly connected, Serial0/1/0
S [Link]/24 [1/0] via [Link]
Fig. 8 — R2 shows [Link]/24 and the serial link as directly connected (C), plus static
routes (S) to [Link]/24 and [Link]/24 via [Link]
Result: every subnet in the topology is reachable from both routers — either as a directly
connected network or through a correctly pointed static route, confirming the static
routing design works as intended
5. Switch MAC Address Table Verification
After console login (protected by the banner and password configured earlier), each
switch's dynamic MAC address table was inspected with show mac address-table to
confirm the attached device's MAC address was learned on the expected Portz
SW1
Fig. 9 — MAC [Link].3b01 learned dynamically on Fa0/3, VLAN 1.
SW2
Fig. 10 — MAC [Link].3b02 learned dynamically on Fa0/3, VLAN 1
SW3
Fig. 11 — MAC 0001.439a.d901 learned dynamically on Fa0/3, VLAN 1.
6. End-to-End Connectivity Testing
Ping tests were run from the command prompt of the PCs to confirm reachability both
within the same LAN and across LANs through the two routers
Fig. 12 — From PC3, pinging its own address ([Link]) succeeds at 0% loss; pinging
[Link] (PC2) succeeds after an initial ARP resolution timeout, settling at 25% loss
due to that first ARP lookup — expected behavior on first contact, since ARP delays the
very first packet while the MAC address is resolved
Interpretation: the single lost packet on the first ping to a new neighbor is a normal ARP
resolution delay, not a routing or connectivity fault — once the destination's MAC address
is cached, subsequent replies return in under a millisecond.
7. ARP Table Investigation
Every ping generates ARP traffic on the local segment: before a PC can address a frame to
another IP on its own LAN, or to its default gateway for a remote IP, it must first resolve the
destination's MAC address with an ARP request/reply exchange. This resolved mapping is
then cached locally and can be displayed with arp –a
Relationship Between IP and MAC Addresses
. For a same-LAN destination (e.g. PC3 → PC4), the PC ARPs for the destination's own MAC
address directly
. For a cross-LAN destination (e.g. PC1 → PC5), the PC ARPs only for its default gateway's
MAC address — the router's interface — since the actual destination is off-segment.
. Each router hop then re-encapsulates the packet with a new source/destination MAC
pair for the next segment, while the source and destination IP addresses stay unchanged
end-to-end.
. This is precisely why the first ping to a new neighbor (as observed with PC3 →
PC2 in Section 6) shows one lost packet: that first exchange is consumed by
ARP resolution before the ICMP echo can actually be delivered.
pwd - Print Working Directory
ls - List Directory Contents
ls -la - List All Files (Including Hidden)
cd - Change Directory
whoami - Display Current User
mkdir - Make Directory
rmdir - Remove Directory
touch - Create Empty File
rm - Remove File
cat - Concatenate & Display File
cut -d ' ' -f 1 [Link] استخراج الـIP addresses
cut -d '"' -f 2 [Link] استخراج الـHTTP requests
cut -d ' ' -f 1,6-8
استخراج الـIP + الـRequest
[Link]
cut -d ' ' -f 1 [Link] |
استخراج الـIPs الفريدة
sort | uniq
cut -d ' ' -f 1 [Link] |
استخراج الـIPs مع عدد التكرارات
sort | uniq -c