Bug 1017471

Summary: Unable to connect to VPN using openconnect via Network Manager
Product: [Fedora] Fedora Reporter: GS <gvs234>
Component: NetworkManager-openconnectAssignee: David Woodhouse <dwmw2>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 20CC: danw, dcbw, dwmw2
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: network-manager-applet-0.9.9.0-7.git20131028.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-01 03:53:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description GS 2013-10-10 00:57:41 UTC
Description of problem:
When connecting to VPN via Network Manager, either clicking on 'On' next to VPN Connections or selecting the VPN by name, it fails to initiate the VPN Connection.

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

How reproducible:
Everytime

Steps to Reproduce:
1.  Configured VPN using Network Settings.  
2.  Clicked add, interface type VPN and clicked Create.  
3.  Selected Cisco AnyConnect Compatible VPN (openconnect) and clicked create.  
4.  Entered in Gateway and clicked Save.  
5.  Initiate connection via Name or VPN Connections.
6.  No dialog box for prompting for credentials.

Actual results:
Starting connection to VPN via Network Manager does nothing.

Expected results:
Starting connection to VPN via Network Manager prompts for credentials and connects to VPN.

Additional info:
Similar to bug 1014716 however system is running the version of Network Manager stated and dialog box does not appear requesting credentials.

Running openconnect via the shell using the following command works successfully.

openconnect --script /etc/vpnc/vpnc-script remote.somevpn.com

tail -f /var/log/messages

Oct  9 19:59:59 LAPTOP NetworkManager[1023]: <info> Starting VPN service 'openconnect'...
Oct  9 19:59:59 LAPTOP NetworkManager[1023]: <info> VPN service 'openconnect' started (org.freedesktop.NetworkManager.openconnect), PID 3062
Oct  9 19:59:59 LAPTOP kernel: [ 1698.091597] tun: Universal TUN/TAP device driver, 1.6
Oct  9 19:59:59 LAPTOP kernel: [ 1698.091601] tun: (C) 1999-2004 Max Krasnyansky <maxk>
Oct  9 19:59:59 LAPTOP NetworkManager[1023]: <info> VPN service 'openconnect' appeared; activating connections
Oct  9 19:59:59 LAPTOP NetworkManager[1023]: <error> [1381363199.282910] [vpn-manager/nm-vpn-connection.c:1534] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request.
Oct  9 20:00:04 LAPTOP NetworkManager[1023]: <info> VPN service 'openconnect' disappeared


rpm -aq | grep -i "network\|openconnect"
NetworkManager-vpnc-0.9.8.2-2.fc20.x86_64
NetworkManager-openvpn-0.9.8.2-3.fc20.x86_64
NetworkManager-0.9.9.0-14.git20131003.fc20.x86_64
NetworkManager-openconnect-0.9.8.0-2.fc20.x86_64
glib-networking-2.38.0-1.fc20.x86_64
dracut-network-033-3.git20130913.fc20.x86_64
NetworkManager-l2tp-0.9.8-2.fc20.x86_64
NetworkManager-pptp-0.9.8.2-3.fc20.x86_64
NetworkManager-glib-0.9.9.0-14.git20131003.fc20.x86_64
openconnect-5.01-4.fc20.x86_64
network-manager-applet-0.9.9.0-6.git20130913.fc20.x86_64

Comment 1 Dan Winship 2013-10-10 13:54:18 UTC
Oct  9 19:59:59 LAPTOP NetworkManager[1023]: <error> [1381363199.282910] [vpn-manager/nm-vpn-connection.c:1534] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request.


That's weird. Do you get prompted for a password if you try to connect to a wifi network that it doesn't have a saved password for?

Does "Alt+F2 r [RETURN]" to restart the shell fix things?

Comment 2 GS 2013-10-10 15:41:42 UTC
I do not get a prompt for a password when connecting to a new network with a password. If I add the password via Network Manager, it connects but VPN still does not work.  Restarting the shell does not fix it.

tail -f /var/log/messages

Oct 10 11:34:27 Laptop NetworkManager[778]: <info> Activation (wlp3s0) starting connection 'Auto My-wireless'
Oct 10 11:34:27 Laptop NetworkManager[778]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct 10 11:34:27 Laptop NetworkManager[778]: <info> NetworkManager state is now CONNECTING
Oct 10 11:34:27 Laptop NetworkManager[778]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 10 11:34:27 Laptop NetworkManager[778]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started...
Oct 10 11:34:27 Laptop NetworkManager[778]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled...
Oct 10 11:34:27 Laptop NetworkManager[778]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete.
Oct 10 11:34:27 Laptop NetworkManager[778]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting...
Oct 10 11:34:27 Laptop NetworkManager[778]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 10 11:34:27 Laptop NetworkManager[778]: <info> Activation (wlp3s0/wireless): access point 'Auto My-wireless' has security, but secrets are required.
Oct 10 11:34:27 Laptop NetworkManager[778]: <info> (wlp3s0): device state change: config -> need-auth (reason 'none') [50 60 0]
Oct 10 11:34:27 Laptop NetworkManager[778]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete.
Oct 10 11:34:27 Laptop NetworkManager[778]: <warn> No agents were available for this request.
Oct 10 11:34:27 Laptop NetworkManager[778]: <info> (wlp3s0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Oct 10 11:34:27 Laptop NetworkManager[778]: <info> NetworkManager state is now DISCONNECTED
Oct 10 11:34:27 Laptop NetworkManager[778]: <info> Marking connection 'Auto My-wireless' invalid.
Oct 10 11:34:27 Laptop NetworkManager[778]: <warn> Activation (wlp3s0) failed for connection 'Auto My-wireless'
Oct 10 11:34:27 Laptop NetworkManager[778]: <info> (wlp3s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Oct 10 11:34:27 Laptop NetworkManager[778]: <info> (wlp3s0): deactivating device (reason 'none') [0]
Oct 10 11:34:27 Laptop firewalld: 2013-10-10 11:34:27 ERROR: UNKNOWN_INTERFACE: wlp3s0
Oct 10 11:34:27 Laptop NetworkManager[778]: <warn> (wlp3s0) firewall zone remove failed: (32) UNKNOWN_INTERFACE: wlp3s0
Oct 10 11:34:35 Laptop fprintd: ** Message: No devices in use, exit


ifconfig -a
em1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether dc:0e:a1:91:c8:c3  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 482  bytes 39076 (38.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 482  bytes 39076 (38.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp3s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet6 fe80::120b:a9ff:fe1d:1104  prefixlen 64  scopeid 0x20<link>
        ether 10:0b:a9:1d:11:04  txqueuelen 1000  (Ethernet)
        RX packets 2970  bytes 624677 (610.0 KiB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 54  bytes 8705 (8.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


lspci | grep Centrino
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)

Comment 3 Dan Winship 2013-10-10 16:14:08 UTC
What session type are you using? (GNOME, GNOME Classic, KDE, etc)

Comment 4 GS 2013-10-10 18:27:44 UTC
Cinnamon - no software rendering.

Comment 5 Dan Winship 2013-10-10 19:15:19 UTC
ok, so the answer (for now) is probably to start "nm-applet" by hand

Comment 6 GS 2013-10-10 20:53:06 UTC
I will try this and update the bug.

Comment 7 GS 2013-10-11 00:38:19 UTC
That works.  I can work with that.  Let me know if there is more data you need.

Comment 8 Fedora Update System 2013-10-28 18:46:02 UTC
network-manager-applet-0.9.9.0-7.git20131028.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/network-manager-applet-0.9.9.0-7.git20131028.fc20

Comment 9 Fedora Update System 2013-10-28 18:47:06 UTC
network-manager-applet-0.9.8.4-1.git20131028.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/network-manager-applet-0.9.8.4-1.git20131028.fc19

Comment 10 Fedora Update System 2013-10-29 03:31:37 UTC
Package network-manager-applet-0.9.8.4-1.git20131028.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing network-manager-applet-0.9.8.4-1.git20131028.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-20146/network-manager-applet-0.9.8.4-1.git20131028.fc19
then log in and leave karma (feedback).

Comment 11 Fedora Update System 2013-11-01 03:53:09 UTC
network-manager-applet-0.9.8.4-1.git20131028.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2013-11-10 07:34:57 UTC
network-manager-applet-0.9.9.0-7.git20131028.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.