Lines Matching refs:sessions
27 An L2TP tunnel carries one or more L2TP sessions. Each tunnel is
31 and whether it is a control or data packet. When tunnels and sessions
37 operations when establishing tunnels and sessions. The procedure looks
89 An L2TP tunnel and all of its sessions are automatically closed when
217 Ethernet sessions only.
231 Ethernet sessions only.
254 Ethernet sessions only.
334 - Delete a tunnel and all of its sessions (if any)::
488 - Bridging L2TP sessions which have PPP pseudowire types (this is also called
490 channels of the two L2TP sessions to be bridged::
607 tunnels and sessions only. Its use is discouraged.
632 keeps a list of sessions in the tunnel. When a tunnel is first
646 tunnel and all of its sessions must be closed and destroyed. Since the
652 handler initiates the same tunnel close actions. All sessions are
669 Like tunnels, L2TP sessions are identified by a unique
675 stays extant while one or more sessions references it.
677 Sessions are kept in a per-net list. L2TPv2 sessions and L2TPv3
678 sessions are stored in separate lists. L2TPv2 sessions are keyed
680 session ID. L2TPv3 sessions are keyed by the 32-bit session ID, since
687 sessions, the list entry may link to multiple sessions with that
709 process of being closed. PPP sessions hold a ref on their associated
719 L2TP Ethernet sessions are created and destroyed by netlink request,
720 or are destroyed when the tunnel is destroyed. Unlike PPP sessions,
721 Ethernet sessions do not have an associated socket.