Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Layer 2 Tunneling Protocol
open-in-new
<h2 id="history">History</h2> <p>Published in August 1999 as proposed standard RFC 2661, L2TP has its origins primarily in two older tunneling protocols for point-to-point communication: <a href="/facts/Cisco_Systems%2c_Inc./ocDgQt6T">Cisco</a>'s <a href="/facts/Layer_2_Forwarding_Protocol/ftUo82mI">Layer 2 Forwarding Protocol</a> (L2F) and <a href="/facts/Microsoft/nGIDDXdx">Microsoft</a>'s<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> <a href="/facts/Point-to-Point_Tunneling_Protocol/jYb3uG0Y">Point-to-Point Tunneling Protocol</a> (PPTP). A new version of this protocol, <a href="/facts/L2TPv3/c2nCggsH">L2TPv3</a>, appeared as proposed standard RFC 3931 in 2005. L2TPv3 provides additional security features, improved encapsulation, and the ability to carry data links other than simply <a href="/facts/Point-to-Point_Protocol/XLaU6D71">Point-to-Point Protocol</a> (PPP) over an <a href="/facts/IP_network/KNkxtSpw">IP network</a> (for example: <a href="/facts/Frame_Relay/bFdv0qIP">Frame Relay</a>, <a href="/facts/Ethernet/nMfhU8tU">Ethernet</a>, <a href="/facts/Asynchronous_Transfer_Mode/SzA8ewFL">ATM</a>, etc.). </p> <h2 id="description">Description</h2> <p>The entire L2TP packet, including payload and L2TP header, is sent within a <a href="/facts/User_Datagram_Protocol/dxLU0D6q">User Datagram Protocol</a> (UDP) datagram. A virtue of transmission over UDP (rather than TCP) is that it avoids the <a href="/facts/TCP_meltdown_problem/jKaT1Czc">TCP meltdown problem</a>.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a><a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> It is common to carry PPP sessions within an L2TP tunnel. L2TP does not provide confidentiality or strong authentication by itself. <a href="/facts/IPsec/01MwcET1">IPsec</a> is often used to secure L2TP packets by providing confidentiality, authentication and integrity. The combination of these two protocols is generally known as L2TP/IPsec (discussed below). </p><p>The two endpoints of an L2TP tunnel are called the L2TP access concentrator (LAC) and the L2TP network server (LNS). The LNS waits for new tunnels. Once a tunnel is established, the network traffic between the peers is bidirectional. To be useful for networking, higher-level protocols are then run through the L2TP tunnel. To facilitate this, an L2TP <i>session</i> is established within the tunnel for each higher-level protocol such as PPP. Either the LAC or LNS may initiate sessions. The traffic for each session is isolated by L2TP, so it is possible to set up multiple virtual networks across a single tunnel. </p><p>The packets exchanged within an L2TP tunnel are categorized as either <i>control packets</i> or <i>data packets</i>. L2TP provides reliability features for the control packets, but no reliability for data packets. Reliability, if desired, must be provided by the nested protocols running within each session of the L2TP tunnel. </p><p>L2TP allows the creation of a virtual private dialup network (VPDN)<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> to connect a remote client to its corporate network by using a shared infrastructure, which could be the Internet or a service provider's network. </p> <h2 id="tunneling-models">Tunneling models</h2> <p>An L2TP tunnel can extend across an entire PPP session or only across one segment of a two-segment session. This can be represented by four different tunneling models, namely: </p> <ul><li>voluntary tunnel</li> <li>compulsory tunnel — incoming call</li> <li>compulsory tunnel — remote dial</li> <li>L2TP <a href="/facts/Multi-hop_routing/UbbjE9ku">multihop</a> connection<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a></li></ul> <h2 id="l2tp-packet-structure">L2TP packet structure</h2> <p>An L2TP packet consists of : </p> <table><tbody><tr><th>Bits 0–15</th><th>Bits 16–31</th></tr><tr><td>Flags and Version Info</td><td>Length (opt)</td></tr><tr><td>Tunnel ID</td><td>Session ID</td></tr><tr><td>Ns (opt)</td><td>Nr (opt)</td></tr><tr><td>Offset Size (opt)</td><td>Offset Pad (opt)......</td></tr><tr><td colspan="2">Payload data</td></tr></tbody></table> <p>Field meanings: </p> Flags and version control flags indicating data/control packet and presence of length, sequence, and offset fields. Length (optional) Total length of the message in bytes, present only when length flag is set. Tunnel ID Indicates the identifier for the control connection. Session ID Indicates the identifier for a session within a tunnel. Ns (optional) sequence number for this data or control message, beginning at zero and incrementing by one (modulo 216) for each message sent. Present only when sequence flag set. Nr (optional) sequence number for expected message to be received. Nr is set to the Ns of the last in-order message received plus one (modulo 216). In data messages, Nr is reserved and, if present (as indicated by the S bit), MUST be ignored upon receipt.. Offset Size (optional) Specifies where payload data is located past the L2TP header. If the offset field is present, the L2TP header ends after the last byte of the offset padding. This field exists if the offset flag is set. Offset Pad (optional) Variable length, as specified by the offset size. Contents of this field are undefined. Payload data Variable length (Max payload size = Max size of UDP packet − size of L2TP header) <h2 id="l2tp-packet-exchange">L2TP packet exchange</h2> <p>At the time of setup of L2TP connection, many control packets are exchanged between server and client to establish tunnel and session for each direction. One peer requests the other peer to assign a specific tunnel and session id through these control packets. Then using this tunnel and session id, data packets are exchanged with the compressed PPP frames as payload. </p><p>The list of L2TP Control messages exchanged between LAC and LNS, for handshaking before establishing a tunnel and session in voluntary tunneling method are </p> <h2 id="l2tpipsec">L2TP/IPsec</h2> <p>Because of the lack of confidentiality inherent in the L2TP, it is often implemented along with <a href="/facts/IPsec/01MwcET1">IPsec</a>. This is referred to as L2TP/IPsec, and is standardized in <a href="/facts/IETF/tIcCsFhX">IETF</a> RFC 3193. The process of setting up an L2TP/IPsec VPN is as follows: </p> <ol><li>Negotiation of IPsec <a href="/facts/Security_association/aMTXVMsU">security association</a> (SA), typically through <i><a href="/facts/Internet_key_exchange/QBvx8mgk">Internet key exchange</a></i> (IKE). This is carried out over UDP port 500, and commonly uses either a shared password (so-called "<a href="/facts/Pre-shared_key/1mgbgR1X">pre-shared keys</a>"), public keys, or <a href="/facts/X.509/rs0JuYDd">X.509</a> certificates on both ends, although other keying methods exist.</li> <li>Establishment of <a href="/facts/IPsec/01MwcET1">Encapsulating Security Payload</a> (ESP) communication in transport mode. The IP protocol number for ESP is 50 (compare TCP's 6 and UDP's 17). At this point, a secure channel has been established, but no tunneling is taking place.</li> <li>Negotiation and establishment of L2TP tunnel between the SA endpoints. The actual negotiation of parameters takes place over the SA's secure channel, within the IPsec encryption. L2TP uses UDP port 1701.</li></ol> <p>When the process is complete, L2TP packets between the endpoints are encapsulated by IPsec. Since the L2TP packet itself is wrapped and hidden within the IPsec packet, the original source and destination IP address is encrypted within the packet. Also, it is not necessary to open UDP port 1701 on firewalls between the endpoints, since the inner packets are not acted upon until after IPsec data has been decrypted and stripped, which only takes place at the endpoints. </p><p>A potential point of confusion in L2TP/IPsec is the use of the terms tunnel and secure channel. The term tunnel-mode refers to a channel which allows untouched packets of one network to be transported over another network. In the case of L2TP/PPP, it allows L2TP/PPP packets to be transported over IP. A secure channel refers to a connection within which the confidentiality of all data is guaranteed. In L2TP/IPsec, first IPsec provides a secure channel, then L2TP provides a tunnel. IPsec also specifies a tunnel protocol: this is not used when a L2TP tunnel is used. </p> <h2 id="windows-implementation">Windows implementation</h2> <p>Windows has had native support (configurable in control panel) for L2TP since <a href="/facts/Windows_2000/amJIt9gz">Windows 2000</a>. <a href="/facts/Windows_Vista/IASEUCTB">Windows Vista</a> added 2 alternative tools, an <a href="/facts/Microsoft_Management_Console/SkY3jHFG">MMC snap-in</a> called "Windows Firewall with Advanced Security" (WFwAS) and the "<a href="/facts/Netsh/UwWf9lbj">netsh</a> advfirewall" command-line tool. One limitation with both of the WFwAS and netsh commands is that servers must be specified by IP address. <a href="/facts/Windows_10/be9IHehJ">Windows 10</a> added the "<a href="https://docs.microsoft.com/en-us/powershell/module/vpnclient/add-vpnconnection?view=win10-ps">Add-VpnConnection</a>" and "<a href="https://docs.microsoft.com/en-us/powershell/module/vpnclient/set-vpnconnectionipsecconfiguration?view=win10-ps">Set-VpnConnectionIPsecConfiguration</a>" <a href="/facts/PowerShell/G1d10lwn">PowerShell</a> commands. A registry key must be created on the client and server if the server is behind a NAT-T device. <a href="https://support.microsoft.com/en-us/help/926179/how-to-configure-an-l2tp-ipsec-server-behind-a-nat-t-device-in-windows">[1]</a> </p> <h2 id="l2tp-in-isps-networks">L2TP in ISPs' networks</h2> <p>L2TP is often used by ISPs when internet service over for example <a href="/facts/ADSL/Y5wsglVy">ADSL</a> or cable is being <i>resold</i>. From the end user, packets travel over a wholesale network service provider's network to a server called a Broadband Remote Access Server (<a href="/facts/BRAS/WxvAQWL4">BRAS</a>), a protocol converter and router combined. On legacy networks the path from end user customer premises' equipment to the BRAS may be over an <a href="/facts/Asynchronous_Transfer_Mode/SzA8ewFL">ATM</a> network. From there on, over an IP network, an L2TP tunnel runs from the BRAS (acting as LAC) to an LNS which is an edge router at the boundary of the ultimate destination ISP's IP network.<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a> </p> <h2 id="rfc-references">RFC references</h2> <ul><li>RFC <a href="https://www.rfc-editor.org/rfc/rfc2341">2341</a> <i>Cisco Layer Two Forwarding (Protocol) "L2F"</i> (a predecessor to L2TP)</li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc2637">2637</a> <i>Point-to-Point Tunneling Protocol (PPTP)</i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc2661">2661</a> <i>Layer Two Tunneling Protocol "L2TP"</i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc2809">2809</a> <i>Implementation of L2TP Compulsory Tunneling via RADIUS</i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc2888">2888</a> <i>Secure Remote Access with L2TP</i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc3070">3070</a> <i>Layer Two Tunneling Protocol (L2TP) over Frame Relay</i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc3145">3145</a> <i>L2TP Disconnect Cause Information</i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc3193">3193</a> <i>Securing L2TP using <a href="/facts/IPsec/01MwcET1">IPsec</a></i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc3301">3301</a> <i>Layer Two Tunneling Protocol (L2TP): ATM access network</i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc3308">3308</a> <i>Layer Two Tunneling Protocol (L2TP) Differentiated Services</i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc3355">3355</a> <i>Layer Two Tunneling Protocol (L2TP) Over ATM Adaptation Layer 5 (AAL5)</i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc3371">3371</a> <i>Layer Two Tunneling Protocol "L2TP" Management Information Base</i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc3437">3437</a> <i>Layer Two Tunneling Protocol Extensions for PPP Link Control Protocol Negotiation</i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc3438">3438</a> <i>Layer Two Tunneling Protocol (L2TP) Internet Assigned Numbers: Internet Assigned Numbers Authority (IANA) Considerations Update</i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc3573">3573</a> <i>Signaling of Modem-On-Hold status in Layer 2 Tunneling Protocol (L2TP)</i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc3817">3817</a> <i>Layer 2 Tunneling Protocol (L2TP) Active Discovery Relay for PPP over Ethernet (PPPoE)</i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc3931">3931</a> <i>Layer Two Tunneling Protocol - Version 3 (<a href="/facts/L2TPv3/c2nCggsH">L2TPv3</a>)</i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc4045">4045</a> <i>Extensions to Support Efficient Carrying of Multicast Traffic in Layer-2 Tunneling Protocol (L2TP)</i></li> <li>RFC <a href="https://www.rfc-editor.org/rfc/rfc4951">4951</a> <i>Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP) "failover"</i></li></ul> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/IPsec/01MwcET1">IPsec</a></li> <li><a href="/facts/Layer_2_Forwarding_Protocol/ftUo82mI">Layer 2 Forwarding Protocol</a></li> <li><a href="/facts/Point-to-Point_Tunneling_Protocol/jYb3uG0Y">Point-to-Point Tunneling Protocol</a></li> <li><a href="/facts/Point-to-Point_Protocol/XLaU6D71">Point-to-Point Protocol</a></li> <li><a href="/facts/Virtual_Extensible_LAN/X7RmKePU">Virtual Extensible LAN</a></li></ul> <h2 id="external-links">External links</h2> <h3>Implementations</h3> <ul><li>Cisco: <a href="https://web.archive.org/web/20090127060833/http://cisco.com/en/US/docs/ios/12_0t/12_0t1/feature/guide/l2tpT.html">Cisco L2TP documentation</a>, also read <a href="http://www.cisco.com/warp/public/cc/pd/iosw/tech/l2pro_tc.htm">Technology brief from Cisco</a></li> <li>Open source and Linux: <a href="http://www.xelerance.com/software/xl2tpd/">xl2tpd</a>, <a href="http://sourceforge.net/projects/rp-l2tp/">Linux RP-L2TP</a>, <a href="http://sourceforge.net/projects/openl2tp/">OpenL2TP</a>, <a href="http://l2tpns.sourceforge.net/">l2tpns</a>, <a href="http://sourceforge.net/projects/l2tpd/">l2tpd</a> (inactive), <a href="http://www.zeroshell.net/eng/vpndetails/">Linux L2TP/IPsec server</a>, <a href="http://mpd.sourceforge.net/">FreeBSD multi-link PPP daemon</a>, <a href="http://bxr.su/OpenBSD/usr.sbin/npppd/">OpenBSD npppd(8)</a>, <a href="http://accel-ppp.sourceforge.net/">ACCEL-PPP - PPTP/L2TP/PPPoE server for Linux</a></li> <li>Microsoft: built-in client included with Windows 2000 and higher; <a href="http://www.microsoft.com/technet/prodtechnol/windows2000serv/support/vpnclientag.mspx">Microsoft L2TP/IPsec VPN Client</a> for Windows 98/Windows Me/Windows NT 4.0</li> <li>Apple: built-in client included with Mac OS X 10.3 and higher.</li> <li><a href="http://www.cisco.com/en/US/tech/tk801/tk703/tsd_technology_support_protocol_home.html">VPDN on Cisco.com</a></li></ul> <h3>Other</h3> <ul><li><a href="https://www.iana.org/assignments/l2tp-parameters">IANA assigned numbers for L2TP</a></li> <li><a href="https://web.archive.org/web/20041207084942/http://www.ietf.org/html.charters/l2tpext-charter.html">L2TP Extensions Working Group (l2tpext)</a> - <i>(where future standardization work is being coordinated)</i></li> <li><a href="http://www.jacco2.dds.nl/networking/linux-l2tp.html">Using Linux as an L2TP/IPsec VPN client</a></li> <li><a href="http://undeadly.org/cgi?action=article&sid=20120427125048&mode=expanded&count=3">L2TP/IPSec with OpenBSD and npppd</a></li> <li><a href="https://www.ivpn.net/pptp-vs-l2tp-vs-openvpn">Comparison of L2TP, PPTP and OpenVPN</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>IETF (1999), RFC 2661, Layer Two Tunneling Protocol "L2TP" <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>"Point-to-Point Tunneling Protocol (PPTP)". TheNetworkEncyclopedia.com. 2013. Retrieved 2014-07-28. Point-to-Point Tunneling Protocol (PPTP) [:] A data-link layer protocol for wide area networks (WANs) based on the Point-to-Point Protocol (PPP) and developed by Microsoft that enables network traffic to be encapsulated and routed over an unsecured public network such as the Internet.[permanent dead link] <a href="http://www.thenetworkencyclopedia.com/entry/point-to-point-tunnelling-protocol-pptp/" target="_blank">http://www.thenetworkencyclopedia.com/entry/point-to-point-tunnelling-protocol-pptp/</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Titz, Olaf (2001-04-23). "Why TCP Over TCP Is A Bad Idea". Archived from the original on 2015-09-01. Retrieved 2015-10-17. <a href="http://sites.inka.de/bigred/devel/tcp-tcp.html" target="_blank">http://sites.inka.de/bigred/devel/tcp-tcp.html</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>Honda, Osamu; Ohsaki, Hiroyuki; Imase, Makoto; Ishizuka, Mika; Murayama, Junichi (October 2005). "Understanding TCP over TCP: effects of TCP tunneling on end-to-end throughput and latency". In Atiquzzaman, Mohammed; Balandin, Sergey I (eds.). Performance, Quality of Service, and Control of Next-Generation Communication and Sensor Networks III. Vol. 6011. Bibcode:2005SPIE.6011..138H. CiteSeerX 10.1.1.78.5815. doi:10.1117/12.630496. S2CID 8945952. <a href="/wiki/Bibcode_(identifier)" target="_blank">/wiki/Bibcode_(identifier)</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>"Cisco Support: Understanding VPDN – Updated Jan 29, 2008". Archived from the original on December 13, 2013. Retrieved December 5, 2013. <a href="http://www.cisco.com/en/US/tech/tk801/tk703/technologies_tech_note09186a0080094586.shtml" target="_blank">http://www.cisco.com/en/US/tech/tk801/tk703/technologies_tech_note09186a0080094586.shtml</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>IBM Knowledge Center: L2TP multi-hop connection <a href="http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=%2Frzaiy%2Frzaiymultihop.htm" target="_blank">http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=%2Frzaiy%2Frzaiymultihop.htm</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>See example of reseller ISPs using L2TP. <a href="http://www.kitz.co.uk/adsl/equip2.htm" target="_blank">http://www.kitz.co.uk/adsl/equip2.htm</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> </ol>