No openconnect support in plasma-widget-networkmanagement

Bug #923587 reported by tnorris
84
This bug affects 16 people
Affects Status Importance Assigned to Milestone
networkmanagement (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Support for openconnect vpn was supposedly added to Network Manager on KDE some time ago (see here: http://www.infradead.org/openconnect/gui.html) yet when even the latest plasma-widget-networkmanagement package is installed, it still doesn't show up as a VPN choice and the additional libraries don't seem to be installed.

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

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

Changed in plasma-widget-networkmanagement (Ubuntu):
status: New → Confirmed
Revision history for this message
Todd Kennedy (toddkenn) wrote :

I found this while trying to duild plasma-widget-networkmanagement

-- Found OpenConnect 3.02-unknown:
ERROR: OpenConnection version '3.02-unknown' does not match minimum required (3.03)
OpenConnect plugin will not be built

Seems that the openconnect version is not correct. It needs at least version 3.03 and whats in Universe.

So I would assume since the current openconnect version 3.02 works fine with nm-applet but not with plasma-widget-networkmanagement that there needs to be a separate package of openconnect with an updated version or get nm-applet to work with at least version 3.03 or latest up stream.

Revision history for this message
tnorris (tnorris) wrote :

It appears from this comment (https://bugs.kde.org/show_bug.cgi?id=226028#c51) in the related KDE bug that it does indeed depend on Open Connect 3.03 or higher. I have no idea though how to get the Ubuntu package of OpenConnect upgraded.

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

This morning I was able to get openconnect 3.15 compiled and install along with network-manager-openconnect as well as enabling openconnect support in plasma-widget-networkmanagement. I can now configure an openconnect VPN but when I try to activate it openconnect fails with no agents available for the request. It is running inside a VirtualBox session but I don't think that has anything to do with it. We are getting farther but we're not there yet.

<info> VPN service 'openconnect' appeared; activating connections
NetworkManager[589]: <info> VPN plugin state changed: 1
NetworkManager[589]: <error> [1329489354.186963] [nm-vpn-connection.c:882] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request.
NetworkManager[589]: <info> Policy set 'Host WLAN' (eth0) as default for IPv4 routing and DNS.
avahi-daemon[591]: Withdrawing workstation service for vpn0.
NetworkManager[589]: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/vpn0, iface: vpn0)
NetworkManager[589]: <info> VPN service 'openconnect' disappeared

Also - for some reason when I perform a make install on network-manager-openconnect it installs the network-manager-openconnect-service files in /lib/libexec instead of /lib/NetworkManager. So I had to manually move them. I', sure I'm not passing some argument in somewhere....(gezzzzz) so many configurations....It boggles the mind.

Philip Muškovac (yofel)
Changed in plasma-widget-networkmanagement (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Todd Kennedy (toddkenn) wrote :

Precise now has openconnect 3.15 but yet Plasma Network Manager still does not recognize that there is an openconnect vpn provider.

Revision history for this message
tnorris (tnorris) wrote :

Looking here: http://packages.ubuntu.com/precise/i386/plasma-widget-networkmanagement/filelist you can see the extra .so and desktop files still don't existing in the precise network manager package. I'll bet whoever is building the plasma-widget-networkmanagement deb doesn't have openconnect installed, and therefore those libs don't get built similar to the problem Todd got earlier when his openconnect version was too old. I don't know who builds it though nor how to get it changed.

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

I also noticed that palsma-widget-networkmanagement never suggests package network-manager-openconnect. So I think your on to something tnorris. I'm trying to build from source now to see what the deal is.

Revision history for this message
Philip Muškovac (yofel) wrote :

Reassigning to the current name of the package.

affects: plasma-widget-networkmanagement (Ubuntu) → networkmanagement (Ubuntu)
Revision history for this message
Philip Muškovac (yofel) wrote :

Ok, I've looked at this and here's the problem:
plasma-widget-networkmanagement is from main, openconnect in universe:
     3.15-0ubuntu1 0
        500 http://ftp-stud.hs-esslingen.de/ubuntu/ precise/universe amd64 Packages

packages in the main component aren't allowed to depend on packages from the universe component so there's nothing we can do right now (unless someone files a MIR for openconnect and intents to personally support the package). Thanks to Canonical dropping commercial support for kubuntu we'll probably be able to fix this for 12.10. Until then this isn't fixable in the archive.

Changed in networkmanagement (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
tnorris (tnorris) wrote :

I suppose you could say that the key issue then is in this comment: https://bugs.kde.org/show_bug.cgi?id=226028#c53 in the original bug. If the compile for p-w-nm built the openconnect plugin regardless of whether or not the right version of openconnect was installed (like the rest of the network manager VPN plugins) then the dependency could be avoided and you'd get the extra files with p-w-nm regardless of whether you could use them or not (just like with the other VPN plugins).

Revision history for this message
avlas (avlas) wrote :

I directly asked the developer of plasma-widget-networkmanagement about this in his blog and it seems this is not possible. I just paste below my question and his response (http://lamarque-lvs.blogspot.ca/2012/04/plasma-nm-0901.html). I hope somebody finds a way to workaround this issue...

------ avlas said...

    Hi Lamarque,

    First of all, thanks a lot for your work!

    I'm having an issue with plasma-widget-networkmanagement in kubuntu, I cannot configure openconnect vpn connections. This is due to an ubuntu policy, in which packages in main (plasma-widget-networkmanagement) cannot depend on packages in universe/multiverse (openconnect). You can see comment #9 in https://bugs.launchpad.net/ubuntu/+source/networkmanagement/+bug/923587

    It seems there could be a solution for this (please see comment #10 in https://bugs.launchpad.net/ubuntu/+source/networkmanagement/+bug/923587)

    Do you think it could be feasible?

    I would very much appreciate it, as right now I have to use anyconnect from cisco because of this issue.

    Thanks a lot in advance!
    May 4, 2012 2:46:00 PM GMT-03:00

------ Lamarque said...

    No. Openconnect is a compile time dependency (we need openconnect.h to
    compile the plugin and link against openconnect's libraries). The other VPN
    plugins do not include compile time dependencies so they can be compiled
    without problems.The suggestion in comment #10 would back fire on us some day
    with users complaining about Plasma NM failing to build and I would be the one
    to fix the problem, so no, sorry.

    > I would very much appreciate it, as right now I have to use anyconnect from
    > cisco because of this issue.

    Sorry but this is a packing issue and I will not risk causing troubles
    for all other Plasma NM's users because Kubuntu's policy.
    May 4, 2012 3:18:00 PM GMT-03:00

Revision history for this message
dwmw2 (dwmw2) wrote :

If you have openconnect v3.02 in main and can't upgrade it to a new version, perhaps you could apply just
commit 423eee0b51a204562d6f2ec67893133ebcf200d6 from the openconnect git tree? That adds the openconnect_vpninfo_new_with_cbdata() function that the Plasma code requires.

Other potential solutions involve including a copy of openconnect.h in the packaging for kde-plasma-networkmanagement, and building a *dummy* version of the shared library which just provides the needed symbols, without any code. The tool would link against that shared library at build time, but of course it would *run* against the real library.

Or maybe build a *separate* kde-plasma-networkmanagement-openconnect package in universe. Or just switch to a distro with saner packaging policies :)

Revision history for this message
dwmw2 (dwmw2) wrote :

Oh, and for security reasons make sure you upgrade to openconnect 3.18 anyway; I fixed a buffer overflow. Anyone shipping 3.02 should be shot. There was another crash fix in 3.13, if you're building with libproxy support. And a serious compatibility fix in 3.12 for new versions of Cisco ASA software.

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

I've been trying to compile this myself and have plasma-network-management-0.9.0 compiled with OpenConnect support and also compiled network-manager-openconnect-0.9.4.0 but I still don't have openconnect support in Network manager. I figured I would just build it myself for my own use but there seems to be more issues that I don't know how to diagnose. Does the NetworkManager plasmoid look for a desktop file in /usr/share/kde4/services/ for the vpn service? If so which package is suppose to put it there, and can I just create one with the correct dbus service name for openconnect?

----------------extract from plasma-network-management-0.9.0.build------------------
-- checking for one of the modules 'openconnect'
-- Found OpenConnect 3.15: openconnect;proxy;z;ssl;crypto;xml2

-----------------------------------------------------------------------------
-- The following external packages were located on your system.
-- This installation will have the extra features provided by these packages.
-----------------------------------------------------------------------------
   * mobile-broadband-provider-info - Database of mobile broadband service providers
   * NetworkManager - A daemon for user controlled networking
   * OpenSSL headers - Encryption suite
   * OpenConnect headers and library - Cisco AnyConnect compatible VPN client

Revision history for this message
avlas (avlas) wrote :

This is not working yet in Kubuntu Quantal Alpha 2, but in principle it should as now packages are in the universe repositories. I guess somebody needs to update the dependencies of plasma-widget-networkmanagement to include openconnect

Revision history for this message
avlas (avlas) wrote :

btw, people suffering this bug still can use openconnect from console, as indicated here:

http://www.youtube.com/watch?v=zBEUylO12vI

Revision history for this message
avlas (avlas) wrote :

still a better way to do it using the script in here

https://wiki.archlinux.org/index.php/OpenConnect

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

This bug was fixed in the package networkmanagement - 0.9.0.3-0ubuntu2

---------------
networkmanagement (0.9.0.3-0ubuntu2) quantal; urgency=low

  * Add libopenconnect-dev to build-dependencies (LP: #923587)
 -- Jonathan Kolberg <email address hidden> Tue, 24 Jul 2012 12:30:08 +0200

Changed in networkmanagement (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
dcecchin (dcecchin-deactivatedaccount) wrote :

Could this package be backported to Precise Pangolin or put in the kubuntu backports ppa? Currently it has 0.9.0.1 which doesn't work still.

Rohan Garg (rohangarg)
no longer affects: kdenetwork
Revision history for this message
Rohan Garg (rohangarg) wrote :

Will get this backported into kubuntu-backports next week

Changed in networkmanagement (Ubuntu):
assignee: nobody → Rohan Garg (rohangarg)
Revision history for this message
Rohan Garg (rohangarg) wrote :

Backported packages are going to be available in https://launchpad.net/~rohangarg/+archive/experimental

Revision history for this message
Rohan Garg (rohangarg) wrote :

openconnect support is now available via Kubuntu Backports PPA [1]

[1] https://launchpad.net/~kubuntu-ppa/+archive/backports

Rohan Garg (rohangarg)
Changed in networkmanagement (Ubuntu):
assignee: Rohan Garg (rohangarg) → nobody
Revision history for this message
dcecchin (dcecchin-deactivatedaccount) wrote :

Thanks for that, I can confirm this works now.

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

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

Revision history for this message
Michael Kuhlmann (kuhlmann-michael) wrote :

This bug effects me too. Im using saucy beta.

I have the packages network-manager and network-manager-openconnect installed.

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

Seems we are bitten again by this bug in Kubuntu 13.10. I too am affected as well.

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

Please report a new bug against plasma-nm.

Revision history for this message
Allcolor-g (allcolor) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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