Lines Matching full:session
28 associated with a socket. Each session is associated with a virtual
30 to/from L2TP. Fields in the L2TP header identify the tunnel or session
47 tunnel socket in order to establish a session.
49 4) Create a session context in the kernel using information
95 L2TP applications use netlink to manage L2TP tunnel and session
100 Create, Delete, Modify and Get for tunnel and session
104 Tunnel and session instances are identified by a locally unique
106 ``L2TP_ATTR_PEER_CONN_ID`` attributes and L2TP session ids are given
108 attributes. If netlink is used to manage L2TPv2 tunnel and session
109 instances, the L2TPv2 16-bit tunnel/session id is cast to a 32-bit
184 SESSION_ID Y Sets the session id.
185 PEER_SESSION_ID Y Sets the parent session id.
201 For Ethernet session types, this will create an l2tpeth virtual
202 interface which can then be configured as required. For PPP session
204 onto the new session. This is covered in "PPPoL2TP Sockets" later.
211 CONN_ID Y Identifies the parent tunnel id of the session
213 SESSION_ID Y Identifies the session id to be destroyed.
214 IFNAME N Identifies the session by interface name. If
225 CONN_ID Y Identifies the parent tunnel id of the session
227 SESSION_ID Y Identifies the session id to be modified.
228 IFNAME N Identifies the session by interface name. If
248 SESSION_ID N Identifies the session id to be queried.
250 IFNAME N Identifies the session by interface name.
292 - Create a session::
312 /* there are other session options which can be set using netlink
313 * attributes during session creation -- see l2tp.h
316 - Delete a session::
351 PPPoL2TP Session Socket API
354 For PPP session types, a PPPoL2TP socket must be opened and connected
355 to the L2TP session.
358 to the kernel about the tunnel and session in a socket connect()
359 call. Source and destination tunnel and session ids are provided, as
366 Userspace may control behavior of the tunnel or session using
382 to retrieve tunnel and session statistics from the kernel using the
383 PPPoX socket of the appropriate tunnel or session.
387 - Create session PPPoX data socket::
413 /* session_fd is the fd of the session's PPPoL2TP socket.
428 /* Input: the session PPPoX data socket `session_fd` which was created
492 /* Input: the session PPPoX data sockets `session_fd1` and `session_fd2`
526 It can be noted that when bridging PPP channels, the PPP session is not locally
530 The PPP channel does not need to be kept open. Only the session PPPoX data
543 tunnel and session instances in the kernel were managed directly using
545 section "PPPoL2TP Session Socket API" but tunnel and session instances
550 dedicated PPPoL2TP socket, connected to (invalid) session
555 - Session instances are created in the kernel when a PPPoL2TP
556 socket is connected to a non-zero session id. Session parameters
557 are set using setsockopt. The L2TP session instance is destroyed
562 session, then create a PPPoL2TP socket for the session.
589 of the current population of tunnel and session contexts existing in the
653 first closed. Each session drops its tunnel ref. When the tunnel ref
659 The kernel keeps a struct l2tp_session context for each session. Each
660 session has private data which is used for data specific to the
661 session type. With L2TPv2, the session always carries PPP
662 traffic. With L2TPv3, the session can carry Ethernet frames (Ethernet
664 Relay. Linux currently implements only Ethernet and PPP session types.
666 Some L2TP session types also have a socket (PPP pseudowires) while
670 session id. Just as with tunnel ids, the session id is 16-bit for
680 session ID. L2TPv3 sessions are keyed by the 32-bit session ID, since
681 L2TPv3 session ids are unique across all tunnels.
683 Although the L2TPv3 RFC specifies that L2TPv3 session ids are not
685 allowed this. Such session id collisions are supported using a per-net
686 hash table keyed by sk and session ID. When looking up L2TPv3
688 session ID, in which case the session matching the given sk (tunnel)
695 session has a PPPoL2TP socket.
702 session and its associated ``pppN`` netdev through the PPP channel
706 by closing its corresponding L2TP session. This is complicated because
707 it must consider racing with netlink session create/destroy requests
708 and pppol2tp_connect trying to reconnect with a session that is in the
710 socket in order that the socket remains extants while the session
717 manages a netdev for each session.
762 pair per VLAN session. The netlink attribute
773 of the L2TP APIs and tunnel/session types. This may be integrated into