DLD Lab11
DLD Lab11
Lab Engineer: Ansa Niaz & Ghulam Ruqia Semester: Spring 2024
Signature: ____________________________
Objective
The objective of this lab is to do some networking commands to help us better understand
networking and, in its troubleshooting, as well as its administration.
Equipment and Component
Component Description Value Quantity
Conduct of Lab
1. Students have to perform this experiment on Wireshark.
2. Students are required to perform this experiment individually.
3. In case the lab experiment is not understood, the students are advised to seek help from the
course instructor, lab engineers and assigned teaching assistants (TAs)
4. At the end of the lab, every student is required to save the completed lab manual in PDF format
and submit this single PDF file on Google Classroom at the submission link created for this lab..
Theory and Background
An Internet Protocol address is a numerical label such as 192.0.2.1 that is connected to a
computer network that uses the Internet Protocol for communication. They establish the
framework for data exchange, with key examples including TCP/IP for internet communication
and HTTP/DNS for web-related functions.
Lab Tasks
● Start up Wireshark and begin packet capture (Capture->Start) and then press OK on the
Wireshark Packet Capture Options screen (we’ll not need to select any options here). ● Start
up pingplotter and enter the name of a target destination in the “Address to Trace Window.”
Enter 3 in the “# of times to Trace” field, so you don’t gather too much data. Select the menu
item Edit>Options->Packet Options and enter a value of 56 in the Packet Size field and then
press OK. Then press the Trace button. You should see a pingplotter window that looks
something like this:
●
Next, send a set of datagrams with a longer length, by selecting Edit->Options->Packet
Options and enter a value of 2000 in the Packet Size field and then press OK. Then press the
Resume button.
● Finally, send a set of datagrams with a longer length, by selecting Edit->Advanced
Options->Packet Options and enter a value of 3500 in the Packet Size field and then
press OK. Then press the Resume button.
● Stop Wireshark tracing.
A look at the captured trace
In your trace, you should be able to see the series of ICMP Echo Request (in the case of
Windows machine) or the UDP segment (in the case of Unix) sent by your computer and the
ICMP TTL-exceeded messages returned to your computer by the intermediate routers. In the
questions below, we’ll assume you are using a Windows machine; the corresponding questions
for the case of a Unix machine should be clear. Whenever possible, when answering a question
below you should hand in a printout of the packet(s) within the trace that you used to answer the
question asked.
Select the first ICMP Echo Request message sent by your computer, and expand the Internet
Protocol part of the packet in the packet details window.
172.16.22.139
2. Within the IP packet header, what is the value in the upper layer protocol field?
ICMP 0X01 in hexadecimal. In decimal it’s 1.
3. How many bytes are in the IP header? How many bytes are in the payload of the IP
datagram? Explain how you determined the number of payload bytes.
4. Has this IP datagram been fragmented? Explain how you determined whether or not
the datagram has been fragmented.
5. Which fields in the IP datagram always change from one datagram to the next within
this series of ICMP messages sent by your computer?
Identification as packets have different IDs
Header Checksum
6. Which fields stay constant? Which of the fields must stay constant? Which fields
must change? Why?
7. What is the value in the Identification field and the TTL field?
TTL= 255
Identification: 16632
8. Do these values remain unchanged for all of the ICMP TTL-exceeded replies sent to
your computer by the nearest (first hop) router? Why?