Double-Click and Type Here or Delete This Text
Double-Click and Type Here or Delete This Text
School of Science
Objectives:
The objective is to assess your understanding of fundamental networking layer structure and your
ability to apply them to analysing real internet packets using Wireshark.
Learning Outcomes:
On completion of this assignment students should be able to:
1. Analyse and evaluate network technologies and services using a layered approach and
network standards.
2. Analyse practical internet packets as per given protocols.
Preparation:
1. This assignment requires students to produce a Panopto video based on task instructions
below. This assignment requires video recording equipment such as a notebook equipped with
a camera, as well as the software Panopto. If required, you can borrow a laptop from the
library.
2. You should be familiar with Panopto and Wireshark for this assignment. It is your
responsibility to submit a video correctly according to the instructions.
IMPORTANT: If you submit your video via the wrong option, it may delay the marking of your
assessment and/or lead to late penalties.
3. Practice recording a few times to keep within the time limit, and use the rubric as a guide, as
it will be used for grading.
Requirements:
1. Please check the submission website for submission details.
2. You have to show your student ID (if you are an online student and do not have the student
card, you can use your passport with your photo on it) at the beginning of the video.
3. You will need to show footage of yourself completing each task, as well as footage of
yourself speaking to the camera about each task.
Academic Integrity:
Please ensure you understand the expectations of the university in terms of citing external sources
and ensuring all individual work is yours and yours alone. It is always assumed that once you hit the
Submit button on your assignment, you understand and have abided by all university expectations
around Academic Integrity. Your assignment is marked as such.
Task 1: HTTP
Generate and capture your own HTTP traffic and examine the message fields. Explain sequences of
messages exchanged between the server and its client for HTTP traffic using Wireshark. Summarise
the captured message flow and you can use slides to support your explanations. In addition, please
try to address the following questions in your video.
1. Which transport protocol is the HTTP using? How do you know?
2. Is the TCP handshake process occurring before the HTTP connection? How do you identify
the TCP handshake packets? How do you know whether the TCP handshake is for the
following HTTP connection?
3. What are the port numbers used at the client and server?
4. What is the version number of the used HTTP?
Note: The following shows an example of how to generate HTTP traffic.
a. Clear the browser’s cache.
b. Find a site with HTTP.
c. Open Wireshark and start capturing.
d. Open your browser and access a HTTP site.
e. Stop capturing the packets and close the browser.
f. Find HTTP packets and complete the tasks.
Task 2: Encapsulation
Generate and capture your own TCP/IP traffic and packets and inspect TCP/IP model layers and
fields. Analyse and explain encapsulation processes with TCP/IP layers and the header size of each
layer and their payload sizes to verify the encapsulation. In addition, please try to address the
following questions in your video.
1. What are the sizes of the headers and payloads of the IP and TCP packets in your captured
traces? Please explicitly point out them.
2. What are the total lengths of these IP and TCP packets? Please explicitly point out them.
3. What are the relationships among the header size, payload size, and total length?
4. How do you confirm that the encapsulation is occurring? Do you have to check the contents
on top of confirming the length of each layer packet?
Note: Layer 2 packet may have a trailer.
Discuss the variations in sequence numbers, acknowledge numbers and window size, and explain the
congestion control actions in the TCP protocol. In addition, please try to address the following
questions in your video.
1. What is the raw sequence number for the TCP packet with "Seq = 1" in your captured trace?
2. How is the raw sequence number determined? Why?
3. Could we determine the expected acknowledge number for a packet with known sequence
number and total length? How?
4. Please point out the corresponding acknowledge packet for a specific packet with a sequence
number. Does each sent packet have a corresponding acknowledge in your captured files?
Why or why not?
5. Did you find a congestion in your captured file? Why and why not? What would you expect
on the sequence number and window size if there is a congestion in the captured file?