Description of problem: Connecting to a vpn, in wireless, fails. Version-Release number of selected component (if applicable): Fedora 8. RPMs: NetworkManager-0.7.0-0.6.6.svn3109.fc8 NetworkManager-openvpn-0.7.0-2.svn3047.fc8 NetworkManager-glib-0.7.0-0.5.svn3030.fc8 NetworkManager-glib-0.7.0-0.6.6.svn3109.fc8 NetworkManager-gnome-0.7.0-0.6.6.svn3109.fc8 NetworkManager-vpnc-0.7.0-0.4.svn3030.fc8 How reproducible: Updated to most current released fedora 8. Steps to Reproduce: 1. Disconnect enhernet cord. 2. Connect to wireless access 3. select VPN from Network Manager 4) See bug report. Additional info: Bug report is attached.
Created attachment 276181 [details] Bug Report
Could you first try to connect manually with the vpnc command ? It's very simple, usually something like vpnc --gateway vpn.foo.com --id group_name --username yourusername This to make sure this is indeed a NM-vpnc problem rather than a vpnc one. Also, seeing the bug report, could you give me the content of gconftool-2 -R /system/networking/connections/1 (assuming 1 is indeed the number of the right connectino directory, it should have a vpn and vpn-properties directory). thanks :-)
Running vpnc manually works here. Trying to connect to the VPN with NM-vpnc crashes nm-applet here. With a freshly run nm-applet I don't get messages in .xsession-errors, but one in /var/log/messages: Dec 4 13:46:43 gibraltar NetworkManager: nm-vpn-connection.c.661: NeedSecrets failed: g-exec-error-quark Could not process the request because the VPN connection settings were invalid. This only happened after I updated to NetworkManager-0.7.0-0.6.6.svn3109.fc8.
Yowza!! You need to also update to NetworkManager-vpnc svn3109. The person who pushed NM 3109 to stable forgot to also push NM-vpnc 3109. I just pushed it to stable, but for the time being you can download it from testing.
I was able to run vpnc from my machine, and was able to reprouce the bug by just getting the connection information from the NM applet.
nils@gibraltar:~> rpm -qa NetworkManager\* NetworkManager-gnome-0.7.0-0.6.6.svn3109.fc8 NetworkManager-0.7.0-0.6.6.svn3109.fc8 NetworkManager-glib-0.7.0-0.6.6.svn3109.fc8 NetworkManager-vpnc-0.7.0-0.6.3.svn3109.fc8 This was logged in /var/log/messages when I tried to start a newly configured VPN connection: Dec 4 14:16:44 gibraltar NetworkManager: nm-vpn-connection.c.661: NeedSecrets failed: g-exec-error-quark Could not process the request because the VPN connection settings were invalid. Dec 4 14:16:44 gibraltar NetworkManager: <info> Deactivating device eth0. Dec 4 14:16:44 gibraltar NetworkManager: <info> eth0: canceled DHCP transaction, dhclient pid 9616 Dec 4 14:16:44 gibraltar avahi-daemon[2519]: Withdrawing address record for 192.168.195.119 on eth0. Dec 4 14:16:44 gibraltar avahi-daemon[2519]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.195.119. Dec 4 14:16:44 gibraltar avahi-daemon[2519]: Interface eth0.IPv4 no longer relevant for mDNS. Dec 4 14:16:44 gibraltar avahi-daemon[2519]: Withdrawing address record for fe80::21c:23ff:fea5:1165 on eth0.
I have also updated to the "released" updates version of packages and began to experience the crashing of nm-applet. I grabbed the NetworkManager-vpnc from updates-testing and now match Nils and still have nm-applet crashing when I try to establish a vpnc connection.
Just for the record, nm-applet crashes with me as well.
nm-applet is part of NetworkManager. Reassigning. Also, please verify the bug with all svn3109 versions. For the record, it works for me no problem here on f-8: NetworkManager-0.7.0-0.6.6.svn3109.fc8 NetworkManager-glib-devel-0.7.0-0.6.6.svn3109.fc8 NetworkManager-devel-0.7.0-0.6.6.svn3109.fc8 NetworkManager-glib-0.7.0-0.6.6.svn3109.fc8 NetworkManager-gnome-0.7.0-0.6.6.svn3109.fc8 NetworkManager-vpnc-0.7.0-0.6.3.svn3109.fc8
(In reply to comment #9) > Also, please verify the bug with all svn3109 versions. As per comment #6, it seems I've done that already ;-).
jkeating and I debugged this last night. It's valid and we'll issue an update to correct the problem. The vpnc plugin may _not_ need to be updated; it may be isolated to NM itself (libnm-util really).
*** Bug 410371 has been marked as a duplicate of this bug. ***
*** Bug 395141 has been marked as a duplicate of this bug. ***
*** Bug 411411 has been marked as a duplicate of this bug. ***
*** Bug 411561 has been marked as a duplicate of this bug. ***
Same error with: NetworkManager-glib-0.7.0-0.6.6.svn3134.fc8 \ NetworkManager-gnome-0.7.0-0.6.6.svn3134.fc8 > from Koji NetworkManager-0.7.0-0.6.6.svn3134.fc8 / NetworkManager-vpnc-0.7.0-0.6.3.svn3109.fc8
Same here, also with rebuild NM-vpnc with svn3134. I'm able to edit the vpn properties, but trying to connect still crashes nm-applet.
Created attachment 278511 [details] nm-vpn-properties bug report
After the latest upgrade to NetworkManager I also experience problem connecting with vpnc. The applet doesn't crash but I get the same syslog messages that the settings are invalid. I then started the nm-vpm-properties program, deleted the connection and created a new one but the program crashed after I pressed apply. I attached the bug report above.
*** Bug 412471 has been marked as a duplicate of this bug. ***
133t h0t bitz: http://koji.fedoraproject.org/koji/taskinfo?taskID=276538 If everyone could try it out and report back. If the VPN connection you want isn't shown in the menu, please choose the "Configure VPN..." option and update the connection details through the VPN connection editor applet.
I just installed these rpm's, and they don't fix my problem. When I try to connect to the vpn via NetworkManager, the applet no longer crashes. But, it doesn't connect either--nothing happens. Also, when I go to edit a vpn connection, the preferences dialog box crashes.
You'll need to restart NetworkManager and pkill the applet, then start the applet again. Or reboot. Did you do either of those?
I rebooted before trying this--it didn't work after reboot.
Same - with updated pkgs from koji: ** (nm-applet:24501): WARNING **: nm_object_get_property: Error getting 'Name' for /org/freedesktop/NetworkManager/VPN/Connection/0: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist ** (nm-applet:24501): WARNING **: nm_object_get_property: Error getting 'Name' for /org/freedesktop/NetworkManager/VPN/Connection/0: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist ** (nm-applet:24501): CRITICAL **: add_one_vpn_connection: assertion `name != NULL' failed
@bche: can you get a backtrace of the VPN properties applet? it's going to be "nm-vpn-properties". Please install both the NetworkManager-debuginfo and the NetworkManager-vpnc-debuginfo. @dan poler: can you try editing the connection from the VPN properties applet? That should fix up that problem.
@dcbw: Hitting "Configure" in nm-vpn-properties causes it to crash.
@dan poler: you mean choosing Configure VPN..., letting the VPN properties applet run, selecting the VPN connection you want to edit, and clicking the "Edit.." button on the right side of the window? Could you report the version of NetworkManager-vpnc that you are using? If you don't hae at least NetworkManager-vpnc-0.7.0.svn3109 please update to the latest in updates-testing.
*** Bug 412791 has been marked as a duplicate of this bug. ***
@dcbw: behavior is exactly as you described, yes. Will update NetworkManager-vpnc and try again later on.
With following modules NetworkManager-gnome-0.7.0-0.6.6.svn3138.fc8 NetworkManager-vpnc-0.7.0-0.6.3.svn3109.fc8 NetworkManager-glib-0.7.0-0.6.6.svn3138.fc8 NetworkManager-0.7.0-0.6.6.svn3138.fc8 I am now able to start VPN a first time but after I disconnect I cannot reconnect using the same VPN.
@didier g: reconnecting works for me here; can you post some NetworkManager log output from /var/log/messages about what happens when it fails?
That is what happen when I have problem to reconnect : Dec 5 23:24:05 qwerty NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' exec scheduled... Dec 5 23:24:05 qwerty NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' executed (org.freedesktop.NetworkManager.vpnc), PID 6680 Dec 5 23:24:06 qwerty NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' just appeared, activating connections Dec 5 23:24:06 qwerty NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' just appeared, activating connections Dec 5 23:24:06 qwerty NetworkManager: nm_vpn_connection_activate: assertion `nm_vpn_connection_get_state (connection) == NM_VPN_CONNECTION_STATE_PREPARE' failed Dec 5 23:24:06 qwerty NetworkManager: <info> VPN connection 'vpn.qwerty' (Connect) reply received. Dec 5 23:24:06 qwerty kernel: tun0: Disabled Privacy Extensions Dec 5 23:24:07 qwerty NetworkManager: <WARN> connection_state_changed(): Could not process the request because no VPN connection was active.
Dan, works here now, and without recompiling NM-vpnc. The reconnection problem is another bug (332821), and the behavior hasn't changed there.
With: NetworkManager-0.7.0-0.6.6.svn3138.fc8 NetworkManager-glib-0.7.0-0.6.6.svn3138.fc8 NetworkManager-gnome-0.7.0-0.6.6.svn3138.fc8 NetworkManager-vpnc-0.7.0-0.4.svn3030.fc8 I restarted the daemon as well as the applet. When trying to start freshly configured VPN connection, I don't get any reaction from the applet (no "lock" throbber, no password questions) and the following in /var/log/messages: Dec 6 12:57:08 gibraltar NetworkManager: nm-vpn-connection.c.661: NeedSecrets failed: g-exec-error-quark Could not process the request because the VPN connection settings were invalid.
@nils, bche: Can you try to update to: https://admin.fedoraproject.org/updates/F8/FEDORA-2007-3839 I had thought this was already pushed to stable. Yes, we do need to be a lot better about updating the VPN plugins and NM in sync. After installing this (make sure nm-vpnc-service is killed, but you don't need to restart), edit the connection again to ensure that it's OK and then try to restart the VPN.
Largely works for me with NetworkManager-vpnc-0.7.0-0.6.3.svn3109.fc8. One minor nit, the icon sometimes seems a bit confused: at one occasion I started a VPN connection, then the icon went "not connected" even though clicking on it showed that a wired LAN connection and a VPN connection were active.
I have the same issue as #37 after updating to the same RPM versions. I can successfully add a VPN connection and connect, but the icon never shows the padlock like it would in NM 0.6.5.
After installing https://admin.fedoraproject.org/updates/F8/FEDORA-2007-3839, I am able to connect to the vpn.
I'm also having issues with vpnc after upgrading to 0.7.0-0.6.6.svn3109.fc8. I currently have: NetworkManager-0.7.0-0.6.6.svn3109.fc8.i386 NetworkManager-0.7.0-0.6.6.svn3109.fc8.x86_64 NetworkManager-glib-0.7.0-0.6.6.svn3109.fc8.i386 NetworkManager-glib-0.7.0-0.6.6.svn3109.fc8.x86_64 NetworkManager-gnome-0.7.0-0.6.6.svn3109.fc8.x86_64 NetworkManager-openvpn-0.7.0-2.svn3047.fc8.i386 NetworkManager-openvpn-0.7.0-2.svn3047.fc8.x86_64 NetworkManager-vpnc-0.7.0-0.6.3.svn3109.fc8.i386 NetworkManager-vpnc-0.7.0-0.6.3.svn3109.fc8.x86_64 The openvpn packages are older, but I'm not using openvpn, so hopefully that doesn't matter. If I launch 'nm-applet' from a terminal and try to make a vpnc connection, I see this in the terminal: ** (nm-applet:4039): WARNING **: nm_object_get_property: Error getting 'Name' for /org/freedesktop/NetworkManager/VPN/Connection/4: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist ** (nm-applet:4039): WARNING **: nm_object_get_property: Error getting 'Name' for /org/freedesktop/NetworkManager/VPN/Connection/4: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist And this appears in /var/log/messages: Dec 6 10:29:33 tarantula NetworkManager: nm-vpn-connection.c.661: NeedSecrets failed: g-exec-error-quark Could not process the request because the VPN connection settings were invalid. And then nm-applet crashes. After restarting nm-applet, I tried to edit my vpnc settings and got this: ** ERROR **: file nm-vpnc.c: line 288 (impl_get_widget): assertion failed: (s_vpn_props) aborting...
Created attachment 279951 [details] crash report from editing vpnc settings I removed the i386 packages from my system and installed the debuginfo packages for NetworkManager and NetworkManager-vpnc. I captured two crash reports. This is from trying to edit my vpnc settings.
Created attachment 279971 [details] crash report from trying to make vpnc connection This crash report is from actually trying to make a vpnc connection. The first attempt to connect fails, but nm-applet does not crash. The second attempt to connect causes nm-applet to crash and generated this report.
Created attachment 280011 [details] crash report from editing vpnc settings (take 2) I installled the glib2, gtk2, and glibc debuginfo packages to get more detailed backtraces. Here is a new backtrace from trying to edit my vpnc settings.
Created attachment 280021 [details] crash report from trying to make vpnc connection (take 2) And here is a more detailed backtrace from trying to make a vpnc connection.
jbastian: can you try to install the RPMs from here: http://koji.fedoraproject.org/koji/taskinfo?taskID=276538 and from here for NetworkManager-vpnc: https://admin.fedoraproject.org/updates/F8/FEDORA-2007-3839 and report how that works out?
Ahh, that's much better! I can make vpnc connections now! Thank you! I now have: NetworkManager-0.7.0-0.6.6.svn3138.fc8.x86_64 NetworkManager-debuginfo-0.7.0-0.6.6.svn3138.fc8.x86_64 NetworkManager-glib-0.7.0-0.6.6.svn3138.fc8.x86_64 NetworkManager-gnome-0.7.0-0.6.6.svn3138.fc8.x86_64 NetworkManager-openvpn-0.7.0-2.svn3047.fc8.x86_64 NetworkManager-vpnc-0.7.0-0.6.3.svn3109.fc8.x86_64 NetworkManager-vpnc-debuginfo-0.7.0-0.6.3.svn3109.fc8.x86_64
(And I can edit my vpnc settings, too.)
*** Bug 414401 has been marked as a duplicate of this bug. ***
*** Bug 415171 has been marked as a duplicate of this bug. ***
It seems that NetworkManager-vpnc is bogusly called... If I run NetworkManager and I ask a VPNc connection I obtain: -- NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' exec scheduled... NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' executed (org.freedesktop.NetworkManager.vpnc), PID 2900 kernel: tun: Universal TUN/TAP device driver, 1.6 kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk> NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' just appeared, activating connections NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' just appeared, activating connections NetworkManager: nm_vpn_connection_activate: assertion `nm_vpn_connection_get_state (connection) == NM_VPN_CONNECTION_STATE_PREPARE' failed NetworkManager: <info> VPN connection 'Red Hat Surrey' (Connect) reply received. kernel: tun0: Disabled Privacy Extensions NetworkManager: <WARN> connection_state_changed(): Could not process the request because no VPN connection was active. -- However if I run it by hand: /usr/libexec/nm-vpnc-auth-dialog -n rh-vpn -s org.freedesktop.NetworkManager.vpnc It just works (tm) -- ** (nm-vpnc-auth-dialog:4624): WARNING **: couldn't communicate with gnome keyring daemon via dbus: The name org.gnome.keyring was not provided by any .service files ** (nm-vpnc-auth-dialog:4624): WARNING **: couldn't communicate with gnome keyring daemon via dbus: The name org.gnome.keyring was not provided by any .service files ** (nm-vpnc-auth-dialog:4624): WARNING **: couldn't communicate with gnome keyring daemon via dbus: The name org.gnome.keyring was not provided by any .service files ** (nm-vpnc-auth-dialog:4624): WARNING **: couldn't communicate with gnome keyring daemon via dbus: The name org.gnome.keyring was not provided by any .service files IPSec secret <secret> Xauth password <my password> -- Is this something related to the issue? Shall I fill a new bug? Anyone have seen it? Chris.
Created attachment 281511 [details] Bug report after trying to edit settings
Clicking on the desired connection has no effect when trying to connect for me.
NetworkManager-0.7.0-0.6.6.svn3138.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update NetworkManager'
Works for me after reboot.
Created attachment 282001 [details] Bug report for attempt after reboot
I rebooted, deleted my old connection, and then attempted to add it back. I am getting a crash when I restart. Attached is the bug report.
Doesn't work for me. [root@localhost ~]# rpm -qa Network\* NetworkManager-glib-0.7.0-0.6.6.svn3109.fc8 NetworkManager-gnome-0.7.0-0.6.6.svn3109.fc8 NetworkManager-glib-devel-0.7.0-0.6.6.svn3109.fc8 NetworkManager-devel-0.7.0-0.6.6.svn3109.fc8 NetworkManager-openvpn-0.7.0-2.svn3047.fc8 NetworkManager-0.7.0-0.6.6.svn3109.fc8 NetworkManager-vpnc-0.7.0-0.4.svn3030.fc8 [root@localhost ~]# yum --enablerepo=updates-testing update NetworkManager Setting up Update Process Could not find update match for NetworkManager No Packages marked for Update
You're probably in "mirror hell". Try a yum clean all first. Rinse and repeat if necessary.
I should say, it works after: yum clean all yum --enablerepo=updates-testing update NetworkManager then a reboot.
NetworkManager-0.7.0-0.6.6.svn3138.fc8 appears to have fixed it for me too.
I can say that I'm getting the same thing as comment #50. yum --enablerepo updates-testing update NetworkManager Networkmanager-vpnc [root@localhost ~]# rpm -qa NetworkManager\* NetworkManager-openvpn-0.7.0-2.svn3047.fc8 NetworkManager-vpnc-0.7.0-0.6.3.svn3109.fc8 NetworkManager-glib-0.7.0-0.6.6.svn3138.fc8 NetworkManager-gnome-0.7.0-0.6.6.svn3138.fc8 NetworkManager-0.7.0-0.6.6.svn3138.fc8 I rebooted, deleted my old vpn connection and created a new one. Tried to run it the first time tt as me for my password and group password. I entered them and told it to save them both to the keyring. I saw the icon act like it was connecting momentarily and then nothing. Looking in /var/log/messages I have the exact same message as comment #50 Dec 10 12:43:43 localhost NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' exec scheduled... Dec 10 12:43:43 localhost NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' executed (org.freedesktop.NetworkManager.vpnc), PID 5947 Dec 10 12:43:43 localhost NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' just appeared, activating connections Dec 10 12:43:43 localhost NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' just appeared, activating connections Dec 10 12:43:43 localhost NetworkManager: nm_vpn_connection_activate: assertion `nm_vpn_connection_get_state (connection) == NM_VPN_CONNECTION_STATE_PREPARE' failed Dec 10 12:43:43 localhost NetworkManager: <info> VPN connection 'RedHat' (Connect) reply received. Dec 10 12:43:43 localhost kernel: tun1: Disabled Privacy Extensions Dec 10 12:43:43 localhost NetworkManager: <WARN> connection_state_changed(): Could not process the request because no VPN connection was active. Since we are not crashing any more maybe this bug is solved, should myself and that reporter move to a new bug for this failure to work?
FWIW: # rpm -qa NetworkManager\* NetworkManager-0.7.0-0.6.6.svn3138.fc8 NetworkManager-vpnc-0.7.0-0.6.3.svn3109.fc8 NetworkManager-glib-0.7.0-0.6.6.svn3138.fc8 NetworkManager-gnome-0.7.0-0.6.6.svn3138.fc8 solves the problem for me. First connect attempt failed though (I had also removed all the passwords from the keyring) after I entered the passwords lise such: <WARN> connection_state_changed(): Could not process the request becaus e no VPN connection was active. But subsequent attempts work just fine (don't know if I was just too slow to enter the passwords)
NetworkManager-0.7.0-0.6.6.svn3138.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.