Wireshark for Beginners: Reading Your First Packet Capture
Network traffic looks like noise until you know what to filter. Then it tells you everything.
The first time I opened Wireshark on a live network capture, I saw 800 packets per second scrolling past in a blur and immediately wanted to close the tab. But once I learned three filters, I went from overwhelmed to genuinely fascinated. You can do the same in the next 20 minutes.
What is Wireshark?
Wireshark is a free, open-source network packet analyser. It captures the raw packets flowing through your network interface and lets you inspect them in detail — every protocol, every header, every byte of data. Security analysts use it to debug network issues, investigate incidents, analyse malware traffic, and understand how protocols work at a deep level.
Download it free at wireshark.org. It works on Windows, Mac, and Linux.
Starting your first capture
- Open Wireshark
- On the start screen, you'll see a list of network interfaces (Wi-Fi, Ethernet, loopback, etc.). You'll see a wavy line next to active interfaces showing live traffic.
- Double-click your active interface (usually Wi-Fi or Ethernet) to start capturing
- Browse a few websites, then press the red Stop button (or Ctrl+E)
You now have a packet capture. It'll look like an overwhelming list. That's fine — the next step is filtering it down to what matters.
The 5 most useful display filters
Wireshark's display filters let you isolate specific traffic without discarding anything from your capture. Type these in the filter bar at the top:
# Show only DNS queries and responses
dns
# Show only HTTP traffic
http
# Show only TLS traffic (HTTPS handshakes)
tls
# Show traffic to or from a specific IP
ip.addr == 142.250.70.46
# Show only TCP connection initiations (SYN packets)
tcp.flags.syn == 1 and tcp.flags.ack == 0
What to look for — a DNS query walkthrough
Apply the filter dns. You'll see DNS queries (your machine asking "what's the IP for google.com?") and DNS responses (the answer). Click on any DNS query packet. You'll see three panes:
- Top pane (packet list): timestamp, source IP, destination IP, protocol, brief info
- Middle pane (packet details): expandable tree of protocol headers — Ethernet → IP → UDP → DNS
- Bottom pane (raw bytes): the actual hex and ASCII of the packet
Expand the DNS section in the middle pane. You'll see: the query name (the domain being looked up), the query type (A = IPv4 address, AAAA = IPv6), and in the response, the IP address returned. This is DNS — right in front of you, completely readable.
Follow a full HTTP conversation
Apply the filter http, then right-click any HTTP packet → Follow → TCP Stream. Wireshark reconstructs the full request-response conversation as readable text. You'll see the HTTP request your browser sent (with headers like User-Agent, Accept-Language) and the server's full response including the HTML. This is exactly what an attacker sees on an unencrypted HTTP connection — everything, in plain text.
💡 Useful tip If you want to practice without capturing live traffic, download sample .pcap files from wiki.wireshark.org/SampleCaptures. There are captures of malware traffic, VoIP calls, HTTP sessions, and more — great for learning without needing to generate your own traffic.
Identifying a port scan in Wireshark
Apply the filter tcp.flags.syn == 1 and tcp.flags.ack == 0. This shows only SYN packets — the first step of TCP connections. If you see one source IP sending SYN packets to dozens or hundreds of different ports on the same destination IP in a short time window, that is a port scan. The pattern is unmistakable once you know what you're looking for.
Why this skill matters
Wireshark is a window into exactly what your network is doing. When alerts fire in a SIEM, packet captures often provide the ground truth — is this traffic genuinely malicious or a false positive? Is this malware actually communicating, or just trying to? Every security analyst benefits from being comfortable reading packet captures, even at a basic level.
About the author
Security operation centre analyst | Vulnerability management and penetration testing (VAPT) | Qualys Compliance | Cloud security
Comments
Join the discussionNo comments yet. Be the first to comment.
Network basics
A series breaking down core networking concepts every security professional should know — from the OSI model to how data actually moves across networks. Written for anyone building a strong foundation before diving into vulnerability management, pentesting, or cloud security

