NAME<\/a> udplite \u2212 Lightweight User Datagram Protocol<\/p>\n #include sockfd = socket(AF_INET, SOCK_DGRAM, IPPROTO_UDPLITE);<\/b><\/p>\n This is an implementation of the Lightweight User Datagram Protocol (UDP-Lite), as described in RFC\u00a03828.<\/p>\n UDP-Lite is an extension of UDP (RFC\u00a0768) to support variable-length checksums. This has advantages for some types of multimedia transport that may be able to make use of slightly damaged datagrams, rather than having them discarded by lower-layer protocols.<\/p>\n The variable-length checksum coverage is set via a setsockopt<\/b>(2) option. If this option is not set, the only difference from UDP is in using a different IP protocol identifier (IANA number 136).<\/p>\n The UDP-Lite implementation is a full extension of udp<\/b>(7)\u2014that is, it shares the same API and API behavior, and in addition offers two socket options to control the checksum coverage.<\/p>\n Address format<\/b> Socket options<\/b> The following two options are specific to UDP-Lite. This option sets the sender checksum coverage and takes an int<\/i> as argument, with a checksum coverage value in the range 0..2^16-1.<\/p>\n A value of 0 means that the entire datagram is always covered. Values from 1\u22127 are illegal (RFC\u00a03828, 3.1) and are rounded up to the minimum coverage of 8.<\/p>\n With regard to IPv6 jumbograms (RFC\u00a02675), the UDP-Litev6 checksum coverage is limited to the first 2^16-1 octets, as per RFC\u00a03828, 3.5. Higher values are therefore silently truncated to 2^16-1. If in doubt, the current coverage value can always be queried using getsockopt<\/b>(2).<\/p>\n UDPLITE_RECV_CSCOV<\/b><\/p>\n This is the receiver-side analogue and uses the same argument format and value range as UDPLITE_SEND_CSCOV<\/b>. This option is not required to enable traffic with partial checksum coverage. Its function is that of a traffic filter: when enabled, it instructs the kernel to drop all packets which have a coverage less<\/i> than the specified coverage value.<\/p>\n When the value of UDPLITE_RECV_CSCOV<\/b> exceeds the actual packet coverage, incoming packets are silently dropped, but may generate a warning message in the system log.<\/p>\n All errors documented for udp<\/b>(7) may be returned. UDP-Lite does not add further errors.<\/p>\n \/proc\/net\/snmp<\/i><\/p>\n Basic UDP-Litev4 statistics counters.<\/p>\n \/proc\/net\/snmp6<\/i><\/p>\n Basic UDP-Litev6 statistics counters.<\/p>\n UDP-Litev4\/v6 first appeared in Linux 2.6.20.<\/p>\n Where glibc support is missing, the following definitions are needed:<\/p>\n #define IPPROTO_UDPLITE 136 ip<\/b>(7), ipv6<\/b>(7), socket<\/b>(7), udp<\/b>(7)<\/p>\n RFC\u00a03828 for the Lightweight User Datagram Protocol (UDP-Lite).<\/p>\n
SYNOPSIS<\/a>
DESCRIPTION<\/a>
ERRORS<\/a>
FILES<\/a>
VERSIONS<\/a>
BUGS<\/a>
SEE ALSO<\/a>
COLOPHON<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
UDP-Litev4 uses the sockaddr_in<\/i> address format described in ip<\/b>(7). UDP-Litev6 uses the sockaddr_in6<\/i> address format described in ipv6<\/b>(7).<\/p>\n
To set or get a UDP-Lite socket option, call getsockopt<\/b>(2) to read or setsockopt<\/b>(2) to write the option with the option level argument set to IPPROTO_UDPLITE<\/b>. In addition, all IPPROTO_UDP<\/b> socket options are valid on a UDP-Lite socket. See udp<\/b>(7) for more information.<\/p>\n
UDPLITE_SEND_CSCOV<\/b><\/p>\nERRORS <\/a> <\/h2>\n
FILES <\/a> <\/h2>\n
VERSIONS <\/a> <\/h2>\n
BUGS <\/a> <\/h2>\n
#define UDPLITE_SEND_CSCOV 10
#define UDPLITE_RECV_CSCOV 11<\/p>\nSEE ALSO <\/a> <\/h2>\n