You are not logged in.

#1 2012-11-28 07:22:34

digger
Member
Registered: 2012-07-06
Posts: 8

[SOLVED] networkmanager-openconnect does not work, CLI does work.

Hi, seven to eight months ago I tried Arch and back then I had the same issue.  Now I am back again smile.

Using the latest install media, I have gnome 3 running.  I have configured openconnect the same way I have on my Fedora and SuSe systems, but I cannot get Arch NetworkManager/openconnect to work through the GUI

# pacman -Ss openconnect
extra/networkmanager-openconnect 0.9.6.2-1 [installed]
    NetworkManager VPN integration for openconnect
extra/openconnect 1:4.07-1 [installed]
    Open client for Cisco AnyConnect VPN
# pacman -Ss network-manager-applet
extra/network-manager-applet 0.9.6.4-1 [installed]
    GNOME frontends to NetWorkmanager

Things I have tried as suggested from various google searches

* reboot system
* restart NetworkManager after each change
* symbolic linking
  # history | grep ln
  ~
  435  ln -s /usr/lib/networkmanager/nm-openconnect-auth-dialog /usr/lib/NetworkManager/
  438  ln -s /usr/lib/networkmanager/nm-openconnect-service /usr/lib/NetworkManager/
  439  ln -s /usr/lib/networkmanager/nm-openconnect-service-openconnect-helper /usr/lib/NetworkManager/
* another sym link
# history | grep gnome-shell
   391  ln -s /usr/lib/networkmanager/nm-openconnect-auth-dialog /usr/lib/gnome-shell/
* installing additional networkman plugins
# pacman -Ss networkmanager
extra/network-manager-applet 0.9.6.4-1 [installed]
     GNOME frontends to NetWorkmanager
extra/networkmanager 0.9.6.4-1 [installed]
     Network Management daemon
extra/networkmanager-openconnect 0.9.6.2-1 [installed]
     NetworkManager VPN integration for openconnect
extra/networkmanager-openvpn 0.9.6.0-1 [installed]
     NetworkManager VPN plugin for OpenVPN
extra/networkmanager-pptp 0.9.6.0-2 [installed]
     NetworkManager VPN plugin for pptp
extra/networkmanager-vpnc 0.9.6.0-1 [installed]
     NetworkManager VPN plugin for vpnc


Log output:

# tail -f /var/log/messages.log
Nov 27 22:53:48 linux-rocks NetworkManager[1675]: <info>   address 10.3.1.6
Nov 27 22:53:48 linux-rocks NetworkManager[1675]: <info>   prefix 25 (255.255.255.128)
Nov 27 22:53:48 linux-rocks NetworkManager[1675]: <info>   gateway 10.3.1.1
Nov 27 22:53:48 linux-rocks NetworkManager[1675]: <info>   hostname 'linux-rocks'
Nov 27 22:53:48 linux-rocks NetworkManager[1675]: <info>   nameserver '10.3.1.1'
Nov 27 22:53:48 linux-rocks NetworkManager[1675]: <info>   domain name 'domain.com'
Nov 27 22:53:48 linux-rocks dbus[354]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Nov 27 22:53:48 linux-rocks dbus-daemon[354]: dbus[354]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Nov 27 22:53:48 linux-rocks dbus-daemon[354]: dbus[354]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 27 22:53:48 linux-rocks dbus[354]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 27 23:13:26 linux-rocks NetworkManager[1675]: <info> Starting VPN service 'openconnect'...
Nov 27 23:13:26 linux-rocks NetworkManager[1675]: <info> VPN service 'openconnect' started (org.freedesktop.NetworkManager.openconnect), PID 2993
Nov 27 23:13:26 linux-rocks NetworkManager[1675]: <info> VPN service 'openconnect' appeared; activating connections
Nov 27 23:13:26 linux-rocks NetworkManager[1675]: <info> VPN plugin state changed: init (1)
Nov 27 23:13:26 linux-rocks NetworkManager[1675]: <info> Policy set 'Auto 1st floor' (wlan0) as default for IPv4 routing and DNS.
Nov 27 23:13:31 linux-rocks NetworkManager[1675]: <info> VPN service 'openconnect' disappeared
# tail -f /var/log/errors.log
Nov 27 19:21:46 linux-rocks NetworkManager[1124]: <error> [1354072906.329566] [nm-vpn-connection.c:1405] get_secrets_cb(): Failed to request VPN secr
ets #2: (6) No agents were available for this request.
Nov 27 19:23:16 linux-rocks NetworkManager[1337]: <error> [1354072996.291610] [nm-vpn-connection.c:1405] get_secrets_cb(): Failed to request VPN secr
ets #2: (6) No agents were available for this request.
Nov 27 19:23:24 linux-rocks NetworkManager[1337]: <error> [1354073004.695017] [nm-vpn-connection.c:1405] get_secrets_cb(): Failed to request VPN secr
ets #2: (6) No agents were available for this request.
Nov 27 19:36:13 linux-rocks NetworkManager[1337]: <error> [1354073773.332671] [nm-vpn-connection.c:1405] get_secrets_cb(): Failed to request VPN secr
ets #2: (6) No agents were available for this request.
Nov 27 19:42:59 linux-rocks NetworkManager[1484]: <error> [1354074179.844412] [nm-vpn-connection.c:1405] get_secrets_cb(): Failed to request VPN secr
ets #2: (6) No agents were available for this request.
Nov 27 19:46:43 linux-rocks NetworkManager[1484]: <error> [1354074403.643156] [nm-vpn-connection.c:1405] get_secrets_cb(): Failed to request VPN secr
ets #2: (6) No agents were available for this request.
Nov 27 19:46:56 linux-rocks NetworkManager[1484]: <error> [1354074416.722930] [nm-vpn-connection.c:1405] get_secrets_cb(): Failed to request VPN secr
ets #2: (6) No agents were available for this request.
Nov 27 20:05:30 linux-rocks NetworkManager[1484]: <error> [1354075530.651087] [nm-vpn-connection.c:1405] get_secrets_cb(): Failed to request VPN secr
ets #2: (6) No agents were available for this request.
Nov 27 20:06:49 linux-rocks NetworkManager[1675]: <error> [1354075609.118254] [nm-vpn-connection.c:1405] get_secrets_cb(): Failed to request VPN secr
ets #2: (6) No agents were available for this request.
Nov 27 22:33:10 linux-rocks NetworkManager[1675]: <error> [1354084390.259571] [nm-vpn-connection.c:1405] get_secrets_cb(): Failed to request VPN secr
ets #2: (6) No agents were available for this request.

Thanks in advance

edit adding
# cat /etc/dbus-1/system.d/nm-openconnect-service.conf
<!DOCTYPE busconfig PUBLIC
"-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/db … config.dtd">
<busconfig>
    <policy user="root">
        <allow own="org.freedesktop.NetworkManager.openconnect"/>
        <allow send_destination="org.freedesktop.NetworkManager.openconnect"/>
    </policy>
    <policy user="nm-openconnect">
        <allow own="org.freedesktop.NetworkManager.openconnect"/>
        <allow send_destination="org.freedesktop.NetworkManager.openconnect"/>
    </policy>
    <policy context="default">
        <deny own="org.freedesktop.NetworkManager.openconnect"/>
        <deny send_destination="org.freedesktop.NetworkManager.openconnect"/>
    </policy>
</busconfig>

Last edited by digger (2012-12-03 03:59:34)

Offline

#2 2012-12-02 23:51:15

heiko
Member
Registered: 2012-04-09
Posts: 9

Re: [SOLVED] networkmanager-openconnect does not work, CLI does work.

Experienced the same problem with networkmanager-vpnc. I created a patch that works around the problem. See this post.

As I think this problem is rather related to networkmanager-applet or gnome-shell it could work for you, too.

Offline

#3 2012-12-03 03:58:53

digger
Member
Registered: 2012-07-06
Posts: 8

Re: [SOLVED] networkmanager-openconnect does not work, CLI does work.

Heiko, thanks for the support.  But I just solved the issue a few min ago big_smile.

The fix was what I have tried in the past execpt the system needs to be rebooted, I believe this is related to dbus?  There are very rare instances when a Linux box needs to be rebooted and dbus seems to add to that?

The fix:

 # ln -s /usr/lib/networkmanager/nm-openconnect-auth-dialog /usr/lib/gnome-shell/ 

how to find the issue
* stop NetworkManager
* get the uuid of the connection you are trouble-shooting
* start NetworkManager via command line with debugging
* view the debug log

 # systemclt stop NetworkManager
# cat /etc/NetworkManager/system-connections/testing | grep uuid
uuid=e6e8b3f3-4eb4-4c5e-b0ab-f50a08695dd0
# NM_SERIAL_DEBUG=3 NetworkManager --no-daemon 2>&1 | tee /tmp/nmserial.txt
# view /tmp/nmserial.txt 

In /tmp/nmserial.txt you will notice that the uuid is failing even before NetworkManager is done connecting to your LAN.  This then led me to:

$ view .cache/gdm/session.log
~
      JS LOG: Error 'VPN plugin at /usr/lib/gnome-shell/nm-openconnect-auth-dialog is not executable' while processing VPN keyfile '/etc/NetworkManager/VPN/nm-openconnec
t-service.name'
      JS LOG: Error 'VPN plugin at /usr/lib/gnome-shell/nm-openvpn-auth-dialog is not executable' while processing VPN keyfile '/etc/NetworkManager/VPN/nm-openvpn-servic
e.name'
      JS LOG: Error 'VPN plugin at /usr/lib/gnome-shell/nm-vpnc-auth-dialog is not executable' while processing VPN keyfile '/etc/NetworkManager/VPN/nm-vpnc-service.name
'
      JS LOG: Invalid VPN service type (cannot find authentication binary)

The issue:  I was only restarting NetworkManager but it was not the issue.  I then tried.

# systemctl restart dbus

Which when gnome restarted I got the auth-dialog gui but the connection failed, so I rebooted and it worked big_smile.

I hope this helps others!

Last edited by digger (2012-12-03 16:45:52)

Offline

#4 2012-12-11 23:46:06

heiko
Member
Registered: 2012-04-09
Posts: 9

Re: [SOLVED] networkmanager-openconnect does not work, CLI does work.

Ok, that is much easier! Your solution also solves my problem (which is the same with vpnc).

Apparently the auth dialog that pops up with the symlink is another one as the one that is used for my workaround.

Offline

#5 2012-12-23 16:48:59

michaels
Member
Registered: 2012-10-17
Posts: 20

Re: [SOLVED] networkmanager-openconnect does not work, CLI does work.

Is it sufficient to add just the auth-dialog symlink mentioned in #3 or do I have to create the others from #1 as well (by the way, just for understanding: What do they do? :-) )? Creating just the mentioned one doesn't solve the problem for me, apparently. The other things in your post #3 are just for information, right?

The interesting thing is that I had occasional problems with vpnc and Gnome 3.6, but at least after rebooting it always worked. Now, after not using VPN for some time, the problem reappeared and persists...

Offline

#6 2016-06-01 09:33:01

Ephraim
Member
Registered: 2012-08-22
Posts: 5

Re: [SOLVED] networkmanager-openconnect does not work, CLI does work.

Thanks a lot digger!
Creating the link of nm-openconnect-auth-dialog in the gnome-shell folder did the trick for me!

Sadly it is more than 2 years now, and the bug is still in ubuntu (even 16.10 alpha). Is there any bug report where I can comment on?

Cheers,
Ephraim

Offline

Board footer

Powered by FluxBB