DO NOT PROVIDE PRE-BUILT BINARIES OF THIS RELEASE UNTIL THE INTENDED LINUX DISTRIBUTION SHIPS WITH OPENSSL 3.0.0 OR LATER THAT IS COMPATIBLE WITH THE GPLv2 LICENSE. But the source code will build with OpenSSL 1.1.0 and later.
NetworkManager-l2tp is a VPN plugin for NetworkManager 1.8 and later which provides support for L2TP and L2TP/IPsec (i.e. L2TP over IPsec) connections.
For L2TP support, it uses xl2tpd ( https://www.xelerance.com/software/xl2tpd/ )
For IPsec support, it uses either of the following :
For user authentication it supports either:
- username/pasword credentials.
- TLS certificates.
For machine authentication is supports either:
- Pre-shared key (PSK).
- TLS certificates.
This VPN plugin auto detect the following TLS certificate and private key file formats by looking at the file contents and not the file extension :
- PKCS#12 certificates.
- X509 certificates (PEM or DER).
- PKCS#8 private keys (PEM or DER)
- traditional OpenSSL RSA, DSA and ECDSA private keys (PEM or DER).
For TLS user certificate support, the ppp package has to have the EAP-TLS patch for pppd applied to the ppp source code (which many Linux distributions already do) :
For details on pre-built packages, known issues and build dependencies, please visit the Wiki :
./autogen.sh ./configure # (see below) make
The default ./configure settings aren't reasonable and should be explicitly
overridden with ./configure arguments. In the configure examples below, you
may need to change the
--with-pppd-plugin-dir value to an appropriate
directory that exists.
Debian and Ubuntu (AMD64, i.e. x86-64)
./configure \ --disable-static --prefix=/usr \ --sysconfdir=/etc --libdir=/usr/lib/x86_64-linux-gnu \ --libexecdir=/usr/lib/NetworkManager \ --localstatedir=/var \ --with-pppd-plugin-dir=/usr/lib/pppd/2.4.7
Fedora and Red Hat Enterprise Linux (x86-64)
./configure \ --disable-static --prefix=/usr \ --sysconfdir=/etc --libdir=/usr/lib64 \ --localstatedir=/var \ --with-pppd-plugin-dir=/usr/lib64/pppd/2.4.7
./configure \ --disable-static --prefix=/usr \ --sysconfdir=/etc --libdir=/usr/lib64 \ --libexecdir=/usr/lib \ --localstatedir=/var \ --with-pppd-plugin-dir=/usr/lib64/pppd/2.4.7
VPN connection profile files
VPN connection profile files (along with other NetworkManager profile files)
are stored under
Run-time generated files
The following files located under
--runstatedir=/var/run were supplied to the configure script at build time.
where UUID is the NetworkManager UUID for the VPN connection.
If strongswan is being used, NetworkManager-l2tp will append the following line
/etc/ipsec.secrets at run-time if the line is missing:
Issue the following on the command line which will increase xl2tpd and pppd debugging, also the run-time generated config files will not be cleaned up after a VPN disconnection :
Debian and Ubuntu
sudo killall -TERM nm-l2tp-service sudo /usr/lib/NetworkManager/nm-l2tp-service --debug
Fedora and Red Hat Enterprise Linux
sudo killall -TERM nm-l2tp-service sudo /usr/libexec/nm-l2tp-service --debug
sudo killall -TERM nm-l2tp-service sudo /usr/lib/nm-l2tp-service --debug
then start your VPN connection and reproduce the problem.
NetworkManager and pppd logging goes to the Systemd journal which can be viewed by issuing the following which will show the logs since the last boot:
For non-Systemd based Linux distributions, view the appropriate system log
file which is most likely located under
Issue with not stopping system xl2tpd service
NetworkManager-l2tp starts its own instance of xl2tpd and if the system xl2tpd service is running, its own xl2tpd instance will not be able to use UDP port 1701, so will use an ephemeral port (i.e. random high port).
Although the use of an ephemeral port is considered acceptable in RFC3193, the L2TP/IPsec standard co-authored by Microsoft and Cisco, there are some L2TP/IPsec servers and/or firewalls that will have issues if an ephemeral port is used.
Stopping the system xl2tpd service should free UDP port 1701 and on systemd based Linux distributions, the xl2tpd service can be stopped with the following:
sudo systemctl stop xl2tpd
If stopping the xl2tpd service fixes your VPN connection issue, you can disable the xl2tpd service from starting at boot time with :
sudo systemctl disable xl2tpd
Issue with VPN servers only proposing IPsec IKEv1 weak legacy algorithms
There is a general consensus that the following legacy algorithms are now considered weak or broken in regards to security and should be phased out and replaced with stronger algorithms.
Encryption Algorithms :
Integrity Algorithms :
Diffie Hellman Groups :
Legacy algorithms that are considered weak or broken are regularly removed from the default set of allowed algorithms with newer releases of strongSwan and Libreswan. As of strongSwan 5.4.0 and Libreswan 3.20, the above algorithms (apart from SHA1 and MODP1536 for Libreswan which still includes them for backwards compatibility) have been or in some cases already been removed from the default set of allowed algorithms.
If you are not sure which IKEv1 algorithms your VPN server uses, you can query
the VPN server with the
ike-scan.sh script located in the IPsec IKEv1
algorithms section of the Wiki :
If the VPN server is only proposing weak or broken algorithms, it is recommended that it be reconfigured to propose stronger algorithms, e.g. AES, SHA2 and MODP2048.
If for some reason the VPN server cannot be reconfigured and you are not too
concerned about security, for a workaround, user specified phase 1 (ike) and
phase 2 (esp) algorithms can be specified in the IPsec Options dialog box in
Advanced section. See the following example and the IPsec IKEv1
algorithms section of the Wiki for more details :
Example workaround for 3DES, SHA1 and MODP1024 broken proposal
Unfortunately there are many L2TP/IPsec VPN servers and consumer routers still offering only the 3DES, SHA1 and MODP1024 broken proposal first introduced with Windows 2000 Server.
Windows Server 2019 offers the following proposals :
AES256-SHA1-ECP384 and AES128-SHA1-ECP256 strong proposals. strongSwan recommends not using SHA1 in its security recommendations documentation.
3DES-SHA1-MODP1024 broken proposal. Legacy Windows 2000 Server era proposal.
Pressing the "Legacy Proposals" button in the IPsec Options dialog box populates Phase 1 and 2 Algorithm text entry boxes with the following (note: it auto-detects if you are using strongswan or libreswan and populates appropriately):
- Phase1 Algorithms : aes256-sha1-ecp384,aes128-sha1-ecp256,3des-sha1-modp1024!
- Phase2 Algorithms : aes256-sha1,aes128-sha1,3des-sha1!
- Phase1 Algorithms : aes256-sha1-ecp_384,aes128-sha1-ecp_256,3des-sha1-modp1024
- Phase2 Algorithms : aes256-sha1,aes128-sha1,3des-sha1
As the proposals populated by the "Legacy Proposals" button includes the 3DES, SHA1 and MODP1024 broken proposal, it should work with L2TP/IPsec VPN servers and consumer routers that only offer that proposal. Alternatively, manually enter the following :
- Phase1 Algorithms : 3des-sha1-modp1024!
- Phase2 Algorithms : 3des-sha1!
- Phase1 Algorithms : 3des-sha1-modp1024
- Phase2 Algorithms : 3des-sha1
If you want to confirm if you are using libreswan or strongswan, issue the following on the command-line: