
“Wireshark is the world's foremost network protocol analyzer, and is the de facto (and often de jure) standard across many industries and educational institutions.”[1] That’s a pretty robust statement. The program has the typical protocol analyzer features, along with some pretty cool inspection methods.
Wireshark has a rich feature set which includes the following:
- Deep inspection of hundreds of protocols, with more being added all the time
Live capture and offline analysis
Standard three-pane packet browser
Multi-platform: Runs on Windows, Linux, OS X, Solaris, FreeBSD, NetBSD, and many others
Captured network data can be browsed via a GUI, or via the TTY-mode TShark utility
The most powerful display filters in the industry
Rich VoIP analysis
Read/write many different capture file formats: tcpdump (libpcap), Pcap NG, Catapult DCT2000, Cisco Secure IDS iplog, Microsoft Network Monitor, Network General Sniffer® (compressed and uncompressed), Sniffer® Pro, and NetXray®, Network Instruments Observer, NetScreen snoop, Novell LANalyzer, RADCOM WAN/LAN Analyzer, Shomiti/Finisar Surveyor, Tektronix K12xx, Visual Networks Visual UpTime, WildPackets EtherPeek/TokenPeek/AiroPeek, and many others
Capture files compressed with gzip can be decompressed on the fly
Live data can be read from Ethernet, IEEE 802.11, PPP/HDLC, ATM, Bluetooth, USB, Token Ring, Frame Relay, FDDI, and others (depending on your platform)
Decryption support for many protocols, including IPsec, ISAKMP, Kerberos, SNMPv3, SSL/TLS, WEP, and WPA/WPA2
Coloring rules can be applied to the packet list for quick, intuitive analysis
Output can be exported to XML, PostScript®, CSV, or plain text [2]
As you can see, Wireshark can pretty much dissect a packet originating from virtually any source. How does this apply to us? In a Cisco class that I’m currently enrolled in, we were tasked with creating a subnet with a couple of switches. The switches were assigned management IP addresses and connected to host computers. Cross over cables connected the switches to replace the function of a router. After the hosts could successfully ping each other over the networks, we installed Wireshark and began inspecting packets.

The following shows a sample packet capture and inspection from Wireshark. The source and destination IP addresses are mapped, along with the protocol and associated information displayed in a column. There is a detailed view starting at the second half of the application window. In the screenshot above, the frame and Reassembled TCP packet is displayed. The packet is in hexadecimal format, followed by a translated decimal view. It breaks the object all the way down to the frame!
I don’t know if it’s the deepest inspecting protocol analyzer, because I haven’t used them all. However, if you’re trying to troubleshoot poor network performance, track rogue network administrators or just get a better understanding of the OSI model, this is the program I recommend.




