Lines Matching refs:tunnel
3 more sessions over an IP tunnel. It is commonly used for VPNs
4 (L2TP/IPSec) and by ISPs to tunnel subscriber PPP sessions over an IP
21 L2TPv2 functionality (rfc2661). L2TPv2 is used to tunnel one or more PPP
22 sessions over a UDP tunnel.
25 to be passed over an L2TP tunnel by moving the PPP-specific parts of
49 Each L2TP tunnel is implemented using a UDP or L2TPIP socket; L2TPIP
51 new l2tpip socket family. The tunnel socket is typically created by
71 tunnel, the interface can be given an IP addresses of itself and its
72 peer. If non-IP frames are to be passed over the tunnel, the interface
76 Each tunnel and session within a tunnel is assigned a unique tunnel_id
81 internal tunnel and/or session contexts to determine how to handle the
82 packet. Zero tunnel / session ids are treated specially - zero ids are
84 the tunnel context keeps a reference to the tunnel UDP or L2TPIP
94 1. Use a UDP socket per tunnel.
96 2. Create a single PPPoL2TP socket per tunnel bound to a special null
98 must remain open while the tunnel is active. Opening this tunnel
99 management socket causes the driver to mark the tunnel socket as an
101 referenced tunnel id. This hooks up the UDP receive path via
107 arguments. A PPPoL2TP tunnel management socket (Step 2) must be
112 destination tunnel and session ids are provided, as well as the file
114 include/linux/if_pppol2tp.h. Note that zero tunnel / session ids are
115 treated specially. When creating the per-tunnel PPPoL2TP management
118 descriptor for use as an L2TP tunnel socket.
120 Userspace may control behavior of the tunnel or session using
133 Only the DEBUG option is supported by the special tunnel management
137 to retrieve tunnel and session statistics from the kernel using the
138 PPPoX socket of the appropriate tunnel or session.
141 include/linux/l2tp.h to manage tunnel and session contexts. The
142 general procedure to create a new L2TP tunnel with one session is:-
147 2. Create a UDP or L2TPIP socket for the tunnel.
149 3. Create a new L2TP tunnel using a L2TP_CMD_TUNNEL_CREATE
150 request. Set attributes according to desired tunnel parameters,
153 4. Create a new L2TP session in the tunnel using a
156 The tunnel and all of its sessions are closed when the tunnel socket
162 setup the tunnel; the tunnel is configured manually at each end of the
163 tunnel. There is no need for an L2TP userspace application in this
164 case -- the tunnel socket is created by the kernel and configured
173 messages may be optionally enabled per tunnel and per session. Care is
214 tunnel endpoints:-
216 # ip l2tp add tunnel tunnel_id 1 peer_tunnel_id 1 udp_sport 5000 \
227 Repeat the above at the peer, with ports, tunnel/session ids and IP
228 addresses reversed. The tunnel and session IDs can be any non-zero
239 When done at both ends of the tunnel, it should be possible to send
248 1. Create tunnel management PPPoX socket
255 peer_addr = l2tp_tunnel_get_peer_addr(tunnel);
259 sax.pppol2tp.fd = udp_fd; /* fd of tunnel UDP socket */
293 * tunnel_fd is the fd of the tunnel UDP socket.
304 The driver keeps a struct l2tp_tunnel context per L2TP tunnel and a
307 sessions in the tunnel. The l2tp_session context keeps kernel state
314 When a tunnel is first opened, the reference count on the socket is
327 Add L2TP tunnel switching support. This would route tunneled traffic
328 from one L2TP tunnel into another. Specified in
329 http://tools.ietf.org/html/draft-ietf-l2tpext-tunnel-switching-08