Lines Matching refs:session

53 created by the kernel. Each L2TP session (pseudowire) gets a network
60 mechanism by which PPP frames carried through an L2TP session are
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
85 socket. The session context holds data that lets the driver interface
97    session id. This is used only for communicating with the driver but
105 3. Create a PPPoL2TP socket per L2TP session. This is typically done
108    created before the first PPPoL2TP session socket is created.
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
116 socket in Step 2 above, zero source and destination session ids are
120 Userspace may control behavior of the tunnel or session using
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:-
153 4. Create a new L2TP session in the tunnel using a
173 messages may be optionally enabled per tunnel and per session. Care is
218 # ip l2tp add session tunnel_id 1 session_id 1 peer_session_id 1
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
275 2. Create session PPPoX data socket
292         /* session_fd is the fd of the session's PPPoL2TP socket.
305 struct l2tp_session context for each session. The l2tp_tunnel is
308 about the session. It has private data which is used for data specific
309 to the session type. With L2TPv2, the session always carried PPP
310 traffic. With L2TPv3, the session can also carry ethernet frames
320 as the reference count for session contexts. The L2TP implementation
321 therefore has its own internal reference counts on the session