Open VPN configuration in plasma-widget-network-manager not working

Bug #351390 reported by Mikael Larsson
112
This bug affects 14 people
Affects Status Importance Assigned to Milestone
knetworkmanager
Fix Released
Medium
plasma-widget-networkmanagement (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: plasma-widget-network-manager

I tried to configure an openvpn connection in kunbuntu jaunty beta release (clean install +openvpn + latest updates).
I've not been able to get this working. Don't know if it is supposed to work?

When opening the OpenVPN configuration dialog Connection Type is set to "X.509 Certificates" but the fields under are "CA file", "Username" and "Password". By selecting another Connection Type (e.g. password) and then going back to "X.509 Certificates" I get the opetions that one should get, i.e.
* CA file
* Certificate
* Key

If I open the "Optional Information" tab there is one check box for overriding default port and one check box for overriding VPN addresses for set specified address masks. Changing these checkboxes do not enable the input fields so it's not possible to enter any information.

If i try so save the connection and open it up later I have to switch between connection types again to see the saved paths, but it looks like the key path is not saved at all.

Trying to connect to the configured connection fails, all I can see in syslog is:
"<WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/3 failed to activate (timeout): (0) Connection was not provided by any settings service"

Where is this configuration stored, is it possible to edit the config manually as a workaround?

Installed plasma-widget-network-manager version: 0.0+svn930811-0ubuntu2

/Mikael

Revision history for this message
Peter (peterroots) wrote :

I can confirm this (running 9.04 beta in virtualbox)
In fact it is a bit worse than mentioned. Before I installed openvpn and the plugin networkmanager showed up the vpn tab and let me fill in the details (albeit with the issues already mentioned) The connection I entered did not appear on the list of available vpn connections and I was given no hint that I did not have openvpn installed. I only discovered this when I tried connecting from the command line!
Once I installed openvpn and the plugin I saw the same odd behaviour as regards entering the key and certificates. I could also not enter a cipher type or enter anything in the tls auth section (not that it gives any clue at all what I should enter here)
The saved connection does not appear anywhere on the networkmanager so I can't try connecting with it.
the configuration page won't use the .ovpn file I can use with openvpn command line and there is no hint on the page of how to extract the settings from it. How would any normal person know how to get keys and certificates from the .p12 file? I did not! If openvpn can use this file, why not NM?
for a GUI 'it just works' set up this is rather off putting especially as it does not work at all.

Revision history for this message
Laurent Poujoulat (lpoujoulat-users) wrote :

Same thing for me (difficult to edit the connection, no way to use pkcs12 file)
but I sometimes get the VPN connection name in the list. Then, if I click on it the VPN connection is made (checked in the logs), but no feedback of any kind is provided by the applet while connecting or when connected. Moreover there is no way to disconnect !

I checked upstream in KDE SVN, and I have sadly seen there is not much work done around OpenVPN plugin.

meanwhile I use the gnome applet for network manager (nm-applet), as it works flawlessly with OpenVPN, although you have to split out the p12 file.

Revision history for this message
Olaf Lenz (olenz) wrote :

Same here. Unfortunately, nm-applet doesn't work in my case either (the applet forgets the HMAC setting), nor does kvpnc in the version provided by ubuntu (alos forgets some settings).
The only way I got the VPN connection running is to compile my own up-to-date kvpnc, which solved the problem.

Revision history for this message
Olaf Lenz (olenz) wrote :

I have just filed bug #362747, in which I summarize all the problems in connecting OpenVPN under Kubutnu jaunty.

Revision history for this message
WalterNicholls (walter-nic) wrote :

I filed bug #368295 yesterday for the same thing (I swear I looked for similar issues first yet here it is). That bug has a much more detailed description.
This is woeful, I see a lot of people subscribed to this area of functionality, so someone please must be able to put a rocket under someone!!

Revision history for this message
Moreno Bartalucci (moreno-bartalucci) wrote :

I'm having the same problems concerning the editing of the connection parameters for openvpn.
Some of the parameters are simply forgotten, others are never enabled on the user interface so I just can't put them in.
Due to this lack of configuration I never tried the connection so I don't know about the connection issues.
I hope it is fixed soon.
Although openvpn works fine from the command line (for me), I'd like to manage it from the desktop.

Revision history for this message
Olaf Lenz (olenz) wrote :

WalterNicolls: The bug that you linked up there is something about problems with java, so I guess you placed a wrong link. Could you please post the correct link?

Revision history for this message
WalterNicholls (walter-nic) wrote :

Ooops, sorry, Bug #368395.

Changed in plasma-widget-network-manager (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
affects: plasma-widget-network-manager (Ubuntu) → plasma-widget-networkmanagement (Ubuntu)
Changed in knetworkmanager:
status: Unknown → In Progress
Revision history for this message
Jithin Emmanuel (jithin1987) wrote :

Is this bug specific to openvpn. I use vpnc and it also has the same issue. Should I open a separate bug for it?

Revision history for this message
Jonathan Thomas (echidnaman) wrote :
Changed in knetworkmanager:
status: In Progress → Fix Released
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fix committed in upstream svn.

Changed in plasma-widget-networkmanagement (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Jithin Emmanuel (jithin1987) wrote :

Does the fix committed includes the fix for vpnc? Please include vpnc also.

 Its fixed in http://bugs.kde.org/show_bug.cgi?id=188489.

Commit link http://websvn.kde.org/?view=rev&revision=1006258.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fix released to Karmic.

Changed in plasma-widget-networkmanagement (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Peter (peterroots) wrote :

The bug as reported is fixed, as far as I can see in karmic but it is still not possible to connect to a openvpn using x509 certificates as there is no space anywhere on the config to enter the passphrase and you are not prompted to enter one at anytime!
No passphrase = rejected connection

Dec 2 14:29:22 PeterLT NetworkManager: <info> Starting VPN service 'org.freedesktop.NetworkManager.openvpn'...
Dec 2 14:29:23 PeterLT NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.openvpn' started (org.freedesktop.NetworkManager.openvpn), PID 25211
Dec 2 14:29:23 PeterLT NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.openvpn' just appeared, activating connections
Dec 2 14:29:24 PeterLT NetworkManager: <info> VPN plugin state changed: 3
Dec 2 14:29:24 PeterLT NetworkManager: <info> VPN connection 'DCMC' (Connect) reply received.
Dec 2 14:29:24 PeterLT NetworkManager: <WARN> nm_vpn_connection_connect_cb(): VPN connection 'DCMC' failed to connect: 'No VPN secrets!'.
Dec 2 14:29:24 PeterLT NetworkManager: <WARN> connection_state_changed(): Could not process the request because no VPN connection was active.

Revision history for this message
3ntix (francesco-3ntini) wrote :

I've the last k-ubuntu, maverick, but with the last relase of kde (4.5.3) and I can't to connect via openVPN. In truth, I can connect only the first time that I've configured the widget network-manager but now is impossible.
I found this but because I've the same error in my syslog file
<warn> connection /org/freedesktop/NetworkManagerSettings/4 (scope 2) failed to activate (timeout)

Is possible that this bug is not fixed yet?
Thanks,
Francesco

Changed in knetworkmanager:
importance: Unknown → Medium
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.