The document outlines a lab exercise focused on using Wireshark, a network protocol analyzer, to analyze network traffic and various protocols. Students engaged in practical exercises to understand HTTP communication and the time taken for requests and responses. Key findings included the identification of HTTP, TCP, and DNS protocols, as well as specific internet addresses and response times.
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
0 ratings0% found this document useful (0 votes)
3 views
Lab 1
The document outlines a lab exercise focused on using Wireshark, a network protocol analyzer, to analyze network traffic and various protocols. Students engaged in practical exercises to understand HTTP communication and the time taken for requests and responses. Key findings included the identification of HTTP, TCP, and DNS protocols, as well as specific internet addresses and response times.
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/ 7
MCT431 Industrial Communication and
Network Systems Lab 1
Fady Kamil Thabet 20P9581
Mohamed Ouda 20P4996 Asser Samir 20P9388 John Samy 20P9313 Mohamed Magdy 20P2424 1. Introduction Wireshark is a powerful network protocol analyzer used to inspect and capture real- time data traffic over a network. The primary objective of this lab was to introduce students to Wireshark and its functionalities. By engaging in practical exercises, students gained hands-on experience with analyzing network traffic, identifying various protocols, and interpreting HTTP communication. This lab lays the groundwork for understanding how data travels across networks and how tools like Wireshark can be used for troubleshooting and analysis. 2. Results Question 1: Protocols in the Protocol Column 1. List 3 different protocols that appear in the protocol column in the unfiltered packet-listing window in step 7 above. The following protocols were observed in the unfiltered packet-listing window: • Protocol 1: HTTP • Protocol 2: TCP • Protocol 3: DNS Question 2: Time Between HTTP GET and HTTP OK 2. How long did it take from when the HTTP GET message was sent until the HTTP OK reply was received? (By default, the value of the Time column in the packet?listing window is the amount of time, in seconds, since Wireshark tracing began. To display the Time field in time-of-day format, select the Wireshark View pull down menu, then select Time Display Format, then select Time-of-day.) The GET request was sent 1.983709 seconds
The response was received 2.123540 seconds.
Therefore, the OK reply was received after 0.139831 seconds or 139.831 milliseconds Question 3: Internet Addresses 3. What is the Internet address of the gaia.cs.umass.edu (also known as www?net.cs.umass.edu)? What is the Internet address of your computer?
Internet Address of the gaia.cs.umass.edu: [128.119.245.12]
Internet address of your computer: [192.168.1.2] Question 4: HTTP Messages 4. Print the two HTTP messages (GET and OK) referred to in question 2 above. To do so, select Print from the Wireshark File command menu, and select the “Selected Packet Only” and “Print as displayed” radial buttons, and then click OK REFERENCES
Wireshark Lab: Getting Started v7.0 Supplement to Computer Networking: A Top-DownApproach, 7th ed., J.F. Kurose and K.W. Ross.