Package Details: networkmanager-l2tp 1.2.2-1

Git Clone URL: https://aur.archlinux.org/networkmanager-l2tp.git (read-only)
Package Base: networkmanager-l2tp
Description: L2TP support for NetworkManager
Upstream URL: https://github.com/nm-l2tp/NetworkManager-l2tp
Licenses: GPL2
Provides: networkmanager-l2tp
Submitter: bradpitcher
Maintainer: mlq
Last Packager: mlq
Votes: 38
Popularity: 2.147377
First Submitted: 2013-03-13 17:16
Last Updated: 2016-05-29 21:39

Latest Comments

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 :
https://github.com/nm-l2tp/network-manager-l2tp/issues
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.

For strongSwan, 'sbin/ipsec restart' is valid, so I suspect your original /sbin/ipsec error message was generated by openswan, not strongSwan.

I should probably add some code to NetworkManager-l2tp to explicitly test for strongSwan, so that it if openswan is used, it 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

darkhan commented on 2016-06-27 22:15

Edit: I do not know why but I replaced strongswan with libreswan and vpn started working.

I resolved the previous issue by installing strongswan, but now I am getting the following
Jun 28 04:13:03 leno NetworkManager[2184]: xl2tpd[2448]: Listening on IP address 0.0.0.0, port 1701
Jun 28 04:13:03 leno NetworkManager[2184]: xl2tpd[2448]: Connecting to host XXX.XXX.XXX.XXX, port 1701
Jun 28 04:13:03 leno NetworkManager[2184]: <info> [1467065583.7984] vpn-connection[0xc2a3c0,7beef323-6b39-4acf-9f49-6e489ebe0f89,"testcon-nm",0]: VPN plugin: state changed: starting (3)
Jun 28 04:13:13 leno NetworkManager[2184]: ** (nm-l2tp-service:2383): WARNING **: Looks like pppd didn't initialize our dbus module
Jun 28 04:13:13 leno NetworkManager[2184]: ** Message: Terminated xl2tpd daemon with PID 2448.
Jun 28 04:13:13 leno NetworkManager[2184]: xl2tpd[2448]: death_handler: Fatal signal 15 received
Jun 28 04:13:13 leno NetworkManager[2184]: xl2tpd[2448]: Connection 0 closed to 199.200.102.162, port 1701 (Server closing)
Jun 28 04:13:13 leno NetworkManager[2184]: <warn> [1467065593.8084] vpn-connection[0xc2a3c0,7beef323-6b39-4acf-9f49-6e489ebe0f89,"testcon-nm",0]: VPN plugin: failed: (7) (7)
Jun 28 04:13:13 leno NetworkManager[2184]: <warn> [1467065593.8084] vpn-connection[0xc2a3c0,7beef323-6b39-4acf-9f49-6e489ebe0f89,"testcon-nm",0]: VPN plugin: failed: connect-failed (1

darkhan commented on 2016-06-27 21:34

I am getting the following error when I try to connect:
Jun 28 03:32:21 leno NetworkManager[24452]: ** Message: starting ipsec
Jun 28 03:32:21 leno NetworkManager[24452]: /sbin/ipsec: unknown IPsec command `restart' (`ipsec --help' for list)

Does anyone know what might be the ussue?

dkosovic commented on 2016-06-19 09:40

@pmig sorry I didn't see your comment till recently.

I've just done a Arch Linux update and upgrade to the latest packages and installed the networkmanager-l2tp 1.2.2-1 package from this page and wasn't able to reproduce the issue.

The following error message you are seeing happens after a 10 second timeout while waiting for xlt2pd and pppd to complete the connection:

May 28 13:13:29 dev-xps15 NetworkManager[420]: ** (nm-l2tp-service:15797): WARNING **: Looks like pppd didn't initialize our dbus module

You could bump 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 */

For reporting general network-manager-l2tp bugs, it would be better report them here :
https://github.com/nm-l2tp/network-manager-l2tp/issues
I would also get an email notification

pmig commented on 2016-05-28 11:19

hi @dkosovic thanks

After make install I started the vpn conenction, but it still fails,

which of these warnings make sense?

http://pastebin.com/hgV6CvdG

dkosovic commented on 2016-05-16 07:15

I meant:

But with the network-manager-l2tp 1.0.0 package (and 1.0.2), you would need to downgrade to xl2tpd-1.3.6 if as 1.3.7 triggers a bug with pppd.

dkosovic commented on 2016-05-16 07:12

Which version of the package are you using? 1.2.0 never really worked. And what version of NetworkManager?

if you are using NetworkManager 1.2.x, I would recommend using the following:
https://github.com/nm-l2tp/network-manager-l2tp/archive/1.2.2/network-manager-l2tp-1.2.2.tar.gz

If you are using NetworkManager 1.0.x, I would recommend using the following:
https://github.com/nm-l2tp/network-manager-l2tp/archive/1.0.2/network-manager-l2tp-1.0.2.tar.gz

But with network-manager-1.0.2 (and with 1.0.0), you would need to downgrade to xl2tpd-1.3.6 if you have xl2tpd-1.3.7 installed.

If you have a NetworkManager 1.1.x developer release installed, upgrade to NetworkManager 1.2.x

pmig commented on 2016-05-15 12:36

I always receive an error during the connection intialization to an IPSec VPN:

May 15 14:32:22 dev-xps15 NetworkManager[15368]: <info> [1463315542.4158] vpn-connection[0x25d71e0,20e18803-6f86-43e8-be03-0ef748803e61,"VPN x",0]: Started the VPN service, PID 15953
May 15 14:32:27 dev-xps15 NetworkManager[15368]: <warn> [1463315547.9320] vpn-connection[0x25d71e0,20e18803-6f86-43e8-be03-0ef748803e61,"VPN x",0]: Timed out waiting for the service to start
May 15 14:32:27 dev-xps15 NetworkManager[15368]: (nm-exported-object.c:930):nm_exported_object_dispose: code should not be reached'


xl2tpd & ipsec are both running without errors:

May 15 14:28:55 dev-xps15 systemd[1]: Started Level 2 Tunnel Protocol Daemon (L2TP).
May 15 14:28:55 dev-xps15 xl2tpd[15118]: xl2tpd[15118]: setsockopt recvref[30]: Protocol not available
May 15 14:28:55 dev-xps15 xl2tpd[15118]: xl2tpd[15118]: Using l2tp kernel support.
May 15 14:28:55 dev-xps15 xl2tpd[15118]: xl2tpd[15118]: xl2tpd version xl2tpd-1.3.7 started on dev-xps15 PID:15118
May 15 14:28:55 dev-xps15 xl2tpd[15118]: xl2tpd[15118]: Written by Mark Spencer, Copyright (C) 1998, Adtran, Inc.
May 15 14:28:55 dev-xps15 xl2tpd[15118]: xl2tpd[15118]: Forked by Scott Balmos and David Stipp, (C) 2001
May 15 14:28:55 dev-xps15 xl2tpd[15118]: xl2tpd[15118]: Inherited by Jeff McAdams, (C) 2002
May 15 14:28:55 dev-xps15 xl2tpd[15118]: xl2tpd[15118]: Forked again by Xelerance (www.xelerance.com) (C) 2006-2016
May 15 14:28:55 dev-xps15 xl2tpd[15118]: xl2tpd[15118]: Listening on IP address 0.0.0.0, port 1701


Do you have some advice for me?

dkosovic commented on 2016-04-28 04:39

NetworkManager-l2tp 1.0.0 tag is for NetworkManager 1.0 based Linux distributions, and the code is on the nm-1-0 branch. I'm still maintaining it and plan to release newer 1.0.x releases. It's pretty stable.

NetworkManager-l2tp 1.2.0 is for NetworkManager 1.2 which hasn't been released yet, it's currently 1.1.93 (i.e. 1.2-RC1).

NetworkManager-l2tp 1.2.0 tag and pull request was for NetworkManager 1.2 based Fedora 24 pre-alpha release and from a GNOME VPN plugin maintainer. I've since tested it and regrettably found it has issues. I'm in the process of fixing the issues on the master branch and will release a version 1.2.1 hopefully in the next day or so.

Sorry I didn't see you comments till I went back to this web page. I wasn't familiar with Arch Linux dependencies, but what you suggested makes sense. I've since installed Arch Linux after getting a couple of bug reports.

All comments