Bugzilla – Bug 400458
NetworkManager and VPNC: connection failed because VPN service stopped
Last modified: 2008-09-03 10:21:52 UTC
Created attachment 222205 [details] Cisco client config file (.pcf) I was using VPN from Gnome NetworkManager in OpenSuse 10.3, and after upgrading to 11.0 RC1 it no longer works. NetworkManager pops up a windows saying: VPN Connection Failed The VPN connection "Vancouver" failed because the VPN servive stopped. VPN config file is attached. I'm using these versions of relevant packages (latest available): vpnc 0.5.1-29 (i586) NetworkManager 0.7.0.r3685-5 NetworkManager-gnome 0.7.0.r729-6 (i586) NetworkManager-glib 0.7.0.r3685-5 (i586) NetworkManager-vpnc 0.7.0.r3647-8 (i586) NetworkManager-vpnc-gnome 0.7.0.r3647-8 (i586) The following lines appear in /var/log/NetworkManager when this occurs: Jun 15 23:58:56 linux-6twq NetworkManager: <info> Starting VPN service 'org.freedesktop.NetworkManager.vpnc'... Jun 15 23:58:56 linux-6twq NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 8470 Jun 15 23:58:56 linux-6twq NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' just appeared, activating connections Jun 15 23:58:56 linux-6twq NetworkManager: <info> VPN plugin state changed: 1 Jun 15 23:58:56 linux-6twq NetworkManager: <info> VPN plugin state changed: 3 Jun 15 23:58:56 linux-6twq NetworkManager: <info> VPN connection 'Vancouver' (Connect) reply received. Jun 15 23:58:56 linux-6twq NetworkManager: <info> VPN plugin state changed: 6 Jun 15 23:58:56 linux-6twq NetworkManager: <WARN> connection_vpn_state_changed(): Could not process the request because no VPN connection was active.
I wonder if this could be related to this fix made 2008 May 2: http://www.nabble.com/NetworkManager-openvpn-td17015853.html In this discussion, Will Woods says something similar was fixed by updates to NetworkManager-{openvpn,vpnc} in the rawhide (whatever that is!) made that day, 2008 May 2. He mentions package release number svn3627, but not a bug number. I checked on the opensuse mailing list, and Andrea Jaeger says the versions of the packages I'm using contain this fix. See http://lists.opensuse.org/opensuse/2008-06/msg01215.html So I think this must not be exactly the same bug that Will Woods fixed, but given that it exhibits the same symptom, it may be related.
Created attachment 222945 [details] the latest NetworkManager-vpnc
Created attachment 222946 [details] the latest NetworkManager-vpnc-gnome
Greg, I think this bug should be already fixed, would mind try the Comment#2 and Comment#3 packages? If any problem, feel free contact me.
BTW, if you use the command 'vpnc' connecting the Server, does it works fine?
Created attachment 223250 [details] VPNC configuration file
I re-installed using 11.0-final. Now I have these versions: vpnc 0.5.1-20.1 NetworkManager-vpnc 0.7.0.r3647-9.1 (i586) NetworkManager-vpnc-gnome 0.7.0.r3647-9.1 (i586) Now the behavior is a little different. The NetworkManager log says: Jun 19 22:22:47 SJ-L-01-GHOLMB NetworkManager: <info> Starting VPN service 'org.freedesktop.NetworkManager.vpnc'... Jun 19 22:22:47 SJ-L-01-GHOLMB NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 19129 Jun 19 22:22:52 SJ-L-01-GHOLMB NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' did not start in time, cancelling connections Yes, if I use the command "vpnc" with the .conf file attached, the connection succeeds (as root, of course). I see the versions of the packages you have attached are 0.7.0.r3647-12, so newer than the ones in 11.0-final. I tried to install them but the RPM installer failed, showing many missing dependencies. This might be because the attachments were built for x86_64, while I'm running the i386 version of opensuse. I can see how you might have thought I was runnng x86_64 opensuse, since I entered that in the "hardware" field. I was a little confused about this field. I do in fact have x86_64 hardware (Intel Core2 Duo). There should be another field that asks what hardware the component and OS were *built for*, as opposed to what they are running on. In any case, if you attach i386 32-bit versions of the VPNC components, I will try them.
Greg, I'd thought you running a x86_64 platform, sorry about it. And the packages you installed should be ok, it's the same version. Now I wanna make sure something: 1) Do you see the password dialog when you connect the VPN server? 2) if not, please kill the NetworkManager and run 'NetworkManager --no-daemon' in root user so that we can get more information. 3) export your NetworkManager's VPN configuration, just 'gconftool-2 -R /system/networking/connections'.
1) No I do not. 2) If I do that it fails again, and displays no password dialog. However, if I now make a new vpn connection, it does show a password dialog and now it works ------------- From when it fails embla:~ # NetworkManager --no-daemon NetworkManager: <info> starting... RTNETLINK answers: File exists NetworkManager: <info> eth0: Device is fully-supported using driver 'r8169'. NetworkManager: <info> Found new Ethernet device 'eth0'. NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_11_09_cc_b8_ff NetworkManager: <info> wlan0: Device is fully-supported using driver 'rt2500pci'. NetworkManager: <info> wlan0: driver supports SSID scans (scan_capa 0x01). NetworkManager: <info> Found new wireless (802.11) device 'wlan0'. NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_11_09_bf_5b_76 NetworkManager: <info> Trying to start the system settings daemon... NetworkManager: <info> (eth0): device state change: 1 -> 2 NetworkManager: <info> (eth0): bringing up device. NetworkManager: <info> (eth0): preparing device. NetworkManager: <info> (eth0): deactivating device. Nothing to flush. Nothing to flush. NetworkManager: <info> (eth0): carrier now ON (device state 2) NetworkManager: <info> (eth0): device state change: 2 -> 3 NetworkManager: <info> (wlan0): device state change: 1 -> 2 NetworkManager: <info> (wlan0): bringing up device. NetworkManager: <info> (wlan0): preparing device. NetworkManager: <info> (wlan0): deactivating device. Nothing to flush. Nothing to flush. NetworkManager: <info> Activation (eth0) starting connection 'Automatisk Ethernet' NetworkManager: <info> (eth0): device state change: 3 -> 4 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: <info> (wlan0): device state change: 2 -> 3 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: <info> (wlan0): supplicant interface state change: 1 -> 2. NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... NetworkManager: <info> (eth0): device state change: 4 -> 5 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... NetworkManager: <info> (eth0): device state change: 5 -> 7 NetworkManager: <info> Activation (eth0) Beginning DHCP transaction. Internet Systems Consortium DHCP Client V3.0.6 Copyright 2004-2007 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ wmaster0: unknown hardware address type 801 NetworkManager: <info> dhclient started with pid 3986 wmaster0: unknown hardware address type 801 Listening on LPF/eth0/00:11:09:cc:b8:ff Sending on LPF/eth0/00:11:09:cc:b8:ff Sending on Socket/fallback NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. NetworkManager: <info> DHCP: device eth0 state changed (null) -> preinit DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 DHCPOFFER from 192.168.2.1 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.2.1 NetworkManager: <info> DHCP: device eth0 state changed preinit -> bound NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started... NetworkManager: <info> address 192.168.2.2 NetworkManager: <info> netmask 255.255.255.0 NetworkManager: <info> gateway 192.168.2.1 NetworkManager: <info> nameserver '192.168.2.1' NetworkManager: <info> nameserver '217.68.109.10' NetworkManager: <info> nameserver '62.65.30.10' NetworkManager: <info> domain name 'Belkin' NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete. NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... bound to 192.168.2.2 -- renewal in 1744 seconds. NetworkManager: <info> (eth0): device state change: 7 -> 8 NetworkManager: <info> Clearing nscd hosts cache. NetworkManager: <info> Policy set (eth0) as default device for routing and DNS. NetworkManager: <info> Activation (eth0) successful, device activated. NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. NetworkManager: <info> Starting VPN service 'org.freedesktop.NetworkManager.vpnc'... NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 4036 NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' just appeared, activating connections NetworkManager: <info> VPN plugin state changed: 1 NetworkManager: <info> VPN plugin state changed: 3 ** Message: <info> vpnc started with pid 4041 /usr/sbin/vpnc: warning: unknown configuration directive in stdin at line 2 /usr/sbin/vpnc: warning: unknown configuration directive in stdin at line 3 /usr/sbin/vpnc: warning: unknown configuration directive in stdin at line 4 /usr/sbin/vpnc: warning: unknown configuration directive in stdin at line 11 NetworkManager: <info> VPN connection 'Jobb VPN' (Connect) reply received. /usr/sbin/vpnc: hash comparison failed: (ISAKMP_N_AUTHENTICATION_FAILED)(24) check group password! ** (process:4036): WARNING **: <WARN> vpnc_watch_cb(): vpnc exited with error code 2 NetworkManager: <info> VPN plugin state changed: 6 NetworkManager: <WARN> connection_vpn_state_changed(): Could not process the request because no VPN connection was active. NetworkManager: <info> Trying to start the system settings daemon... ------------ If you need the info from when it works (and 3) set need info again
Note If I log in as root (gui) it works from the get go, password dialog and all. Does this mean this is policykit related?
Bjørn, You said displays no password dialog, so do you use the gnome-keyring saving the password?
I use whatever the default one is called yes. Sorry for the late reply, I must have missed the email
So it's related to the gnome-keyring, I'll try to reproduce this bug, and reply you later.
-> Upstream.