Bug 1405456 - VPN connection using NM fails (timeouts) but the same connection works from terminal
Summary: VPN connection using NM fails (timeouts) but the same connection works from t...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager-fortisslvpn
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-16 14:49 UTC by Paweł
Modified: 2017-12-12 10:36 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
: 1490874 (view as bug list)
Environment:
Last Closed: 2017-12-12 10:36:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Logs of vpn connection attempts. (6.44 KB, text/plain)
2016-12-16 14:49 UTC, Paweł
no flags Details
detailed log as per comment #1 (45.92 KB, text/plain)
2017-08-01 09:13 UTC, John
no flags Details

Description Paweł 2016-12-16 14:49:50 UTC
Created attachment 1232558 [details]
Logs of vpn connection attempts.

Description of problem:
Can not connect to OpenfortiSSL VPN from NetworkManager via GUI.

Version-Release number of selected component (if applicable):
latest in Fedora 25:
NetworkManager-1.4.2-2.fc25.x86_64
NetworkManager-fortisslvpn-gnome-1.2.4-1.fc25.x86_64
openfortivpn compiled on 2016-11-27, from https://github.com/adrienverge/openfortivpn

How reproducible:
Inconsistent. Let's say 50/50. But openfortivpn tool from terminal works everytime.

Steps to Reproduce:
1. Configure FortiSSL VPN connection
2. Enable VPN from NetworkManager via GUI
3. Wait for connection

Actual results:
Timeout and no VPN connection established

Expected results:
Connecting to VPN

Additional info:
The same connections works, when using openfortivpn, via terminal. Both examples are inside attached log.

Making this bug report, because I see no reason it (NM) should timeout/fail a connection, when it works with plain openfortivpn tool everytime. Can timeout be set to custom value?

Comment 1 Thomas Haller 2016-12-16 15:12:53 UTC
Hm...

unclear why... and I have no setup to reproduce this.

I would enable debug logging of NetworkManger:

 sudo nmcli general logging level TRACE domains ALL,VPN_PLUGIN

Note, it's important to explicitly mention "VPN_PLUGIN" domain. It's exculded from "ALL". See also https://cgit.freedesktop.org/NetworkManager/NetworkManager/plain/contrib/fedora/rpm/NetworkManager.conf?id=master

Beware not to post trace loggings without checking for sensitive data.

Comment 2 John 2017-08-01 09:13:00 UTC
Created attachment 1307471 [details]
detailed log as per comment #1

detailed log as per comment #1
same issue, Fedora 25 / 26

Comment 4 Yauhen Lazurkin 2017-09-29 09:34:17 UTC
Happens on Fedora 26 as well. openfortivpn in terminal works perfectly, but NM fails with timeout.
Versions are:
>rpm -q NetworkManager NetworkManager-fortisslvpn NetworkManager-fortisslvpn-gnome openfortivpn
NetworkManager-1.8.2-1.fc26.x86_64
NetworkManager-fortisslvpn-1.2.4-2.fc26.x86_64
NetworkManager-fortisslvpn-gnome-1.2.4-2.fc26.x86_64
openfortivpn-1.3.0-2.fc26.x86_64

Log output looks very similar.

Comment 5 Fedora End Of Life 2017-11-16 19:39:40 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2017-12-12 10:36:47 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.