Page MenuHomePureOS Tracker

network-manager-openvpn: fails to work with Librem Tunnel and some other OpenVPN services on byzantium
Closed, ResolvedPublic

Description

OS version: BYZANTIUM

Upstream bug report: https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues/64
Fix merged: https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/merge_requests/34

I request fix to be backported, as the bug prevents Librem Tunnel (and some other OpenVPN services) to connect.

Event Timeline

mladen triaged this task as High priority.Mar 16 2021, 04:04
mladen created this task.
mladen created this object with edit policy "Restricted Project (Project)".
mladen updated the task description. (Show Details)Mar 16 2021, 04:10
jonas.smedegaard renamed this task from Librem Tunnel and some other OpenVPN services not working with networkmanager-openvpn-1.8.12 on byzantium to networkmanager-openvpn: fails to work with Librem Tunnel and some other OpenVPN services on byzantium.Mar 16 2021, 04:12
jonas.smedegaard renamed this task from networkmanager-openvpn: fails to work with Librem Tunnel and some other OpenVPN services on byzantium to network-manager-openvpn: fails to work with Librem Tunnel and some other OpenVPN services on byzantium.

In Byzantium, I see openvpn at version 2.5.1-1. I created a new Purist openvpn certificate, loaded that cert into Network Manager, and as expected received the tun0 interface. I then used the browser to determine my IP and the browser returned 'Your IP address is in Gunzenhausen, Bayern, Germany (91710)' which is the end point of the VPN apparently because normally my address is in Oakville, Connecticut, United States (06779).

Cannot reproduce the issue.

jeremiah.foster lowered the priority of this task from High to Normal.Apr 5 2021, 17:23

I guess the next step is to try to reproduce with Librem Tunnel.

mladen added a comment.Apr 6 2021, 01:21

@jeremiah.foster We already reproduced the issue with Librem Tunnel.

jeremiah.foster added a comment.EditedApr 6 2021, 11:26

With which version of openvpn? Some of the links you provided indicated older versions of openvpn were the issue, we have a newer version in Byzantium now.

mladen added a comment.Apr 6 2021, 13:48

openvpn: 2.5.1-1
network-manager-openvpn: 1.8.12-2

Issue is still reproducible. Like I explained, network-manager-openvpn package needs this fix: https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/merge_requests/34

We're using network-manager-openvpn from Debian - is there an issue for that in Debian's bugtracker?

mladen added a comment.Apr 13 2021, 09:46

@sebastian.krzyszkowiak I am not aware, I could not find anything on their bug tracker. But this issue has been fixed with https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/merge_requests/34 and it seems that version with the fix, v1.8.14, is released already.

mladen added a comment.Apr 13 2021, 09:49

This package version is found in Debian experimental: https://packages.debian.org/experimental/network-manager-openvpn

@jonas.smedegaard could you please work with @mladen to get this fix into byzantium (and ideally also Debian bullseye since this looks like it would qualify).

network-manager-openvpn 1.8.14-1~pureos1 has now been queued for byzantium.
When it enters in landing it will be helpful if you could test and confirm that it works as expected, @mladen - thanks for the detailed investigation!

@mladen Do I understand it correctly that this issue affects only byzantium (not amber)?

mladen added a comment.Apr 26 2021, 08:07

@jonas.smedegaard Yes. I'll will have the latest version tested and report back, thanks!

mladen added a comment.May 6 2021, 13:35

Confirmed, the network-manager-openvpn 1.8.14-1~pureos1 fixes the issue! Thank you @jonas.smedegaard

mladen closed this task as Resolved.May 6 2021, 13:35
guido added a comment.May 7 2021, 03:32

Cool stuff, thanks @jonas.smedegaard , @mladen !