bionic: VPN not working at all

[Thomas]

VPN is completely busted on bionic-desktop (4/21/2018). In 17.10 my VPN was still working, "only" had to do a `killall nm-applet; nohup nm-applet &` to get the password prompt to show up. In bionic, at least that portion now works without work-around. However, I can't establish my VPN to my workplace at all.

My VPN configuration in /etc/NetworkManager/system-connections/Test seems rather basic:

[connection]
id=Test
uuid=ae916f15-2e8d-46b0-92d3-c2dece212c40
type=vpn
autoconnect=false
permissions=user:thomas:;

[vpn]
domain=XXXXXX.XXX
gateway=vpn.XXXXXX.XXX
password-flags=2
refuse-chap=yes
refuse-eap=yes
refuse-pap=yes
require-mppe=yes
user=YYYYYYYYY
service-type=org.freedesktop.NetworkManager.pptp

[ipv4]
dns=10.11.11.11;
dns-search=
method=auto
never-default=true
route1=10.11.0.0/16,10.11.31.31

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=ignore

Here's the logs from syslog:

Apr 22 10:29:18 thomas-bionic NetworkManager[507]: <info> [1524414558.0300] audit: op="connection-activate" uuid="ae916f15-2e8d-46b0-92d3-c2dece212c40" name="Test" pid=1141 uid=1000 result="success"
Apr 22 10:29:18 thomas-bionic gnome-shell[781]: JS ERROR: TypeError: item is undefined#012setActiveConnections/<@resource:///org/gnome/shell/ui/status/network.js:1518:17#012setActiveConnections@resource:///org/gnome/shell/ui/status/network.js:1515:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
Apr 22 10:29:18 thomas-bionic NetworkManager[507]: <info> [1524414558.0445] vpn-connection[0x555885252640,ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test",0]: Started the VPN service, PID 2601
Apr 22 10:29:18 thomas-bionic NetworkManager[507]: <info> [1524414558.0631] vpn-connection[0x555885252640,ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test",0]: Saw the service appear; activating connection
Apr 22 10:29:21 thomas-bionic NetworkManager[507]: <info> [1524414561.2896] settings-connection[0x55588511f440,ae916f15-2e8d-46b0-92d3-c2dece212c40]: write: successfully updated (keyfile: update /etc/NetworkManager/system-connections/Test (ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test")), connection was modified in the process
Apr 22 10:29:21 thomas-bionic NetworkManager[507]: <info> [1524414561.3008] vpn-connection[0x555885252640,ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test",0]: VPN connection: (ConnectInteractive) reply received
Apr 22 10:29:21 thomas-bionic NetworkManager[507]: <info> [1524414561.3095] vpn-connection[0x555885252640,ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test",0]: VPN plugin: state changed: starting (3)
Apr 22 10:29:21 thomas-bionic pppd[2613]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Apr 22 10:29:21 thomas-bionic NetworkManager[507]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Apr 22 10:29:21 thomas-bionic pppd[2613]: pppd 2.4.7 started by root, uid 0
Apr 22 10:29:21 thomas-bionic NetworkManager[507]: <info> [1524414561.3358] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/5)
Apr 22 10:29:21 thomas-bionic pppd[2613]: Using interface ppp0
Apr 22 10:29:21 thomas-bionic NetworkManager[507]: Using interface ppp0
Apr 22 10:29:21 thomas-bionic pppd[2613]: Connect: ppp0 <--> /dev/pts/0
Apr 22 10:29:21 thomas-bionic NetworkManager[507]: Connect: ppp0 <--> /dev/pts/0
Apr 22 10:29:21 thomas-bionic pptp[2620]: nm-pptp-service-2601 log[main:pptp.c:353]: The synchronous pptp option is NOT activated
Apr 22 10:29:21 thomas-bionic systemd-udevd[2617]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 22 10:29:21 thomas-bionic NetworkManager[507]: <info> [1524414561.3610] devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Apr 22 10:29:21 thomas-bionic NetworkManager[507]: <info> [1524414561.3613] device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
Apr 22 10:29:21 thomas-bionic pptp[2632]: nm-pptp-service-2601 log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 1 'Start-Control-Connection-Request'
Apr 22 10:29:21 thomas-bionic pptp[2632]: nm-pptp-service-2601 log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply
Apr 22 10:29:21 thomas-bionic pptp[2632]: nm-pptp-service-2601 log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established.
Apr 22 10:29:22 thomas-bionic pptp[2632]: nm-pptp-service-2601 log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 7 'Outgoing-Call-Request'
Apr 22 10:29:22 thomas-bionic pptp[2632]: nm-pptp-service-2601 log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply.
Apr 22 10:29:22 thomas-bionic pptp[2632]: nm-pptp-service-2601 log[ctrlp_disp:pptp_ctrl.c:939]: Outgoing call established (call ID 63889, peer's call ID 52566).
Apr 22 10:29:52 thomas-bionic pppd[2613]: LCP: timeout sending Config-Requests
Apr 22 10:29:52 thomas-bionic NetworkManager[507]: LCP: timeout sending Config-Requests
Apr 22 10:29:52 thomas-bionic NetworkManager[507]: Connection terminated.
Apr 22 10:29:52 thomas-bionic pppd[2613]: Connection terminated.
Apr 22 10:29:52 thomas-bionic NetworkManager[507]: <warn> [1524414592.3891] vpn-connection[0x555885252640,ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test",0]: VPN plugin: failed: connect-failed (1)
Apr 22 10:29:52 thomas-bionic gnome-shell[781]: Removing a network device that was not added
Apr 22 10:29:52 thomas-bionic NetworkManager[507]: <info> [1524414592.4202] vpn-connection[0x555885252640,ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test",0]: VPN service disappeared
Apr 22 10:29:52 thomas-bionic NetworkManager[507]: <info> [1524414592.4244] devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Apr 22 10:29:52 thomas-bionic pppd[2613]: Terminating on signal 15
Apr 22 10:29:52 thomas-bionic NetworkManager[507]: Terminating on signal 15
Apr 22 10:29:52 thomas-bionic NetworkManager[507]: Child process /usr/sbin/pptp XXX.XXX.XXX.XXX --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-2601 (pid 2616) terminated with signal 15
Apr 22 10:29:52 thomas-bionic NetworkManager[507]: Modem hangup
Apr 22 10:29:52 thomas-bionic pppd[2613]: Child process /usr/sbin/pptp XXX.XXX.XXX.XXX --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-2601 (pid 2616) terminated with signal 15
Apr 22 10:29:52 thomas-bionic pppd[2613]: Modem hangup
Apr 22 10:29:52 thomas-bionic pppd[2613]: Exit.
Apr 22 10:29:52 thomas-bionic pptp[2620]: nm-pptp-service-2601 warn[decaps_hdlc:pptp_gre.c:226]: short read (-1): Input/output error
Apr 22 10:29:52 thomas-bionic pptp[2620]: nm-pptp-service-2601 warn[decaps_hdlc:pptp_gre.c:238]: pppd may have shutdown, see pppd log
Apr 22 10:29:52 thomas-bionic pptp[2632]: nm-pptp-service-2601 log[callmgr_main:pptp_callmgr.c:245]: Closing connection (unhandled)
Apr 22 10:29:52 thomas-bionic pptp[2632]: nm-pptp-service-2601 log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 12 'Call-Clear-Request'
Apr 22 10:29:52 thomas-bionic pptp[2632]: nm-pptp-service-2601 log[call_callback:pptp_callmgr.c:84]: Closing connection (call state)
Apr 22 10:29:52 thomas-bionic gnome-shell[1141]: Removing a network device that was not added

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[canti (cantipop)]

Also I cannot do vpn connections after upgrade to bionic from 17.10.

[Raatikka (raatikka)]

I upgraded from Xenial to Bionic and noticed the same. I also noticed that bug preventing from using VPN has been open for 6 months now! Could this be added to your priority list?

Now, I need to be able to use VPN (like many who work for their living). Is there anything I can do for it (in Bionic) or is the best option to downgrade to Xenial?

Thanks

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.