Lines Matching refs:using

32 are set up using the Linux kernel API, we're just setting up the L2TP
43     2) Create a tunnel context in the kernel, using information
44        obtained from the peer using the control protocol messages.
49     4) Create a session context in the kernel using information
50        obtained from the peer using the control protocol messages.
65 For example, for a tunnel using IPv4 addresses and UDP encapsulation::
69 Or for a tunnel using IPv6 addresses and IP encapsulation::
80 should bind the L2TPIP socket using the locally assigned
85 from peers using L2TPIP, it must open a dedicated L2TPIP
86 socket to listen for those requests and bind the socket using tunnel
114 creates a kernel socket for the tunnel, using IP parameters set in
260 Sample userspace code using libmnl_:
312         /* there are other session options which can be set using netlink
366 Userspace may control behavior of the tunnel or session using
382 to retrieve tunnel and session statistics from the kernel using the
420 tunnel and session instances in the kernel were managed directly using
426     - Tunnels are managed using a tunnel management socket which is a
434       are set using setsockopt. The L2TP session instance is destroyed
448 configuration is done using netlink. There is no need for an L2TP
450 the kernel and configured using parameters sent in the
476 In addition the L2TP subsystem implements tracepoints using the standard
495 tunnel is created using a UDP socket, the socket is set up as an
572 tunnel can be identified using the tunnel socket's sk_user_data and
584 Userspace sends and receives PPP packets over L2TP using a PPPoL2TP
642      used. The kernel's tunnel context is identified using private
649   3) VLAN pseudowires are implemented using an ``l2tpethN`` interface