Bug 1422763 - Unable to import .ovpn
Summary: Unable to import .ovpn
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-nm
Version: 25
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-16 06:41 UTC by B H
Modified: 2017-02-18 04:47 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-18 04:47:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
.ovpn file used (270 bytes, text/plain)
2017-02-16 14:12 UTC, B H
no flags Details

Description B H 2017-02-16 06:41:28 UTC
Description of problem: Im unable to import a vpn file from OpenVPN (.ovpn)


Version-Release number of selected component (if applicable):

Installed Packages
Name        : NetworkManager
Arch        : x86_64
Epoch       : 1
Version     : 1.4.4
Release     : 3.fc25
Size        : 10 M
Repo        : @System
From repo   : updates
Summary     : Network connection manager and user applications
URL         : http://www.gnome.org/projects/NetworkManager/
License     : GPLv2+
Description : NetworkManager is a system service that manages network interfaces and
            : connections based on user or automatic configuration. It supports
            : Ethernet, Bridge, Bond, VLAN, Team, InfiniBand, Wi-Fi, mobile broadband
            : (WWAN), PPPoE and other devices, and supports a variety of different VPN
            : services.

➜  ~ cat /etc/redhat-release 
Fedora release 25 (Twenty Five)


How reproducible: Every time


Steps to Reproduce:
1.Open the Connection Editor
2.click Add, click Import VPN
3.choose the .ovpn file, click Open and nothing happens

Actual results: Not a thing happens. Click Open and nothing happens.


Expected results:Not a thing happens.


Additional info:

Comment 1 B H 2017-02-16 14:12:57 UTC
Created attachment 1250874 [details]
.ovpn file used

Comment 2 poma 2017-02-16 15:30:45 UTC
openvpn_config.ovpn opens with no issues;

Tested with:
NetworkManager-1.7.1-0.4.20170207gitca5f915.fc24.x86_64
NetworkManager-openvpn-1.2.8-2.fc24.x86_64
NetworkManager-openvpn-gnome-1.2.8-2.fc24.x86_64
nm-connection-editor-1.4.5-0.4.20170207gitd898ecf.fc24.x86_64
network-manager-applet-1.4.5-0.4.20170207gitd898ecf.fc24.x86_64

Comment 3 poma 2017-02-16 16:59:53 UTC
What the reporter described here is reproducible, but with kde5-nm-connection-editor i.e. plasma-nm.

See if you can find anything relevant to the issue here:
https://bugs.kde.org/describecomponents.cgi?product=plasma-nm

Comment 4 B H 2017-02-16 18:04:10 UTC
Thanks poma.  I only found this: https://bugs.kde.org/show_bug.cgi?id=310605 But its from 2012 thru 2014.  

Any chance I can 'side-grade' to:
NetworkManager-1.7.1-0.4.20170207gitca5f915.fc24.x86_64
NetworkManager-openvpn-1.2.8-2.fc24.x86_64
nm-connection-editor-1.4.5-0.4.20170207gitd898ecf.fc24.x86_64
network-manager-applet-1.4.5-0.4.20170207gitd898ecf.fc24.x86_64

Comment 5 poma 2017-02-16 20:58:57 UTC
I've provided a link as reference in the thread on the user mailing list, where you can find and rebuild SOURCE RPMS.
However these are TEST builds, and if you use them, you do so at your own risk.
With all due respect, I do not recommend you do this, because you're new here, rigth.

Comment 6 B H 2017-02-16 22:11:26 UTC
Understood.  I have no issues with compiling packages from source.  However I don't want to have to do that to get a working NM gui.

Comment 7 Thomas Haller 2017-02-16 23:27:52 UTC
the issues described in comment 0 does not happen for me when using nm-connection-editor.

also plasma-nm and gnome-control-center, all import the attached ovpn file as expected.

(all on Fedora 25).

Comment 8 B H 2017-02-17 00:26:08 UTC
Thomas, What versions of plasma-nm are you running?

Comment 9 Jan Grulich 2017-02-17 06:39:01 UTC
It works for me, do you have plasma-nm-openvpn installed?

Comment 10 Ed Greshko 2017-02-17 07:12:13 UTC
Works for me as well.

plasma-nm-mobile-5.8.5-1.fc25.x86_64
plasma-nm-pptp-5.8.5-1.fc25.x86_64
plasma-nm-openvpn-5.8.5-1.fc25.x86_64
plasma-nm-openconnect-5.8.5-1.fc25.x86_64
plasma-nm-5.8.5-1.fc25.x86_64
plasma-nm-vpnc-5.8.5-1.fc25.x86_64
plasma-nm-strongswan-5.8.5-1.fc25.x86_64

Comment 11 Ed Greshko 2017-02-17 07:13:18 UTC
That is, of course, if the file is named something.ovpn.

Comment 12 poma 2017-02-17 13:44:26 UTC
That's right,
# dnf install plasma-nm-openvpn
 then
$ kde5-nm-connection-editor
  "Add - Import VPN..."
 will open 'openvpn_config.ovpn'

Comment 13 B H 2017-02-17 14:15:35 UTC
That did it, profile successfully imported.  Is there any reason why the Openvpn plasma package isnt installed by default like the others are?

Comment 14 B H 2017-02-17 19:00:59 UTC
(In reply to B H from comment #13)
> That did it, profile successfully imported.  Is there any reason why the
> Openvpn plasma package isnt installed by default like the others are?

As a side note, the profile imported however somethings amiss because the connection times out, also only asks me for a password but no user.  Not related to this issue but I wanted to mention it.

Comment 15 B H 2017-02-18 04:47:37 UTC
So this issue is resolved after manual installation of plasma-nm-openvpn.

I'd think that moving forward with the other VPN options already available by default (anyconnect, openswan, etc) that openvpn should be included as well. Or at least give an error trying to import an .ovpn without that required package installed.

Thanks poma, Ed, Jan and Thomas.


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