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)::
484 tunnels and sessions only. Its use is discouraged.
509 keeps a list of sessions in the tunnel. When a tunnel is first
524 tunnel and all of its sessions must be closed and destroyed. Since the
530 handler initiates the same tunnel close actions. All sessions are
536 Sessions  section in Internal Implementation
552 Like tunnels, L2TP sessions are identified by a unique
557 Sessions hold a ref on their parent tunnel to ensure that the tunnel
558 stays extant while one or more sessions references it.
560 Sessions are kept in a per-tunnel list, indexed by session id. L2TPv3
561 sessions are also kept in a per-net list indexed by session id,
570 tunnels and does not add sessions of L2TPv3 UDP tunnels into the
594 process of being closed. Unlike tunnels, PPP sessions do not hold a
605 L2TP Ethernet sessions are created and destroyed by netlink request,
606 or are destroyed when the tunnel is destroyed. Unlike PPP sessions,
607 Ethernet sessions do not have an associated socket.