roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Prepare for Wireshark interview questions on capturing and reading traffic, from filters and dissectors to TCP analysis. Covers the protocols on the wire, streams, statistics and TLS decryption.
137 of 137 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 137 new. 0 cut, outside your plan.
Wireshark rarely gets a round of its own. It surfaces inside the technical conversation of a SOC analyst, network engineer or security engineer loop, often as a capture put in front of you: a file from a user whose application hangs, or the traffic behind an alert, and the request to say what happened. Some loops do this live on a shared screen; others describe the trace and ask which filter you would type. The first questions separate the two filter languages, since `host 10.0.0.5` belongs in the capture options and `ip.addr == 10.0.0.5` in the display filter bar, and only one of them discards packets for good. Then comes the protocol view: why traffic on an unusual port shows up as bare TCP until you tell Wireshark how to decode it, and why a TLS session that used an ephemeral key exchange stays opaque even with the server's private key in hand. Stronger candidates read timing rather than payload. They take a round-trip time from the handshake, tell a receiver advertising a zero window from a path that drops segments, notice when the analyser's flags describe loss at the capture point rather than on the network, and ask where the capture was taken before trusting any of it.
Protocols come first, because everything Wireshark shows is a protocol decoded. The opening stretch is the stack the packet details pane unfolds, from [encapsulation](/topics/proto-osi-encapsulation) through [Ethernet frames](/topics/proto-ethernet-frames-mac), 802.11 [frame types](/topics/proto-wifi-frame-types) and the [IPv4 header](/topics/proto-ipv4-header) up to [TCP](/topics/proto-tcp), which gets the most room: its flags, sequence numbers and windows are what the analysis modules later interpret. The application layer is taken narrowly, only the parts a capture exposes: [DNS messages](/topics/proto-dns-message-format), [HTTP body framing](/topics/proto-http-headers-message-framing), and the [TLS handshake](/topics/proto-tls-handshake) with its [key exchange](/topics/proto-tls-key-exchange), which decides much later whether a session can be decrypted at all. Capturing Traffic turns to the tool, starting before Wireshark opens: how packets reach the machine through a [SPAN port or TAP](/topics/proto-network-telemetry-port-mirroring), and the [Linux capabilities](/topics/os-linux-permissions-capabilities) dumpcap needs to capture without root. [Interfaces and capture modes](/topics/sec-wireshark-capture-setup) follow, then the libpcap [filter language](/topics/sec-tcpdump-filters) Wireshark shares with tcpdump, ahead of [where Wireshark applies it](/topics/sec-wireshark-capture-filters). Reading what was captured is the next turn. [Display filters](/topics/sec-wireshark-display-filters) query the fields that [dissectors](/topics/sec-wireshark-protocol-dissectors) produce, so the two sit together, with Decode As and Lua on the dissector side. [Following streams](/topics/sec-wireshark-stream-analysis) and the [Expert Info and statistics](/topics/sec-wireshark-expert-statistics) views move from single packets to whole conversations, where most troubleshooting answers are found. [Decryption](/topics/sec-wireshark-tls-decryption) closes the plan because it draws on nearly everything before it: the handshake, the key exchange, stream reassembly, and a filter to confirm the plaintext arrived.
Analysts heading into a SOC loop get the most from the second half of the plan. Display filters, following a stream and the Expert Info flags are what a triage exercise leans on, so raise importance to must know and work those modules first. Network engineers weight it the other way: the TCP module and the statistics views carry their questions, and a senior network candidate should be able to explain a throughput graph from window and retransmission behaviour without opening a payload. If you have only ever read someone else's trace, capture your own browser session with a key log file set before the interview; decrypting it once teaches the TLS module faster than reading about it. The plan stays with the analyser and the protocols it decodes. Writing detections, triaging alerts and carrying an incident through response belong to the [SOC Analyst roadmap](/roadmaps/soc-analyst). Routing, switching and the design of the network a capture came from are in the [Network Engineer roadmap](/roadmaps/network-engineer).
Wireshark rarely gets a round of its own. It surfaces inside the technical conversation of a SOC analyst, network engineer or security engineer loop, often as a capture put in front of you: a file from a user whose application hangs, or the traffic behind an alert, and the request to say what happened. Some loops do this live on a shared screen; others describe the trace and ask which filter you would type.
The first questions separate the two filter languages, since host 10.0.0.5 belongs in the capture options and ip.addr == 10.0.0.5 in the display filter bar, and only one of them discards packets for good. Then comes the protocol view: why traffic on an unusual port shows up as bare TCP until you tell Wireshark how to decode it, and why a TLS session that used an ephemeral key exchange stays opaque even with the server's private key in hand. Stronger candidates read timing rather than payload. They take a round-trip time from the handshake, tell a receiver advertising a zero window from a path that drops segments, notice when the analyser's flags describe loss at the capture point rather than on the network, and ask where the capture was taken before trusting any of it.
Protocols come first, because everything Wireshark shows is a protocol decoded. The opening stretch is the stack the packet details pane unfolds, from encapsulation through Ethernet frames, 802.11 frame types and the IPv4 header up to TCP, which gets the most room: its flags, sequence numbers and windows are what the analysis modules later interpret. The application layer is taken narrowly, only the parts a capture exposes: DNS messages, HTTP body framing, and the TLS handshake with its key exchange, which decides much later whether a session can be decrypted at all.
Capturing Traffic turns to the tool, starting before Wireshark opens: how packets reach the machine through a SPAN port or TAP, and the Linux capabilities dumpcap needs to capture without root. Interfaces and capture modes follow, then the libpcap filter language Wireshark shares with tcpdump, ahead of where Wireshark applies it.
Reading what was captured is the next turn. Display filters query the fields that dissectors produce, so the two sit together, with Decode As and Lua on the dissector side. Following streams and the Expert Info and statistics views move from single packets to whole conversations, where most troubleshooting answers are found. Decryption closes the plan because it draws on nearly everything before it: the handshake, the key exchange, stream reassembly, and a filter to confirm the plaintext arrived.
Analysts heading into a SOC loop get the most from the second half of the plan. Display filters, following a stream and the Expert Info flags are what a triage exercise leans on, so raise importance to must know and work those modules first. Network engineers weight it the other way: the TCP module and the statistics views carry their questions, and a senior network candidate should be able to explain a throughput graph from window and retransmission behaviour without opening a payload. If you have only ever read someone else's trace, capture your own browser session with a key log file set before the interview; decrypting it once teaches the TLS module faster than reading about it.
The plan stays with the analyser and the protocols it decodes. Writing detections, triaging alerts and carrying an incident through response belong to the SOC Analyst roadmap. Routing, switching and the design of the network a capture came from are in the Network Engineer roadmap.