Lines Matching refs:UDP
19 L2TPv3. L2TPv2 is carried over UDP. L2TPv3 is carried over UDP or
60 L2TPv2 always uses UDP. L2TPv3 may use UDP or IP encapsulation.
65 For example, for a tunnel using IPv4 addresses and UDP encapsulation::
73 UDP socket programming doesn't need to be covered here.
130 ENCAP_TYPE Y Encapsulation type: UDP or IP.
132 UDP_CSUM N Enable IPv4 UDP checksums. Used only if FD is
134 UDP_ZERO_CSUM6_TX N Zero IPv6 UDP checksum on transmit. Used only
136 UDP_ZERO_CSUM6_RX N Zero IPv6 UDP checksum on receive. Used only if
142 UDP_SPORT N UDP source port. Used only if FD is not set.
143 UDP_DPORT N UDP destination port. Used only if FD is not
360 well as the file descriptor of a UDP or L2TPIP socket. See struct
407 * tunnel_fd is the fd of the tunnel UDP / L2TPIP socket.
494 UDP sockets are implemented by the networking core. When an L2TP
495 tunnel is created using a UDP socket, the socket is set up as an
496 encapsulated UDP socket by setting encap_rcv and encap_destroy
497 callbacks on the UDP socket. l2tp_udp_encap_recv is called when
508 l2tp_tunnel is always associated with a UDP or L2TP/IP socket and
527 socket. For UDP sockets, when userspace closes the tunnel socket, the
569 scoped by the tunnel, the kernel does not police this for L2TPv3 UDP
570 tunnels and does not add sessions of L2TPv3 UDP tunnels into the
571 per-net session list. In the UDP receive code, we must trust that the
641 1) Multiple UDP sockets with the same 5-tuple address cannot be