![]() |
![]()
| ![]() |
![]()
NAME
SYNOPSIS
int
DESCRIPTIONUDP is a simple, unreliable datagram protocol which is used to
support the 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
FIB supportUDP sockets are FIB-aware. They inherit the FIB of the process
which created the socket. By default, a UDP socket bound to an address can
receive datagrams originating from any FIB. If the
net.inet.udp.bind_all_fibs tunable is set to 0, all
UDP sockets will receive only datagrams originating from the same FIB as the
socket. In this mode, multiple sockets can be bound to the same address, so
long as each socket belongs to a different FIB, similar to the behavior of
the MIB (sysctl) VariablesThe
ERRORSA socket operation may fail with one of the following errors returned:
SEE ALSOgetsockopt(2), recv(2), send(2), socket(2), blackhole(4), inet(4), intro(4), ip(4), udplite(4) HISTORYThe
|