Adding just this to NetworkManager environment seems to be a sufficient
workaround:
$ cat /etc/systemd/system/NetworkManager.service.d/openvpn-workaround.conf
[Service]
Environment="NM_OPENVPN_CHROOT="
At least the connection survives SIGUSR1 to openvpn process.
I presume the
This still happens with:
network-manager/testing,unstable,now 1.10.6-2 amd64 [installed]
network-manager-openvpn/testing,unstable,now 1.8.2-1 amd64 [installed]
openvpn/testing,unstable,now 2.4.5-1 amd64 [installed]
I've found a potentially less clumsy workaround, but didn't try it yet:
Package: network-manager-openvpn
Version: 1.2.8-2
Followup-For: Bug #667611
Workaround used according to Christian's suggestion about chroot not
holding the --up script : mv /var/lib/openvpn/chroot
/var/lib/openvpn/chroot.disabled
thus preventing chrooting.
-nsouch
-- System Information:
Package: network-manager-openvpn
Version: 1.2.0-1
Followup-For: Bug #667611
I think the root cause of this issue may have changed over time, given the
activity on the upstream openvpn bug report, but the fact that it still
fails.
I see this locally with this error in the logs:
May 9 09:18:49
On Thu, Apr 05, 2012 at 12:18:23PM +0200, Christian Michallek wrote:
Package: network-manager-openvpn
Version: 0.9.4.0-1
I thought i copy this bug over here, because its already quite old and still
not fixed.
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/280160
I
On Fri, Apr 11, 2014 at 09:29:52AM +0900, Mike Hommey wrote:
On Thu, Apr 05, 2012 at 12:18:23PM +0200, Christian Michallek wrote:
Package: network-manager-openvpn
Version: 0.9.4.0-1
I thought i copy this bug over here, because its already quite old and still
not fixed.
Package: network-manager-openvpn
Version: 0.9.4.0-1
I thought i copy this bug over here, because its already quite old and
still not fixed.
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/280160
I can confirm the same behavior in debian squeeze and wheezy.
at least
7 matches
Mail list logo
