Package Details: networkmanager-l2tp 1.2.14-1

Git Clone URL: (read-only)
Package Base: networkmanager-l2tp
Description: L2TP support for NetworkManager
Upstream URL:
Licenses: GPL2
Submitter: bradpitcher
Maintainer: smfsh
Last Packager: smfsh
Votes: 88
Popularity: 1.70
First Submitted: 2013-03-13 17:16
Last Updated: 2019-10-16 16:45

Dependencies (9)

Required by (0)

Sources (1)

Pinned Comments

smfsh commented on 2018-11-03 21:05

If you receive an unknown public key error, please add it to your gpg keychain:

gpg --recv-keys 49A7787EF8D3C039

Latest Comments

1 2 3 4 5 6 ... Next › Last »

bezirg commented on 2019-08-15 09:35

Thank you @dkosovic ! Please use the suggestion of @dkosovic

eblau commented on 2019-03-27 00:37

@dkosovic thanks for the suggestion! That was the issue. Disabling PFS in my NetworkManager VPN connection settings with 1.2.12-2 allowed me to connect successfully again. I had looked through the connection settings but did not realize the significance of disabling PFS.

dkosovic commented on 2019-03-26 13:30

With NetworkManager-l2tp 1.2.12, PFS (Perfect Forward Secrecy) is no longer disabled (which is libreswan's default behavior).

If your VPN server doesn't use PFS, you will now need to click the new "Disable PFS" tick box in the IPsec settings to explicitly disable PFS .

I can confirm clicking "Disable PFS" tick box fixed the issue for another NetworkManager-l2tp 1.2.12 user.

If you are using strongswan, the "Disable PFS" tick box is greyed out as the pfs option is ignored by strongswan (as it automatically tries to use PFS anyway).

eblau commented on 2019-03-26 13:11

The update to 1.2.12-2 broke my VPN connection. I did some cursory debugging by running with the "--debug" option in the foreground but could not immediately figure it out. The connection seems to time out when launching the ipsec script now. Reverting to 1.2.10-4 fixes the issue for me.

Anyone else seeing similar issues?

bezirg commented on 2019-03-18 09:56

Thank you EarthMind. Your workarounds are correct.

EarthMind commented on 2019-03-17 20:45

The problem is not only the checksum mismatch but also the package name. The script is trying to cd to the network-manager-l2tp folder but there is no such folder. The extracted folder name is NetworkManager-l2tp-$pkgver

That needs to be fixed too

eblau commented on 2019-03-17 11:08

I'm getting checksum mismatches validating the md5sum:

==> Validating source files with md5sums...
    network-manager-l2tp-1.2.12.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build networkmanager-l2tp.

$ md5sum NetworkManager-l2tp-1.2.12.tar.gz 
e26824d4ae67ec75b7f19ae0fca4ea36  NetworkManager-l2tp-1.2.12.tar.gz

From the PKGBUILD:


Could you please check this and update the checksum if appropriate?

squalou commented on 2019-02-23 11:40

Why is this package flagged as out-of-date ? the "new" release available if a maintainance release for older branch of networkmanager (0.98 and 1.0.x) Maybe the dependencies should explicitely say networkmanager >=1.2 ?

dkosovic commented on 2019-02-08 15:08

In the past building with libnm-glib compatibility (NetworkManager 1.0) was enabled by default as there were lots of applications and desktop environments that were dependent on it, not any more.

Building without libnm-glib support removes the dependency on libnm-gtk.

Along with the package dependency changes (which would be similar to network-manager-pptp), the configure script will require the following argument : --without-libnm-glib

The next release of networkmanager-l2tp won't need --without-libnm-glib as it will be the default.

nstankovic commented on 2019-02-08 11:25

Having trouble to install, libnm-gtk doesn't exists anymore.

==> Building and installing package

==> Install or build missing dependencies for networkmanager-l2tp:

[sudo] password for :

error: target not found: libnm-gtk

==> Restart building networkmanager-l2tp ? [y/N]