Week 1 Lab - Wireshark Getting Started - Rosa Pereira

docx

School

University Of Arizona *

*We aren’t endorsed by this school

Course

375

Subject

Computer Science

Date

Apr 3, 2024

Type

docx

Pages

4

Uploaded by LieutenantStar15454

Report
1 Week 1 Lab: Getting Started with Wireshark Rosa Pereira University of Arizona NETV 375: Advanced Network Operations Professor Cyrus Afarin March 17, 2024
2 The purpose of this assignment is to familiarize ourselves with Wireshark, its basic functions and components that will help us get a better understanding of the packet analyzer and its capabilities. We will be taking Wireshark on a test run with a series of already given steps, this test run should help us observe different protocols in action as they occur, and more specifically we will be getting into the HTTP protocol and analyzing its interactions with sending and receiving information. There are a series of answers we must answer, in order to answer those, we will have to follow a series of steps provided in the Wireshark Lab – Getting Started v8.0 file in Week 1. We will list out the steps that will help us understand the packet analyzer a bit better, as well as take us to the right display that will be used to answer the questions provided. 1. Open a browser of choice. 2. Open Wireshark. 3. To start the capture, select the interface corresponding to the device that is being used to capture, in this case it would be Ethernet (as shown below). 4. To begin the packet capture double, click on the interface, the packets will begin to appear, let some of those packets load to get some information in our capture going.
3 5. Generate network traffic by visiting the following URL: https://gaia.cs.umass.edu/wireshark-labs/INTRO-wireshark-file1.html 6. Once the URL is displayed in the browser, stop the capture by selecting the “Stop Capturing Packets” button in the command menu. 7. In the display filter go ahead and type “http” then hit enter. This will let us visualize only the HTTP protocol (the site visited in step 5). 8. Below the capture we can observe a series of minimized protocols such as Internet, TCP, and HTTP, observe the different protocols, after being done select the HTTP GET request from the website entered, and leave only the HTTP information maximized below the capture (as shown below). After the previous steps have been completed, we are now ready to answer the questions provided by the Lab 1 file. 1. Without any filters three protocols that can be appreciated are: UDP, TCP, and DNS. More can be observed, but as far as protocols we should be familiar with those are the ones that stand out.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
4 2. To calculate the amount of time it took from the HTTP GET request until the HTTP OK reply from the server, we will subtract the GET request time, from the OK reply time, this will give us the amount of time between both interactions. In this case the amount of time it took from the GET request to get that OK reply was 0.063987 seconds. 3. The IP address of the gaia.cs.umass.edu is 128.119.245.12 and the IP address of the device being used to capture is 192.168.1.62. 4. The print of the two HTTP messages will be included along with the submission of this assignment in D2L. After completing this exercise, we should feel more familiarized with the functionality and components on Wireshark. More specifically this introductory assignment helped us identify different protocols found in a capture, the time it takes to from the GET request (source) to the OK reply (destination), as well as the information found within the HTTP protocol precisely. This introduction to Wireshark functions and capabilities provided important and crucial information needed in order to continue understanding and exploring the packet analyzer and its many other features.