| Main index | Section 4 | 日本語 | Options |
#include <sys/types.h>
#include <sys/socket.h>
#include <netinet/in.h>
UDP address formats are identical to those used by TCP. In particular UDP provides a port identifier in addition to the normal Internet address format. Note that the UDP port space is separate from the TCP port space (i.e., a UDP port may not be "connected" to a TCP port). In addition broadcast packets may be sent (assuming the underlying network supports this) by using a reserved "broadcast address"; this address is network interface dependent.
Options at the IP transport level may be used with UDP; see ip(4). UDP_ENCAP socket option may be used at the IPPROTO_UDP level to encapsulate ESP packets in UDP. Only one value is supported for this option: UDP_ENCAP_ESPINUDP from RFC 3948, defined in <netinet/udp.h>.
| blackhole | |
| When a datagram is received on a port where there is no socket listening, do not return an ICMP port unreachable message. (Disabled by default. See blackhole(4).) | |
| checksum | |
| Enable UDP checksums (enabled by default). | |
| log_in_vain | |
| For all UDP datagrams, to ports on which there is no socket listening, log the connection attempt (disabled by default). | |
| maxdgram | |
| Maximum outgoing UDP datagram size | |
| recvspace | |
| Maximum space for incoming UDP datagrams | |
| [EISCONN] | |
| when trying to establish a connection on a socket which already has one, or when trying to send a datagram with the destination address specified and the socket is already connected; | |
| [ENOTCONN] | |
| when trying to send a datagram, but no destination address is specified, and the socket has not been connected; | |
| [ENOBUFS] | |
| when the system runs out of memory for an internal data structure; | |
| [EADDRINUSE] | |
| when an attempt is made to create a socket with a port which has already been allocated; | |
| [EADDRNOTAVAIL] | |
| when an attempt is made to create a socket with a network address for which no network interface exists. | |
| UDP (4) | January 20, 2025 |
| Main index | Section 4 | 日本語 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
| “ | A typical Unix /bin or /usr/bin directory contains a hundred different kinds of programs, written by dozens of egotistical programmers, each with its own syntax, operating paradigm, rules of use ... strategies for specifying options, and different sets of constraints. | ” |
| — The Unix Haters' handbook | ||