Openconnect VPN is not shown in the plasma Network Manager applet

Bug #1239667 reported by Allcolor-g
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
plasma-nm (Ubuntu)
Fix Released
High
Unassigned

Bug Description

I've installed saucy beta, and openconnect is no more in the available VPN list.

I've installed openconnect and the network-manager-openconnect package but the openconnect option is not present.

network-manager 0.9.8.0-0ubuntu20
network-manager-openconnect 0.9.8.0-1ubuntu2
network-manager-openconnect-gnome 0.9.8.0-1ubuntu2
openconnect 5.01-1
libopenconnect2:amd64 5.01-1
plasma-nm 0.9.3.0-0ubuntu1

lsb_release -rd
Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10

Tags: kubuntu
Allcolor-g (allcolor)
affects: networkmanagement (Ubuntu) → plasma-nm (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in plasma-nm (Ubuntu):
status: New → Confirmed
Revision history for this message
Harald Sitter (apachelogger) wrote :

plasma-nm is built without openconnect support

Changed in plasma-nm (Ubuntu):
status: Confirmed → In Progress
importance: Undecided → High
assignee: nobody → Harald Sitter (apachelogger)
milestone: none → ubuntu-13.10
tags: added: kubuntu
Revision history for this message
Todd Kennedy (toddkenn) wrote :

I was able to get openconnect to show up in Plasma-nm as a VPN source by doing the following:

1. sudo apt-get build-dep plasma-nm
2. sudo apt-get install libopenconnect-dev
3. sudo apt-get source -b plasma-nm
4. Install resulting plasma-widget-networkmanagement_0.9.3.0-0ubuntu4_all.deb and plasma-nm_0.9.3.0-0ubuntu4_i386.deb
 that where generated from step 2. Your file names might be different if you have a different architecture. ie: amd64
5. reboot

The next hurdle is to actually get openconnect to connect to my vpn source, which for some reason it won't.

----- new errors -----------
<info> Starting VPN service 'openconnect'...
<info> VPN service 'openconnect' started (org.freedesktop.NetworkManager.openconnect), PID 3068
<info> VPN service 'openconnect' appeared; activating connections
get_secret_flags: assertion 'is_secret_prop (setting, secret_name, error)' failed
   SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/vpn0, iface: vpn0)
   SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/vpn0, iface: vpn0): no ifupdown configuration found.
<warn> /sys/devices/virtual/net/vpn0: couldn't determine device driver; ignoring...
<info> VPN plugin state changed: starting (3)
<info> VPN connection 'MyVPNConnectionName' (Connect) reply received.
   SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/vpn0, iface: vpn0)
<warn> VPN plugin failed: 0
<info> VPN plugin state changed: stopped (6)
<info> VPN plugin state change reason: 10
<info> Policy set 'WiFiNetwork' (wlan0) as default for IPv4 routing and DNS.
<warn> error disconnecting VPN: Could not process the request because no VPN connection was active.
<info> VPN service 'openconnect' disappeared

Revision history for this message
Todd Kennedy (toddkenn) wrote :

Looking at my VPN session I noticed this message:

10/14/13 09:55:16 AM tkennedy-ThinkPad-T430 openconnect[3095] Got inappropriate HTTP CONNECT response: HTTP/1.1 401 Unauthorized

So I'm not sure why I get this. I can use openconnect at the command line with the same parameters (hostname,username, password) to connect and it connects without issue.

Revision history for this message
Todd Kennedy (toddkenn) wrote :

After further research and trying to connect I was able to connect to my VPN server. So the answer for me is still valid. I think my issue was that I was testing my credentials and switching between VPN server hosts. So what I did below resolved my issue.

---- steps to get openconnect working with Plasma-nm ----
1. sudo apt-get build-dep plasma-nm
2. sudo apt-get install libopenconnect-dev
3. sudo apt-get source -b plasma-nm
4. Install resulting plasma-widget-networkmanagement_0.9.3.0-0ubuntu4_all.deb and plasma-nm_0.9.3.0-0ubuntu4_i386.deb
 that where generated from step 3. Your file names might be different if you have a different architecture. ie: amd64
5. reboot

Revision history for this message
Allcolor-g (allcolor) wrote :

Rebuild plasma-nm as Todd Kennedy instructed did work for me too.

I've openconnect in the list and it works.

Thank you

Revision history for this message
Harald Sitter (apachelogger) wrote :

Fixed by 0.9.3.0-0ubuntu5.

Changed in plasma-nm (Ubuntu):
assignee: Harald Sitter (apachelogger) → nobody
status: In Progress → Fix Released
Revision history for this message
Cherif Tawil (c-tawil-home) wrote :

I had the same problem
tried the instructions from Todd but did not work :(

Basically it works on first connection attempt after creating the VPN connection but subsequent connection attempts do not work.

Figured out a work around, basically
the /etc/NetworkManager/system-connections/<VPN_Connection_Name> has an section called
[vpn-secrets]
form:main:username=USERNAME
lasthost=IP_ADDRESS
xmlconfig=<some XML>

If I remove those I can use the VPN configured connection

Regards
Cherif

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.