Common OS Errors When Sending UDP Packets

While the User Datagram Protocol (UDP) is a connectionless, best-effort transport protocol, the host operating system still performs local validation, memory allocation, routing lookups, and interface checks prior to transmitting a datagram. When an issue occurs at the local socket layer, the network stack, or via an asynchronous ICMP response, the operating system returns specific error codes—typically defined via POSIX errno on Unix-like systems or Winsock error codes on Windows. Below are the most common OS errors encountered when sending UDP packets, their causes, and how to resolve them.

1. Message Too Long (EMSGSIZE / WSAEMSGSIZE)

• Cause: The datagram size exceeds the maximum payload size supported by the local network interface’s Maximum Transmission Unit (MTU), the socket’s internal buffer limit, or the maximum theoretical limit of UDP (65,507 bytes for IPv4). It can also occur if the “Don’t Fragment” (DF) bit is set and the packet size exceeds the path MTU.
• Resolution: Reduce the size of the payload to fit within the standard MTU (commonly 1,500 bytes on Ethernet, resulting in a safe payload of ~1,472 bytes for IPv4), implement application-level fragmentation, or adjust socket buffer sizes.

2. No Buffer Space Available (ENOBUFS / WSAENOBUFS)

• Cause: The operating system’s outgoing network queues or socket send buffers are completely full. This happens when an application transmits UDP datagrams faster than the physical network interface or OS network stack can dispatch them.
• Resolution: Increase the socket send buffer using setsockopt with the SO_SNDBUF option, rate-limit the application’s transmission speed, or optimize the OS kernel’s network queuing parameters.

3. Resource Temporarily Unavailable (EAGAIN / EWOULDBLOCK / WSAEWOULDBLOCK)

• Cause: Returned by non-blocking sockets when the send buffer is full and cannot immediately accept new data for transmission without blocking the thread.
• Resolution: Use I/O multiplexing mechanisms (such as epoll, kqueue, poll, or select) to wait until the socket becomes writable again before attempting to send subsequent packets.

4. Permission Denied (EACCES / EPERM / WSAEACCES)

• Cause: The application is attempting an operation restricted by local permissions or firewall rules. Common triggers include trying to send a broadcast packet to a subnet (e.g., 255.255.255.255) without enabling the SO_BROADCAST socket option, or being blocked by local packet filters (e.g., iptables, nftables, or Windows Defender Firewall).
• Resolution: Explicitly enable SO_BROADCAST via setsockopt if sending broadcast traffic, or configure local firewall rules to permit outbound UDP traffic for the application.

5. Connection Refused (ECONNREFUSED / WSAECONNREFUSED)

• Cause: Although UDP is connectionless, if a socket is explicitly connected to a remote address using connect(), the OS can associate asynchronous incoming ICMP “Port Unreachable” (Type 3, Code 3) messages from previous transmissions with the socket. The next send() or write() call will then return this error.
• Resolution: Verify that the destination host is active and that the target service is actively listening on the specified port.

6. Network Unreachable (ENETUNREACH / WSAENETUNREACH) and Host Unreachable (EHOSTUNREACH / WSAEHOSTUNREACH)

• Cause: The operating system cannot find a route to the destination IP address in its routing table (ENETUNREACH), or a local/remote router has returned an ICMP “Host Unreachable” message indicating the destination node is unreachable (EHOSTUNREACH).
• Resolution: Check local network connectivity, ensure default gateways and routing tables are properly configured, and verify the destination IP address.

7. Address Not Available (EADDRNOTAVAIL / WSAEADDRNOTAVAIL)

• Cause: The socket was bound to a local IP address or interface that does not exist on the host machine, or an ephemeral source port could not be allocated because the local port range is exhausted.
• Resolution: Ensure the application binds to valid local IP addresses (or INADDR_ANY / in6addr_any), and tune ephemeral port range settings or recycle sockets to prevent port exhaustion.