NetworkManager-pptp doesn't work after lastest update

English Network/Internet
1

Hi
I’m using pptp vpn connection to connect to my office. I’ve done this by creating a vpn connection in networkmanager-pptp. It used to work properly, but after recent update, it doesn’t.
I’ve updated system to all new packages that are found by “zypper update” command.To make sure that vpn server is working properly, I used other distribution to test it and it works.But on opensuse it fails to connect and pppd exited suddenly with **error code 16
**

This is the part of log since I clicked on pptp connection until it fails to connect.


May 03 00:49:08 suse-pc NetworkManager[2151]: <info> VPN plugin state changed: starting (3)
May 03 00:49:08 suse-pc NetworkManager[2151]: ** Message: pppd started with pid 17691
May 03 00:49:08 suse-pc NetworkManager[2151]: <info> VPN connection 'myOffice' (Connect) reply received.
May 03 00:49:08 suse-pc pppd[17691]: Plugin /usr/lib64/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
May 03 00:49:08 suse-pc NetworkManager[2151]: Plugin /usr/lib64/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
May 03 00:49:08 suse-pc NetworkManager[2151]: ** Message: nm-pptp-ppp-plugin: (plugin_init): initializing
May 03 00:49:08 suse-pc pppd[17691]: pppd 2.4.7 started by root, uid 0
May 03 00:49:08 suse-pc NetworkManager[2151]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection'
May 03 00:49:08 suse-pc pppd[17691]: Using interface ppp0
May 03 00:49:08 suse-pc pppd[17691]: Connect: ppp0 <--> /dev/pts/4
May 03 00:49:08 suse-pc NetworkManager[2151]: Using interface ppp0
May 03 00:49:08 suse-pc NetworkManager[2151]: Connect: ppp0 <--> /dev/pts/4
May 03 00:49:08 suse-pc NetworkManager[2151]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish'
May 03 00:49:08 suse-pc NetworkManager[2151]: <info> (ppp0): new Generic device (driver: 'unknown' ifindex: 12)
May 03 00:49:08 suse-pc NetworkManager[2151]: <info> (ppp0): exported as /org/freedesktop/NetworkManager/Devices/11
May 03 00:49:08 suse-pc pptp[17692]: nm-pptp-service-17649 log[main:pptp.c:314]: The synchronous pptp option is NOT activated
May 03 00:49:08 suse-pc pptp[17699]: nm-pptp-service-17649 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request'
May 03 00:49:08 suse-pc pptp[17699]: nm-pptp-service-17649 log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply
May 03 00:49:08 suse-pc pptp[17699]: nm-pptp-service-17649 log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established.
May 03 00:49:09 suse-pc pptp[17699]: nm-pptp-service-17649 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request'
May 03 00:49:09 suse-pc pptp[17699]: nm-pptp-service-17649 log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply.
May 03 00:49:09 suse-pc pptp[17699]: nm-pptp-service-17649 log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's call ID 11077).
May 03 00:49:31 suse-pc pptp[17699]: nm-pptp-service-17649 log[ctrlp_disp:pptp_ctrl.c:929]: Call disconnect notification received (call id 0)
May 03 00:49:31 suse-pc pptp[17699]: nm-pptp-service-17649 log[ctrlp_error:pptp_ctrl.c:199]: Result code is 1 'Lost Carrier'. Error code is 0, Cause code is 1
May 03 00:49:31 suse-pc pptp[17699]: nm-pptp-service-17649 log[call_callback:pptp_callmgr.c:79]: Closing connection (call state)
May 03 00:49:31 suse-pc pppd[17691]: Modem hangup
May 03 00:49:31 suse-pc pppd[17691]: Connection terminated.
May 03 00:49:31 suse-pc avahi-daemon[1967]: Withdrawing workstation service for ppp0.
May 03 00:49:31 suse-pc NetworkManager[2151]: Modem hangup
May 03 00:49:31 suse-pc NetworkManager[2151]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 11 / phase 'disconnect'
May 03 00:49:31 suse-pc NetworkManager[2151]: Connection terminated.
May 03 00:49:31 suse-pc NetworkManager[2151]: <warn> VPN plugin failed: connect-failed (1)
May 03 00:49:31 suse-pc NetworkManager[2151]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 1 / phase 'dead'
May 03 00:49:31 suse-pc pppd[17691]: Script /usr/sbin/pptp W.X.Y.Z --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-17649 finished (pid 17692), status = 0x0
May 03 00:49:31 suse-pc pppd[17691]: Exit.
May 03 00:49:31 suse-pc NetworkManager[2151]: <warn> VPN plugin failed: connect-failed (1)
May 03 00:49:31 suse-pc NetworkManager[2151]: Script /usr/sbin/pptp W.X.Y.Z --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-17649 finished (pid 17692), status = 0x0
May 03 00:49:31 suse-pc NetworkManager[2151]: ** Message: nm-pptp-ppp-plugin: (nm_exit_notify): cleaning up
May 03 00:49:31 suse-pc NetworkManager[2151]: <warn> VPN plugin failed: connect-failed (1)
May 03 00:49:31 suse-pc NetworkManager[2151]: <info> VPN plugin state changed: stopped (6)
May 03 00:49:31 suse-pc NetworkManager[2151]: <info> VPN plugin state change reason: unknown (0)
May 03 00:49:31 suse-pc NetworkManager[2151]: <warn> error disconnecting VPN: Could not process the request because no VPN connection was active.
May 03 00:49:31 suse-pc NetworkManager[2151]: ** (nm-pptp-service:17649): WARNING **: pppd exited with error code 16

NOTES :W.X.Y.Z is a fictional ip address due to privacy
openSuSE 13.2 x64
Please guide me to fix this issue.

2

Have you rebooted (or restarted the NetworkManager.service) since the updates were done? Can we see the NetworkManager packages you have installed?

rpm -qa|grep Network
3

Kernel version may be relevant here too.

4 

homelinux1:~ # rpm -qa | grep Network
NetworkManager-openvpn-0.9.10.0-2.1.4.x86_64
NetworkManager-gnome-0.9.10.0-2.2.1.x86_64
typelib-1_0-NetworkManager-1_0-0.9.10.0-3.8.2.x86_64
NetworkManager-vpnc-gnome-0.9.10.0-2.1.4.x86_64
NetworkManager-0.9.10.0-3.8.2.x86_64
NetworkManager-openconnect-gnome-0.9.10.0-2.1.4.x86_64
NetworkManager-vpnc-0.9.10.0-2.1.4.x86_64
NetworkManager-pptp-gnome-0.9.10.0-2.2.2.x86_64
NetworkManager-pptp-0.9.10.0-2.2.2.x86_64
NetworkManager-openvpn-gnome-0.9.10.0-2.1.4.x86_64
NetworkManager-devel-0.9.10.0-3.8.2.x86_64
NetworkManager-openconnect-0.9.10.0-2.1.4.x86_64
libNetworkManagerQt1-0.9.8.2-3.1.3.x86_64



homelinux1:~ # uname -a
Linux homelinux1 3.16.7-21-desktop #1 SMP PREEMPT Tue Apr 14 07:11:37 UTC 2015 (93c1539) x86_64 x86_64 x86_64 GNU/Linux

I also searched the web and I’ve found that some guys have the same problem,but on ArchLinux.

5

Okay, the package list looks consistent and kernel version is as expected

homelinux1:~ # uname -a
Linux homelinux1 3.16.7-21-desktop #1 SMP PREEMPT Tue Apr 14 07:11:37 UTC 2015 (93c1539) x86_64 x86_64 x86_64 GNU/Linux

I also searched the web and I’ve found that some guys have the same problem,but on ArchLinux.

I have seen problems reported that were related to using 3.18.x kernels, and ‘nf_conntrack_pptp’ module not being loaded, but this shouldn’t be impacting in your case. I share what I read anyway

https://blog.wedrop.it/fedora-vpn-problems.html
https://bugzilla.redhat.com/show_bug.cgi?id=1187328

Try deleting and re-creating your VPN connection again.

6

The issue has been solved with the following command :


modprobe nf_conntrack_pptp

Tnx

7

I’m surprised, since I thought it only affected those using 2.18.x kernels, but happy that this solution worked. Anyway, for now you could automate the loading of this module at boot by adding a .conf file in /etc/modules-load.d/ directory eg /etc/modules-load.d/pptp.conf using your favourite editor as root. As an example

sudo nano  /etc/modules-load.d/pptp.conf

# Load nf_conntrack_pptp module at boot
nf_conntrack_pptp

More information about loading modules at boot here:

http://www.freedesktop.org/software/systemd/man/modules-load.d.html