Networking: UDP (User Datagram Protocol)
What It Is
UDP is a connectionless transport-layer protocol, defined in RFC 768: it sends data ("datagrams") to a destination with no handshake, no connection setup, and no acknowledgment that the data actually arrived — sometimes described as "fire-and-forget." UDP does not guarantee delivery, ordering, or protection against duplicate packets; if a packet is dropped in transit, it is simply lost, and UDP does not detect or correct this on its own. Any reliability, ordering, or retransmission a UDP-based application needs (if any) has to be built into the application/protocol running on top of it — UDP itself provides none of it.
Header Structure
UDP's header is minimal — just 8 bytes, versus TCP's minimum 20 bytes — containing only four fields: source port, destination port, length (of header + data), and checksum. There's no sequence number, no acknowledgment number, no window size, and no connection-state flags, because UDP has no concept of a connection to track. This low overhead is part of why UDP is cheaper, in both bandwidth and processing, than TCP for small, frequent messages.
Why That's Actually Useful for Real-Time Traffic
UDP's lack of overhead (no handshake, no retransmission delays, no waiting for acknowledgments) makes it faster and lower-latency than TCP — a significant advantage for real-time media like live audio and video, where a dropped packet causing a brief audio glitch is preferable to TCP's approach of pausing everything to retransmit a lost packet in order.
Where UDP Shows Up in Two-Way Radio and Support Work
- Presence/registration: ARS (Automatic Registration Service) uses UDP port 4005 by default.
- Name resolution: DNS queries normally use UDP (falling back to TCP only for larger responses or zone transfers).
- Address assignment: DHCP runs over UDP, including its initial broadcast Discover step.
- Monitoring/logging: SNMP traps and Syslog messages are both commonly sent over UDP.
- Time synchronization: NTP uses UDP port 123.
- Multicast and broadcast traffic can only travel over UDP, never TCP (which is inherently a one-to-one connection) — see Unicast, Broadcast, and Multicast for where multicast is and isn't actually used in real LMR system designs.
Common Misunderstandings
- "UDP is unreliable, so it's a worse/broken protocol" — it isn't broken, it's a different tool: UDP trades guaranteed delivery for low latency and low overhead, which is exactly the right trade for traffic where a late-arriving retransmission is useless (live voice) or where the application handles its own reliability semantics more efficiently than TCP would (many request/response protocols like DNS just resend the whole query if no answer arrives in time).
- "No handshake means UDP is insecure" — connection setup and security are separate concerns; UDP has no built-in encryption or authentication either, but neither does raw TCP. Protocols that need security add it themselves regardless of transport (e.g., WireGuard runs its own encrypted protocol over UDP).
- "If a firewall passes ping and TCP, it'll pass UDP fine too" — not necessarily. See the troubleshooting note below.
Troubleshooting Implications
- UDP and firewalls/NAT behave differently than TCP. Because UDP has no connection-open/connection-close signaling (no SYN, no FIN/RST), a firewall or NAT device can't tell when a UDP "session" is really over — it can only infer it from an idle timeout, and many devices apply a much shorter idle timeout to UDP state-table entries than to TCP connections. A long-idle UDP-based session (e.g., a monitoring feed that only sends data occasionally) can have its NAT/firewall mapping silently expire and then fail to resume without a new outbound packet re-opening it — a classic cause of "it was working, then just stopped" for UDP-based links.
- A firewall rule that allows a TCP control/signaling port but not the paired UDP media port produces the classic "the application connects fine, but there's no audio" symptom in RoIP/VoIP systems — see Troubleshooting RoIP and Gateway Connectivity for the full layered troubleshooting approach, and confirm both protocols independently rather than assuming one implies the other is open.
- Packet capture is the definitive tool for confirming whether UDP traffic is actually flowing (and in which direction) versus being silently dropped somewhere in the path — see Wireshark and Packet Capture.
Related Pages
- Networking: TCP
- RoIP (Radio over IP)
- Latency, Jitter, and Packet Loss in Voice Networks
- Networking: DNS
- Networking: DHCP
- Unicast, Broadcast, and Multicast
- NAT (Network Address Translation)
- Troubleshooting RoIP and Gateway Connectivity
References
See also: CTI product documentation
This article is part of the CTI Products Knowledge Base. Questions about RadioPro or MCN products? Call +1 (513) 595-5900 or email info@ctiproducts.com.
Informational only. This article is general background and is not engineering, safety, legal or regulatory advice. Verify requirements with the equipment manufacturer and the applicable authority before relying on it. Product names and trademarks belong to their respective owners.