network-manager-fortisslvpn not working but openfortivpn does

Bug #1879377 reported by robin
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
network-manager-fortisslvpn (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I've used network-manager-fortisslvpn to establish a VPN but it doesn't work. I setup the VPN and then try to load a web page which can only be loaded if on the VPN. The window keeps still trying to connect (dots indicating loading keep moving)
I do it directly from a terminal, via openfortivpn, i.e. I run the command
openfortivpn the.apropriate.url:port -u my.user
and it establishes the tunnel OK. I'm able to load the said page right away.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager-fortisslvpn 1.2.10-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 18 20:12:58 2020
InstallationDate: Installed on 2020-04-25 (22 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: network-manager-fortisslvpn
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
robin (rbfster) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in network-manager-fortisslvpn (Ubuntu):
status: New → Confirmed
Revision history for this message
Kolmar Kafran (kafran) wrote :

This is a critical bug with network-manager-fortisslvpn incompatibility with openfortivpn >= 1.11.0. This package is useless right now. Ubuntu needs to repackage it with a patch.

Before openfortipvn 1.11.0 the default configuration was equivalent to:
--set-dns=1 --pppd-use-peerdns=1
Starting with openfortivpn 1.11.0 the default configuration is equivalent to:
--set-dns=1 --pppd-use-peerdns=0
NetworkManager-fortisslvpn expects the configuration to be equivalent to:
--set-dns=0 --pppd-use-peerdns=1
This expectation breaks with openfortivpn 1.11.0 because NetworkManager-fortisslvpn only passes this command line option:
--no-dns / --set-dns=0
Starting with openfortivpn 1.11.0 it needs to be:
--no-dns / --set-dns=0 --pppd-use-peerdns=1

There is already a patch. More information on: https://gitlab.gnome.org/GNOME/NetworkManager-fortisslvpn/-/merge_requests/13

There is a patch on Fedora's package: https://src.fedoraproject.org/rpms/NetworkManager-fortisslvpn/c/6378487

robin (rbfster)
description: updated
Revision history for this message
Mathieu (mathieu.web) wrote (last edit ):

Hi, 3 years down the road, any update on this? NetworkManager-fortisslvpn is now available as 1.4.0 (a .deb exists in Debian 12/unstable), but Ubuntu is still stuck with 1.2.10. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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