0% found this document useful (0 votes)
33 views

Telecommunications Network Lab I - ECEG-6328: 1. Objectives

This lab aims to teach students about IPv4 protocol, VLSM, and CIDR. Students will create a network topology in GNS3 representing a company with three offices. They will develop a VLSM addressing scheme and configure routers and host devices with IP addresses. Students will configure static routes between subnets and verify connectivity using ping. Finally, they will capture and analyze packets using Wireshark to examine IPv4 and ARP protocol fields and observe packet fragmentation.

Uploaded by

fast ipnet
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
33 views

Telecommunications Network Lab I - ECEG-6328: 1. Objectives

This lab aims to teach students about IPv4 protocol, VLSM, and CIDR. Students will create a network topology in GNS3 representing a company with three offices. They will develop a VLSM addressing scheme and configure routers and host devices with IP addresses. Students will configure static routes between subnets and verify connectivity using ping. Finally, they will capture and analyze packets using Wireshark to examine IPv4 and ARP protocol fields and observe packet fragmentation.

Uploaded by

fast ipnet
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Telecommunications Network Lab I -ECEG-6328

Lab 1- IPv4 Protocol

1. Objectives
The aim of this lab is to understand IPv4 protocol, VLSM and CIDR. Thus, you are expected
to:-

 Create a network topology using GNS3


 Design and implement VLSM/CIDR
 Examine IPV4 protocol

2. Requirements
This lab uses the following software tools

 Wireshark to capture and examine the packets


 GNS3 – to create network topology
 Ping for connectivity test

3. Introduction
3.1. IPv4 protocol

IP version 4 is the widely deployed IP protocol, which is usually referred to simply as IPv4.
IPV4 datagrams have the format shown below.
3.2. IPV4 addressing

Every host and router is capable of sending and receiving IP datagrams. Thus, each host
and router interface needs to have its own IP address. IPv4 address is 32 bits long
(equivalently, 4 bytes), and there are thus a total of 232 possible IP addresses. These
addresses are typically written in so-called dotted-decimal notation.

IP address are assigned as a block of contiguous addresses. An organization that is granted


a range of addresses may divide the range into several subranges and assign each subrange
to a subnetwork (or subnet).

The Internet’s address assignment strategy is known as Classless Interdomain Routing.


CIDR generalizes the notion of subnet addressing. As with subnet addressing, the 32-bit IP
address is divided into two parts and again has the dotted-decimal form a.b.c.d/x, where x
indicates the number of bits in the first part of the address. The x most significant bits of an
address of the form a.b.c.d/x constitute the network portion of the IP address.

4. Network Topology
Assume a company has three offices: Central, East and West. The Central office is connected to
the East and West offices via point-to-point WAN lines. The central office is connected to the ISP
via a serial link. The company is granted a block of addresses with the beginning address
72.12.100.0/23. The Central office needs 120 addressed and each of the two other offices need 60
addresses. Create the network topology using GNS3.

5. Activity 1
5.1. Develop a VLSM address scheme for the network
Subnet Subnet address Subnet mask Broadcast
address

5.2. Configure the routers


 To start your routers Navigate to Control | Start/Resume all devices or click on the green
Start/Resume all devices icon in the toolbar
 Now that the routers are running, navigate to Control | Console connect to all devices, and
your terminal application should open windows or tabs to each of your routers.
 Commands to configure the routers interfaces
R#configure terminal
R(config)#interface f0/0
R(config-if)#ip address w.x.y.z subnet mask
R(config-if)#no shutdown
R(config-if)#end

 Check routers interfaces configuration


R(config-if)#show ip interface brief

 Save your configuration


R#write memory or
R#copy running-config startup-config

5.3. Configuring host devices

To configure the IP address of the host devices, type the following commands into the
VPCS command interface.

VPCS> ip <ip address/mask> < default gateway>


VPCS> save

Check your configuration with the “show ip” and “show ip all” commands

4. Activity 2
4.1. Configure static route on the router to allow connectivity between all the subnets

R(config)#ip route <network address > <subnet mask> <next hop>

4.2. Check that the static routes have been added to the routers

R(config)#show ip route

4.3. Verify connectivity between the offices and between the offices and the ISP

VPCS> ping <ip address>

5. Activity 3
5.1. Capture and analyze the packets using Wireshark

To begin capturing packets, right-click a link between two devices and select Start
Capture, as shown in Figure
5.2. Select ICMP packet and expand the IP header field to see the detail
o Explain the meaning of each field
o What is the initial value of the TTL field? Does this value change or stay the same?
o What is the payload length of the IP packet? What does it consist of?
o Are the IP packets fragmented or not?
5.3. What kind of difference do you observe between ICMP and ARP protocol packets?

You might also like