Draft:Applications: Wireshark

• Comment: In accordance with Wikipedia's Conflict of interest guideline, I disclose that I have a conflict of interest regarding the subject of this article. Oluwatobi TJ (talk) 16:09, 8 June 2026 (UTC)

---

Project 2-2: Install and Use Wireshark | Chapter 2

In this page I will explain how to complete project 2-2 from the CompTIA Network+ Guide to Networks by Jill West. Its an interesting project that involves downloading and installing Wireshark from the internet, as well as performing diagnostics on network packets and protocols. Let us begin.

Downloading Wireshark

to download Wireshark proceed to https://www.wireshark.org/#download or click this download link. Select the release that is compatible with your platform and the file should be downloaded to your platform. Open the executable file and proceed with the installation process. If you need help installing Wireshark, proceed to watch this Youtube video by ZacsTech titled "How to Install Wireshark on Windows 11/10: Step-by-Step Guide".

My setup

For this project I am using a Packard Bell Carrera-F3 running windows 11 pro. It has a 16GB memory and a 500GB hard drive. It runs an AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx, 2600 Mhz, 2 Core(s), 4 Logical Processor(s).

Key Technical Concepts Learned

1. Real-Time Packet Capture & Interface Selection

• Learned how to identify active network interfaces (NICs) handling traffic.
• Mastered starting, stopping, and navigating live packet captures using the control ribbon interface.

Capturing packets using Wireshark

2. The Three-Pane Wireshark Architecture

• Top Pane (Packet List): Displays a summary of every captured frame, including timestamp, source/destination IP addresses, protocol types, and basic info lengths.
• Middle Pane (Packet Details): Breaks down a selected packet protocol-by-protocol, illustrating how headers map directly to the layers of the OSI model.
• Bottom Pane (Packet Bytes): Shows the raw data in hexadecimal and ASCII format.

3. Data Encapsulation & OSI Layer Mapping

By analyzing specific packets generated during the lab (via web browsing and running ping 8.8.8.8 in the CLI), a concrete understanding of layer stack differences was achieved:

• ICMP Traffic (Ping): Demonstrates 4 layers of information. It skips the traditional Transport layer, mapping directly from the Data Link layer (Ethernet II / Frame) through the Network layer (IPv4) to the Internet Control Message Protocol (ICMP).

  

  A screenshot of the Wireshark application interface, showing captured packet data.

• DNS Traffic: Demonstrates 5 layers of information. It fully encapsulates from the physical frame up through the Data Link layer (Ethernet), Network layer (IP), Transport layer (UDP), and the Application layer (Domain Name System).

A screenshot of the Wireshark application interface, showing captured packet data.

Lab Reflection & Observations

Network Visibility: Running a capture for even a few seconds reveals massive background network noise (broadcasts, background API hits, and local routing talk). It highlights that networking isn't just a static connection, but a constant, rapid dialogue between devices. Source/Destination Analysis: Analyzing the source and destination columns clearly shows how your local private IP interacts with your default gateway (router) to route requests out to external public DNS and web servers (like Google's 8.8.8.8 or Cengage).