Ubuntu
network-manager-openvpn package

OpenVPN connection not stable after upgrade to 18.10 (udp, ipv6)

Bug #1800542 reported by Steve Langasek
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager-openvpn (Ubuntu)
New
High
Unassigned

Bug Description

After upgrade to Ubuntu 18.10, my connection to my employer's VPN server has become unstable.

The server provides both ipv4 and ipv6 endpoints. Since I have global ipv6 at home, my client defaults to connecting over ipv6.

The connection consistently drops after only a few minutes of being connected.

If I force the connection to use ipv4 (by hard-coding the host resolution in /etc/hosts), the connection is stable.

If I use ipv6 and force proto-tcp=yes, the connection is stable.

If I use the default ipv6 and udp, the connection is not stable.

Using tcp for VPNs is suboptimal. Hard-coding addresses in /etc/hosts is suboptimal.

This may be a bug in openvpn rather than in network-manager-openvpn, but I'm starting here.

It's possible there are pathMTU issues involved, but I reproduced this same problem when I was on a different network from my home network (though I did not confirm, when I had access to this other network, that it was ipv6-enabled).

I will work on getting more details about both sides of the network to try to debug this.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2010-09-24 (2957 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: network-manager-openvpn 1.8.6-1ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Tags: cosmic
Uname: Linux 4.18.0-10-generic x86_64
UpgradeStatus: Upgraded to cosmic on 2018-10-18 (11 days ago)
UserGroups: adm admin cdrom dialout docker libvirt libvirtd lpadmin lxd mythtv plugdev sambashare sbuild src sudo
_MarkForUpload: True

See original description
Revision history for this message
Cristian Aravena Romero (caravena) wrote :

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1800542

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

Changed in network-manager-openvpn (Ubuntu):
status: New → Incomplete
Revision history for this message
Steve Langasek (vorlon) wrote : Dependencies.txt

apport information

tags: added: apport-collected cosmic
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Steve Langasek (vorlon) wrote : ProcEnviron.txt

apport information

Revision history for this message
Steve Langasek (vorlon) wrote :

attached, though aside from the package number there doesn't appear to be much of use here.

Changed in network-manager-openvpn (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Please reproduce the problem, do a hard reset and then run this command:

  journalctl -b-1 > prev_boot.txt

and send us the resulting file prev_boot.txt
--
Cristian Aravena Romero (caravena)

Revision history for this message
Steve Langasek (vorlon) wrote :

> Please reproduce the problem, do a hard reset and then run this command:

... absolutely not.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you get a debug log as described on https://wiki.gnome.org/Projects/NetworkManager/Debugging#Debugging_NetworkManager-openvpn ?

Changed in network-manager-openvpn (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
Revision history for this message
Steve Langasek (vorlon) wrote :

Following the debugging instructions at https://wiki.gnome.org/Projects/NetworkManager/Debugging#Debugging_NetworkManager-openvpn was not sufficient to get debug logs; NM still spawned a separate nm-openvpn-service process instead of using the one I was running from a terminal, despite supports-multiple-connections=false being set. Does NM have to be restarted after making this change?

Revision history for this message
Sebastien Bacher (seb128) wrote :

@Steve, right, I just gave it a try and indeed n-m needs to be restarted ('sudo systemctl restart NetworkManager' is enough, no need of rebooting)

Revision history for this message
Steve Langasek (vorlon) wrote :

Thanks, attached is a complete log of an nm-openvpn-service session, ending with exit 1.

Changed in network-manager-openvpn (Ubuntu):
status: Incomplete → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.