Package Details: networkmanager-l2tp 1.2.4-3

Git Clone URL: (read-only)
Package Base: networkmanager-l2tp
Description: L2TP support for NetworkManager
Upstream URL:
Licenses: GPL2
Provides: networkmanager-l2tp
Submitter: bradpitcher
Maintainer: mlq
Last Packager: mlq
Votes: 53
Popularity: 1.855733
First Submitted: 2013-03-13 17:16
Last Updated: 2017-01-18 21:39

Latest Comments

rvalue commented on 2017-04-30 11:37

I was able to build it only after I had installed nm-connection-editor (see this comment:

Probably nm-connection-editor should be added to dependencies, because it contains required by this package.

dkosovic commented on 2017-01-18 22:16

The dependencies for this AUR package have been updated.

dkosovic commented on 2017-01-18 01:31

@leemeng0x61 are you saying the latest code in GitHub repository lets you connect to the VPN server like it did with tapia?

But note, tapia would have been referring to networkmanager-l2tp 1.2.2.

networkmanager-l2tp 1.2.4 is the latest version. There have only been four commits in the GitHub repository since 1.2.4 :

Main issue with this package is that openswan isn't a dependency, but libreswan and xl2tpd are.

leemeng0x61 commented on 2017-01-18 01:13

The same with @tapia, failed connect to server

tapia commented on 2016-12-03 10:11

I can't establish a connection with this packages, but I do if I install the latest git version. Maybe this package should be updated.

dkosovic commented on 2016-11-28 14:24

Have a look at the following which seems to indicate issues with the dependencies being broken:

the new networkmanager-l2tp 1.2.4 dependencies should be more like networkmanager-pptp, but with libreswan and xl2tpd added and also pptpclient removed.

batyu commented on 2016-11-28 12:29

When probing install with yaourt:
configure: error: Package requirements (libnma >= 1.2.0) were not met: No package 'libnma' found

darkhan commented on 2016-07-02 08:00

@dkosovic, thanks!
I am currently busy, but will try to follow your steps to see if I can make this work with strongSwan and let you know.
As of now, it is working for me with libreSwan. And yes, you are right, the initial error message I had was when I had only openswan. I deleted it later.

dkosovic commented on 2016-06-30 07:07

@darkhan could you try bumping up the timeout by upping the following value in network-manager-l2tp/src/nm-l2tp-service.c :
#define NM_L2TP_WAIT_PPPD 10000 /* 10 seconds */
as the "Looks like pppd didn't initialize our dbus module" message happens after a 10 second timeout waiting for xl2tpd to connect.

I'll be happy to follow-up with help if you submit the issue here :
that way I get an email notification.

Regarding Libreswan, NetworkManager-l2tp does an initial runtime detection to determine if Libreswan is being used by scanning the output of /sbin/ipsec to see if it contains the string "Libreswan". If it doesn't, it then assumes strongSwan is to be used.

In the master branch on GitHub, I've added some code to NetworkManager-l2tp to also explicitly test for strongSwan, so that it if openswan is used, it now outputs an error message indicating only Libreswan and openSwan are supported.

For this package, the "openswan (optional)" dependency ought to be changed to "libreswan (optional)" and a mandatory dependency for xl2tpd added. Also as libgnome-keyring has been superseded by libsecret, that dependency could probably be changed as well.

boyi commented on 2016-06-30 06:34

Can't use openswan with it out of the box as it calls ipsec restart command --> unknown IPsec command `restart' (`ipsec --help' for list)

Got it working with libreswan.

During the first time, if ipsec is not starting, you need to enable and start it:
systemctl enable ipsec.service
systemctl start ipsec.service

If fail to reconnect after booting, might be due to ipsec is not starting. Try to reenable the service:
systemctl reenable ipsec.service

All comments