Complete this assignment in” rel=”nofollow”>in the Maryville Virtual Lab.

One of the most well-known packet sniffers is called Wireshark┬«. It is a powerful tool that can capture, filter, and analyze network traffic. It can promiscuously capture traffic on both wired and wireless networks. It is used by security and networkin” rel=”nofollow”>ing professionals to troubleshoot networkin” rel=”nofollow”>ing problems.

In this project, you will use Wireshark, capture packets, and look at the contents of a packet. When placed correctly, a network admin” rel=”nofollow”>inistrator can use Wireshark to see all the traffic comin” rel=”nofollow”>ing in” rel=”nofollow”>into and out of a network. Network admin” rel=”nofollow”>inistrators can, among other thin” rel=”nofollow”>ings, see which hostnames are bein” rel=”nofollow”>ing requested and who is requestin” rel=”nofollow”>ing them. Surfin” rel=”nofollow”>ing the Web is not anonymous.

Before begin” rel=”nofollow”>innin” rel=”nofollow”>ing your project, watch the followin” rel=”nofollow”>ing Wireshark 101 video from Hak5 for background in” rel=”nofollow”>information on the tool (please note the videos covers version 1 while we will be usin” rel=”nofollow”>ing version 2 but usage if very similar).
https://www.youtube.com/watch?v=f4zqMDzXt6k (Lin” rel=”nofollow”>inks to an external site.)Lin” rel=”nofollow”>inks to an external site.
Double-click the Wireshark icon on your desktop from the Maryville Virtual Lab that you used in” rel=”nofollow”>in Week 3 (If prompted to update the version, just select Skip this Version).
Click Local Area Connection on the home screen to begin” rel=”nofollow”>in collectin” rel=”nofollow”>ing data. (This selects the network in” rel=”nofollow”>interface we’ll be usin” rel=”nofollow”>ing and starts data collection).
While you are waitin” rel=”nofollow”>ing for data to be collected, open a web browser and go to a few websites of your choosin” rel=”nofollow”>ing and then close the browser.
After a few min” rel=”nofollow”>inutes of collectin” rel=”nofollow”>ing data packets that are passin” rel=”nofollow”>ing over the network, hit Stop Capturin” rel=”nofollow”>ing Packets (represented by a red rectangle).
Take a screenshot.
Sort your network traffic by selectin” rel=”nofollow”>ing the Protocol headin” rel=”nofollow”>ing which categorizes your traffic (e.g. ARP, TCP, UDP, etc).
Select 5 packets (from at least 3 different protocol types) and write a one page analysis (double spaced) for each packet discussin” rel=”nofollow”>ing your opin” rel=”nofollow”>inion of what is occurrin” rel=”nofollow”>ing here (for a total of at least 5 pages). A good example of what is expected is in” rel=”nofollow”>in the videos provided herein” rel=”nofollow”>in. Take a screenshot of each packet you are analyzin” rel=”nofollow”>ing as well (does not count toward the one page length requirement).
Close Wireshark and log off the Maryville Virtual Lab.
Also, you may fin” rel=”nofollow”>ind it in” rel=”nofollow”>interestin” rel=”nofollow”>ing to load Wireshark on your home machin” rel=”nofollow”>ine to analyze what traffic is comin” rel=”nofollow”>ing from your in” rel=”nofollow”>internet service provider.
If you’d like a video that further expands on Wireshark, I recommend the one below.

https://www.youtube.com/watch?v=-aTGL4M0db4Lin” rel=”nofollow”>inks to an external site.</p>

find the cost of your paper