Learn / Field guide

UDP: fast, connectionless messages

UDP sends single messages with no handshake and no delivery guarantee. It's used where speed matters more than reliability, or where the application handles retries itself: DNS, video calls, games, QUIC.

11 UDP fields, explained

Field names are the ones Wireshark and TShark use, so you can search for them or use them in display filters.

udp.srcport

The port number on the sending side.

udp.dstport

The port number on the receiving side.

Why it matters: 53 is DNS, 123 is NTP (time), 5353 is multicast DNS.

udp.length

The size of the UDP header plus its data.

udp.checksum

An optional check value for the UDP header and data.

udp.stream

A number Wireshark gives each UDP conversation in the capture.

udp.stream.pnum

This packet's position within its UDP conversation.

udp.time_relative

Time since this UDP conversation's first packet.

udp.time_delta

Time since the previous packet in this UDP conversation.

udp.payload

The data this datagram carries for the application.

udp

A UDP header. Inside an ICMP error, this is the start of the packet that caused the error.

Why it matters: Traceroute matches replies to its probes using the quoted destination port.

udp.possible_traceroute

Wireshark's note that this UDP packet looks like a traceroute probe: a low TTL to a port in the 33434+ range.

Why it matters: Traceroute sends probes with TTL 1, 2, 3… so each router along the path answers in turn.