keepcalculator

06 Numbers and Powers

Read Packets in Wireshark: A Practical Guide

Card No. 06·78101 · Updated · Standard formula, shown below

Yes. Wireshark can read and analyze captured network packets, showing their protocols, addresses, ports, timing, and—when available—message contents. To inspect traffic, open a capture file or start a capture on a network interface, then use the packet list, packet details, and packet bytes panes to explore it.

What It Means to Read a Packet

A packet is a unit of data sent across a network. Depending on the network technology and protocol, a capture may contain frames, packets, or segments; people often use “packet” informally for any captured unit. Wireshark decodes the data it can recognize into layers, such as Ethernet or Wi-Fi, IP, TCP or UDP, and an application protocol such as DNS or HTTP.

This layered view helps answer questions like which device contacted a server, whether a DNS lookup succeeded, or when a TCP connection was established. It does not mean Wireshark automatically translates every byte into readable text. Some data is binary, some is encrypted, and some may be incomplete or malformed.

How Wireshark Displays Captured Traffic

Wireshark’s main packet view is organized into three panes:

  • Packet list: A row for each captured frame, with columns commonly showing its number, time, source, destination, protocol, length, and a brief summary.
  • Packet details: A hierarchical view of the selected frame’s decoded fields. Expand a protocol layer to examine values such as IP addresses, TCP flags, or DNS names.
  • Packet bytes: The raw captured bytes, displayed in hexadecimal and, where printable, as text. Selecting a decoded field can highlight the corresponding bytes.

Select a row to examine it. For example, a DNS query may show the client’s address, the resolver’s address, the requested domain, and the query type. A TCP packet may show sequence and acknowledgment numbers, flags such as SYN or ACK, and payload length. The exact fields depend on the protocols and data captured.

Opening a Capture or Starting One

For an existing capture, open the file in Wireshark. Common capture formats include PCAP and PCAPNG. The menus and wording can vary slightly by operating system and release, but the usual workflow is to choose a capture file or select a live interface from the start screen.

  1. Choose the right source. For a saved file, open that file. For live traffic, select the network interface that is actually carrying the traffic—for example, the active Wi-Fi or Ethernet connection.
  2. Check permissions and capture support. Live capture may require approved capture permissions or a supported capture driver. If no interfaces appear, check the installation, permissions, and operating-system capture setup.
  3. Start or inspect the capture. For live traffic, begin capturing, reproduce the behavior you are investigating, and stop when you have enough data. For a saved file, begin with its packet list.
  4. Save useful evidence carefully. Save a copy of a relevant capture if needed, and avoid collecting or sharing unrelated traffic.

Capturing the right interface matters: a computer may have separate interfaces for wired networking, wireless networking, VPNs, and virtual machines. A capture on the wrong one can look empty even when the computer is online.

Finding Packets with Display Filters

Display filters narrow what Wireshark shows without deleting packets from the capture. Enter a filter in the display-filter bar and apply it. Examples include dns for DNS traffic, tcp for TCP, ip.addr == 192.0.2.10 for packets involving that IPv4 address, and tcp.port == 443 for TCP traffic using port 443.

Filters can be combined with logical operators. For instance, dns && ip.addr == 192.0.2.10 displays DNS packets involving that address. Use field names and syntax supported by the installed Wireshark version; the filter bar indicates whether an expression is accepted, and autocomplete can help identify fields.

A display filter is different from a capture filter. A capture filter decides which traffic is recorded in the first place; a display filter selects among traffic already captured. If a capture filter excludes a packet, a later display filter cannot bring it back. When uncertain, capture broadly enough for the task and narrow the view afterward, while keeping privacy and storage in mind.

What You Can and Cannot Read

Wireshark can decode protocols for which it has suitable protocol support and enough captured data. Plain-text protocols may expose readable requests or responses. However, HTTPS and other encrypted connections generally reveal metadata—such as endpoints, timing, and packet sizes—rather than the protected application content. Wireshark does not simply bypass encryption.

Even unencrypted traffic may not be fully understandable. A capture can start partway through a conversation, omit packets, contain checksums affected by network-interface offloading, or include application data Wireshark cannot decode. TCP conversations can span many packets, so a single row may not contain a complete message. Follow a stream when appropriate, but interpret the result in the context of the capture and protocol.

Common Problems and Useful Checks

  • The capture is empty: Confirm that you chose the active interface, reproduced traffic during the capture, and have permission to capture. VPNs and virtual adapters may carry traffic on a different interface.
  • A filter shows nothing: Clear the display filter and check whether packets are present. Verify the address, protocol, and field syntax; a typo or wrong address family can exclude everything.
  • Names appear instead of addresses: Name resolution can make packet lists easier to read, but it can also add lookups or affect interpretation. Check the relevant name-resolution preferences or use address fields directly in filters.
  • Payload is unreadable: It may be encrypted, compressed, binary, or incomplete. Unreadable bytes alone do not prove that a packet is corrupt.
  • Packets appear missing or oddly timed: Capture location, dropped packets, clock settings, and network-interface offloading can affect what is recorded or displayed. Compare with another capture point when appropriate.

Privacy and Responsible Use

Packet captures can contain sensitive information, including device identifiers, internal addresses, browsing metadata, and—on some unencrypted protocols—message contents or credentials. Capture only traffic you own or are authorized to inspect, and follow your organization’s policies. Minimize the capture duration and scope, protect files with suitable access controls, and remove or redact sensitive data before sharing when possible.

Wireshark is an analysis tool, not permission to monitor other people’s communications. A capture file may remain sensitive even if it looks technical or contains no obvious text. Treat it accordingly, especially when uploading it to a support forum or sending it outside your organization.

Frequently Asked Questions

Can Wireshark read packets in real time?
Yes. Select the active network interface and start a live capture. Packets appear as they are captured, though permissions, interface selection, and capture support can affect whether this works.

Can Wireshark read HTTPS packets?
It can display and analyze the captured network packets, including connection metadata, but HTTPS content is encrypted. Decrypting traffic requires appropriate session secrets and authorization; Wireshark does not defeat encryption by itself.

How do I see only packets from one IP address?
Use a display filter such as ip.addr == 192.0.2.10, replacing the example address with the one you need. For IPv6, use the corresponding IPv6 field, such as ipv6.addr.

Why can’t I see any packets?
You may have selected an inactive interface, started capturing at the wrong time, lacked capture permissions, or applied a filter that matches nothing. Clear the filter and verify the interface while generating the traffic you expect to see.

Does Wireshark capture all network traffic?
No. What it sees depends on the capture point, interface, network configuration, permissions, and capture filters. On switched networks, a computer usually does not receive every other device’s unicast traffic.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →