Jared Doll 2021
The below table is the Network topology for the
project:
|
Device |
Interface |
IP Address |
|
R0 |
Ge0/0 |
192.168.10.1/24 |
|
Ge0/1 |
10.0.0.1/30 |
|
|
R1 |
Ge0/0 |
10.0.1.1/30 |
|
Ge0/1 |
10.0.0.2/30 |
|
|
S0/0/0 |
NA |
|
|
R2 |
Ge0/0 |
192.168.20.1/24 |
|
Ge0/1 |
10.0.1.2/30 |
|
|
PC0 |
NIC |
DHCP Assigned |
|
PC1 |
NIC |
DHCP Assigned |
|
PC2 (Dual NIC) |
NIC 1 |
DHCP Assigned |
|
NIC 2 |
192.168.0.4 |
|
|
PC3 |
NIC |
192.168.0.2 |
Routers 0, 1, and 2
are configured with RIPv2 Routing. To verify connectivity, Pings were conducted
across the network.
Ping from PC2 to
R2: This ping verified that
PC2 could reach R2 over the network. It also showed that S1 was functioning
properly to deliver traffic between PC2 and R2.
Ping from R2 to R1: This ping verified that Router 2 and Router 1 were
able to communicate with each other over the 10.0.1.0 network.
Ping from R1 to R0: This ping verified that R1 and R0 were able to
communicate over the 10.0.0.0 network.
Ping from PC2 to
PC0: this ping verified that
traffic was able to reach across the entirety of the network. It also verified
that RIP routing was functioning correctly.
Router 1 was set up
with a DHCP server. Router 0 and 2 utilized DHCP helper addresses to relay
addresses from R1 to end devices connected to the switches on either side of
Routers 0 and 2. To test DHCP configuration, end devices were plugged into
Switch 0 and Switch 1. R0’s client side was set up on the 192.168.10.0/24
subnet and R2’s client side was set up on the 192.168.20.0/24 subnet. The
screenshots below are end devices plugged into Switch 0 and 1 respectively to
verify DHCP addresses were assigned:
R2 SSH connectivity: A PC connected to S1 needed to be able to SSH
into R2. To test this, Putty was launched on PC2 and R2’s IP was connected to
over SSH. The login prompt in the screenshot below shows that the two machines
can communicate with each other over SSH.