You're digging through your router's admin panel, or maybe resurrecting an old work VPN setup guide from around 2014, and there it is: L2TP/IPsec, sitting in a dropdown menu. It's built into practically every device that's ever shipped a VPN client. So is picking it fine, or are you about to make a mistake you won't notice until it's too late?
The short answer? If you have other choices, don't pick L2TP. The thing is, it doesn't encrypt your traffic. At all. On its own, it's just a tunnel, a delivery truck with no lock on the back doors. It's exactly what it was built to do in 1999, but times has changes, and so has the internet.
Let's get into what that actually means, why most of the companies that shipped this protocol have spent the last few years quietly walking away from it, and why it's still staring at you from that dropdown anyway.
What Is L2TP, Actually?
L2TP (Layer 2 Tunneling Protocol) is a tunneling protocol from 1999, standardized as RFC 2661, built jointly by Cisco and Microsoft as the successor to PPTP. Think of it as a merger: Microsoft brought PPTP to the table, Cisco brought its own tunnel format called L2F, and L2TP is what came out of that meeting.
In short, L2TP builds the pipe your data travels through, but it does nothing to keep that data private once it's inside. The thing is, a tunnel is not a lock. It's a delivery mechanism.
Because L2TP provides exactly zero encryption on its own, it never travels alone. It gets bolted to IPsec (so you get the combo L2TP/IPsec). There's also L2TPv3, a 2005 update that mostly lives inside ISP and carrier networks moving traffic between their own equipment these days, not on your laptop.
| Released | 1999, RFC 2661 |
|---|---|
| Encryption | None on its own; AES via IPsec |
| Ports | UDP 1701, plus UDP 500 and UDP 4500 for IPsec |
| Speed | Slow: double encapsulation |
| Status in 2026 | Disabled by default on new Windows Server RRAS setups, dropped by major VPN providers, not offered by Windscribe |
So how does a tunnel with no lock, and a lock with no tunnel, end up working together?
How L2TP/IPsec Actually Works
Think of L2TP/IPsec like shipping a delicate package inside an armored truck. First, IPsec steps in to negotiate the keys and build the bulletproof, encrypted highway using a process called Internet Key Exchange. Once that safe road is open, L2TP kicks in and packages your raw data inside basic envelopes called PPP frames, the same classic packaging format old-school dial-up used.
The catch is that every single piece of data gets wrapped twice: first by L2TP to build the tunnel, and then by IPsec to encrypt it. This double encapsulation adds heavy overhead to every packet, which is the main reason L2TP/IPsec has a reputation for being sluggish and clunky compared to modern protocols like WireGuard.
Once the package finally reaches the server, both layers get unwrapped, and your traffic is sent on its way to its final destination.
The Firewall Problem
L2TP/IPsec is a total nightmare for strict firewalls because it relies on three separate network ports (500, 4500, and 1701) open simultaneously. Any hotel, school, or corporate network admin can block your connection with a single mouse click.
Sitting behind a home router makes things even trickier, forcing you to rely on special "L2TP passthrough" settings or port 4500 tricks just to get your data past the router's built-in address translation system. Modern protocols avoid this mess entirely by slipping through standard web ports.
The Speed Tax
That double-wrapping process is a heavy performance tax on every single packet of data you send. Because your traffic has to be packaged by L2TP and then encrypted by IPsec, it runs roughly 20% to 30% slower than sleek, modern protocols like WireGuard. You end up paying that speed penalty every second you are online.
While the underlying AES encryption is rock-solid on paper, the clunky execution makes L2TP/IPsec a tough protocol to love today.
Is L2TP Actually Secure in 2026?
Properly configured L2TP/IPsec, running AES-256 (the same strong, widely trusted encryption cipher used across the security world), has no known practical break for an ordinary user. But the way it’s set up in the real world exposes some massive security risks.
The Pre-Shared Key Problem
Real-world consumer L2TP setups run on pre-shared keys, and the culture around handling those keys has been genuinely embarrassing for the industry. Providers and router manufacturers have published PSKs in plain text on their own public setup pages, for anyone to find.
On top of that, IKEv1, the key exchange method L2TP leans on, has a documented offline dictionary attack exposure, meaning an attacker who's grabbed a copy of the handshake can walk away and keep guessing keys against it on their own hardware, no need to stay connected to you.
It's tracked as CVE-2018-5389, the official ID security researchers assigned to the flaw. The lock itself isn't the problem. The key has been sitting under the doormat.
The Silent Failure Mode
L2TP's real danger is structural: it has no encryption of its own. If someone deploys bare L2TP, or configures a gateway (the server on the other end of the tunnel) or client badly enough that IPsec protection isn't actually being enforced, the tunnel itself does not save you.
With modern protocols, the secure handshake is the protocol. Fail the handshake, and there's no connection at all. With L2TP, the security is bolted on beside it, a separate layer that has to be correctly configured and enforced, which leaves more room for legacy misconfiguration.
The Legacy Crypto Rot
Older L2TP/IPsec deployments frequently negotiated 3DES (a deprecated legacy cipher with a small 64-bit block size that makes it risky for modern high-volume use), SHA-1 (an outdated way of checking data hasn't been tampered with), and weak Diffie-Hellman groups (the math behind agreeing on a secret key, where older versions no longer meet modern expectations).
All of that is now considered too weak to trust, the exact kind of weak default that shows up whenever researchers analyze what nation-state actors are actually capable of decrypting.
The Snowden-era leaks raised documented suspicion, not proven fact, that intelligence agencies specifically targeted configurations exactly like this one. Keep that in the back of your mind, because it's precisely the algorithm list Apple has been quietly narrowing.
The Quiet Retirement of L2TP: A Timeline
Protocols rarely die with a dramatic announcement. Instead, they experience a slow, coordinated sunset as security teams and operating system developers gradually move the goalposts.
L2TP didn't become obsolete overnight because its core cryptography failed. It fell out of favor because maintaining its fragile, multi-layered architecture became an unnecessary liability in a world with faster, simpler options.
2018: VPN Providers Go First
VPN companies started cutting L2TP loose years before the operating system vendors caught up. NordVPN discontinued L2TP/IPsec and PPTP server support on December 1, 2018, and CyberGhost dropped both protocols around the same era.
The math for commercial VPN providers was simple: maintaining legacy infrastructure for a protocol that requires three separate open ports and generates constant firewall troubleshooting tickets made no operational sense. More importantly, offering a protocol with known pre-shared key vulnerabilities and a silent failure mode compromised user safety.
2024: Microsoft, L2TP's Own Co-Creator, Pulls the Plug
Microsoft helped build L2TP in 1999. Fast forward a quarter-century, and they are actively burying it. Beginning with Windows Server 2025, new Routing and Remote Access Service (RRAS) setups don't accept PPTP or L2TP VPN connections by default. While administrators can technically still toggle them back on for legacy compatibility, Microsoft explicitly points administrators toward SSTP and IKEv2 instead.
This change is part of a broader, industry-wide push toward "secure by default" configurations. By disabling L2TP out of the box, Microsoft prevents junior sysadmins from deploying inherently risky, pre-shared key topologies that are vulnerable to offline dictionary attacks. When the company that wrote the protocol decides it is too much of a liability to leave running by default, the debate is officially over.
Android: A Messier Story Than It Looks
Google's own Android Enterprise documentation still lists a built-in VPN client that supports PPTP, L2TP/IPsec, and IPsec, so it would be wrong to say Android formally killed L2TP the way Microsoft killed it server-side. Nobody at Google ever made that announcement.
What actually happened is messier, and arguably more frustrating if you're the one trying to use it: on many newer Android devices, legacy L2TP/IPsec setup is no longer something users can count on finding in the native VPN settings. Support is inconsistent enough across manufacturers and OS versions that treating it as a modern default is a mistake.
2025: Apple Tightens the Bolts
Starting with iOS 26 and macOS 26 Tahoe, both released in September 2025, Apple's enterprise notes say DES, 3DES, SHA-1 variants, and Diffie-Hellman groups below Group 14 are no longer supported for IKEv2 VPNs.
That doesn’t prove Apple killed L2TP/IPsec, and Apple still documents L2TP/IPsec support as a supported VPN type, but it does show Apple tightening support around the same family of older IPsec-era crypto that many legacy gateways relied on.
Any old L2TP/IPsec gateway still depending on weak legacy algorithms is therefore more likely to run into compatibility trouble as Apple keeps tightening VPN crypto requirements. The tunnel doesn’t stop existing. The safe configuration window just keeps getting narrower.
Why Is L2TP Still Sitting in Your Settings Menu?
If L2TP is such a relic, why haven't technology companies scrubbed it from existence? There are three honest reasons for its survival, and none of them involve a conspiracy.
ISP Plumbing (L2TPv3)
L2TP didn't die; it just moved into the walls. As mentioned earlier, a variant called L2TPv3 lives deep inside carrier networks. ISPs frequently use it to tunnel wholesale broadband traffic from your local neighborhood exchange back to the core network.
In this environment, encryption doesn't matter because the data is traveling over a closed, physically secure fiber or copper link owned by the telecom company. It’s incredibly efficient at moving data packets between routers. It just shouldn't be used over public café Wi-Fi.
The Installed Base
Enterprise hardware has a massive lifecycle. Millions of mid-range routers, Network Attached Storage (NAS) boxes (like older Synology or QNAP units), and small office gateways shipped with L2TP as their primary out-of-the-box VPN solution. Businesses don't throw away a $500 router that works perfectly fine just because security blogs say the protocol is old. Until that hardware physically dies and is replaced, L2TP remains alive on life support.
Operating System Inertia
Microsoft, Apple, and Google keep L2TP clients bundled into their operating systems because ripping a legacy protocol out entirely creates a massive support nightmare. If an OS update instantly breaks a legacy VPN connection for thousands of remote corporate workers, the resulting influx of angry IT tickets is a headache no software vendor wants to deal with.
So, pretending that L2TP, as clunky and ancient as it is, has zero legitimate use anywhere would be its own kind of dishonesty.
If you're stuck connecting to a legacy corporate gateway that genuinely only speaks L2TP/IPsec, using it beats using nothing. Insist on a strong pre-shared key or certificate-based authentication (proving your identity with an installed digital certificate instead of a shared password), not one copy-pasted out of a PDF from 2011, and treat the whole thing as a bridge to get you connected, not a destination you're choosing on purpose.
So, What Protocols Should You Use Instead of L2TP?
If you are setting up a new VPN or updating an old one, you don't have to settle for 1999-era compromises. L2TP's three fundamental design flaws each have a direct, modern replacement.
If you want speed: Use WireGuard.
L2TP suffers from a "speed tax" caused by double encapsulation, wrapping your data in both L2TP and IPsec layers. WireGuard strips all that legacy bloat away. It operates inside the Linux kernel space using modern, streamlined cryptography, running faster than L2TP/IPsec while consuming significantly less battery on mobile devices.
If you want corporate-grade security: Use IKEv2.
If your IT department loves IPsec architecture, you don't have to throw the baby out with the bathwater. IKEv2 uses the same robust IPsec encryption as L2TP, but swaps out the vulnerable IKEv1 key exchange for IKEv2. It fixes the pre-shared key vulnerability, handles network changes seamlessly (like walking out of your house and dropping Wi-Fi for cellular data), and avoids the performance penalty of double encapsulation.
If you need to bypass firewalls: Use OpenVPN (TCP Port 443).
L2TP/IPsec requires fixed, predictable ports (UDP 1701, 500, and 4500) that are incredibly easy for network admins or restrictive firewalls to block.
OpenVPN can be configured to run over TCP port 443, the exact same port used by all standard HTTPS web traffic. To a firewall, your VPN traffic looks identical to someone securely checking their bank account, making it virtually impossible to block without shutting down the entire local internet connection.
Frequently Asked Questions About L2TP
What is L2TP used for?
L2TP (Layer 2 Tunneling Protocol) creates a secure pathway or "tunnel" for your data to travel across the internet. Because L2TP provides zero encryption on its own, it's almost always paired with IPsec to build corporate VPNs and remote access connections.
Should L2TP be enabled?
No, you should leave it disabled unless you're maintaining legacy network hardware that supports nothing else. Modern protocols like WireGuard and IKEv2 are faster, far easier on your battery, and significantly simpler to maintain securely.
Is L2TP the same thing as IPsec?
No, they're entirely separate networking technologies that are famously combined as L2TP/IPsec. L2TP acts as the courier by building the virtual tunnel and managing how data packets are formatted, but it offers absolutely zero privacy on its own. IPsec acts as the armored lockbox, handling the heavy cryptographic lifting by verifying identities and encrypting the payload. While L2TP requires IPsec to be secure, IPsec doesn't need L2TP to function and serves as the foundation for superior modern protocols like IKEv2.
Is L2TP faster than OpenVPN?
In an isolated laboratory test, "raw" L2TP without encryption can technically edge out OpenVPN, but this is a useless real-world metric since unencrypted L2TP shouldn't be used. Once you bolt on IPsec protection, the combination suffers from a structural "speed tax" known as double encapsulation, where every packet is wrapped twice. This overhead makes L2TP/IPsec roughly 20% to 30% slower than OpenVPN or WireGuard. Modern alternatives like WireGuard operate efficiently within the operating system's kernel space, easily outrunning both options.
Does Windscribe support L2TP?
No, we deliberately removed support for both L2TP and PPTP because continuing to offer them in 2026 creates a false sense of security. The protocol relies on poorly handled pre-shared keys that are often exposed in plain text and uses an aging key exchange vulnerable to offline dictionary attacks. We believe shipping a protocol that users shouldn't trust is just security theater. Instead, our lineup features modern, reliable alternatives like WireGuard, IKEv2, OpenVPN, Stealth, and WStunnel.
What are the disadvantages of L2TP?
Its biggest flaw is double encapsulation: L2TP wraps your data in a tunnel, and then IPsec wraps it again to encrypt it, creating massive speed overhead. It also drags down battery life, is notoriously difficult to configure, and struggles with firewalls.
Can L2TP be blocked?
Extremely easily. L2TP/IPsec relies on fixed, unchangeable network ports (UDP 500, 4500, and 1701). Restrictive network administrators at hotels, schools, or offices can shut down your entire connection simply by closing one of those specific doors.
Is L2TP VPN safe?
It’s "safe-ish," but with heavy asterisks. While the IPsec encryption layer is cryptographically strong, consumer L2TP setups usually rely on weak Pre-Shared Keys (PSKs) or prone-to-error manual configurations that make it far easier to compromise than modern alternatives.
Is L2TP obsolete?
Yes, it is essentially a dead man walking. Major tech vendors like Microsoft have officially deprecated L2TP/IPsec in server environments, and reputable consumer VPNs are purging it from their apps in favor of WireGuard.
