Scribd
Upload
5 views2 pages

K3 - Revised Packet Tracer - Subnet Routing

The document outlines a revised Packet Tracer exercise for connecting two IP subnets, 192.168.1.0/24 and 192.168.15.0/24, by verifying their configurations and ensuring proper DHCP settings. It includes steps for validating subnet reachability and configuring routing rules on Router 0 to enable communication between the subnets. The exercise emphasizes troubleshooting ping failures and provides guidance for extending the experiment to include additional subnets and routing hops.

Uploaded by

asustrinity
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views2 pages

K3 - Revised Packet Tracer - Subnet Routing

The document outlines a revised Packet Tracer exercise for connecting two IP subnets, 192.168.1.0/24 and 192.168.15.0/24, by verifying their configurations and ensuring proper DHCP settings. It includes steps for validating subnet reachability and configuring routing rules on Router 0 to enable communication between the subnets. The exercise emphasizes troubleshooting ping failures and provides guidance for extending the experiment to include additional subnets and routing hops.

Uploaded by

asustrinity
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Faculty of Computer Science and Engineering - HCMC University of Technology

Department of Systems and Networks

Computer Network 1 – Revised Packet Tracer

REVISED PACKET TRACER (3)


Prerequisite: Given the following network topology:

In the previous practice, the two IP subnet is not seen by each other. This work is a
further practice which help setting to make them connected.

1. Verify each subnet configurations


subnet 192.168.1.0/24 with server1 subnet 192.168.15.0/24 with server0
Netmask 255.255.255.0 Netmask 255.255.255.0
Gateway IP (router) 192.168.1.1 Gateway IP (router) 192.168.15.1
Server 1 IP (static) 192.168.1.5 Server 0 IP (static) 192.168.15.5
- Server 1 requires gateway and netmask configuration - Server 0 requires gateway and netmask configuration
DHCP service on server 1: DHCP service on server 0:
- Start: 192.168.1.100 - Start: 192.168.15.100
- mask: 255.255.255.0 - mask: 255.255.255.0
- Gateway: 192.168.1.1 - Gateway: 192.168.15.1
- Range: 127 - Range: 127
2. Validation step on each subnet:
It need to validate the local subnet reachability:

1) Physical link must be ON for all links


2) DHCP client successfully obtained the IP with correct info:
a) Gateway IP is correctly assigned to router associated port (connect) of the subnet
Faculty of Computer Science and Engineering - HCMC University of Technology
Department of Systems and Networks

Computer Network 1 – Revised Packet Tracer

b) Netmask
c) IP no-duplicate (all IP are unique) and correct physical port, link ON 3) Reachable link:
a) ping PC -> Server must be success
b) ping PC -> router gateway port must be success

If the ping step is fail, you need to back-trace verify these previous step one by one to make sure every item is satisfied. If
you are still not able to do the ping successfully, you still have wrong items somewhere.

3. Configure routing rules:


After finishing local subnet verification, config the routing rule in the Router 0
Router0#
Router0#
Router0#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router0(config)#route ospf 65001
Router0(config-router)#network 192.168.1.0 0.0.0.255 area 0
Router0(config-router)#network 192.168.15.0 0.0.0.255 area 0
Router0(config-router)#end
Router0#
After finish this work, you are now able to create a routing rule between the two different subnets. An
extended work in appendix helps upgrade the experiment to involve more subnets and more routing
hop.

You might also like