Hide Forgot
Description of problem: VPN connections used to work rather well for me with NetworkManager. With F15 however, something broke. I'm using nm-applet. The VPN connections are available in the context menu, but when I choose (click) one, there is only a short indication of connection-making by an animated icon, then it turn back to the standard icon. No connection was made, no error message by the notification daemon. Dmesg has the following though: [37806.617575] NetworkManager[2352]: <info> Starting VPN service 'vpnc'... [37806.624654] NetworkManager[2352]: <info> VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 2462 [37806.700086] NetworkManager[2352]: <info> VPN service 'vpnc' appeared; activating connections [37806.709458] NetworkManager[2352]: <info> VPN plugin state changed: 1 [37807.082304] NetworkManager[2352]: <info> VPN plugin state changed: 3 [37807.082401] NetworkManager[2352]: <info> VPN connection 'VPN RWTH (Full tunnel)' (Connect) reply received. [37807.082431] NetworkManager[2352]: <warn> VPN connection 'VPN RWTH (Full tunnel)' failed to connect: 'No VPN secrets!'. [37807.083652] NetworkManager[2352]: <warn> error disconnecting VPN: Could not process the request because no VPN connection was active. [37807.084545] NetworkManager[2352]: <info> Policy set 'Auto Fritz!Box Eva' (wlan0) as default for IPv4 routing and DNS. [37812.007777] NetworkManager[2352]: <info> VPN service 'vpnc' disappeared I don't get the "no vpn secrets" message. It appears that the vpn login data is still there, and it did work before. No idea if it can be related to #699786. Anyway, I tried the update without luck.
Well, after a reboot it appears to be working now.. I'll keep an eye on it.
I'm receiving the same behavior. Using plane networkManager-vpnc: NetworkManager-openvpn-0.8.999-1.fc15.x86_64 vpnc-script-0.5.3-9.fc15.noarch vpnc-0.5.3-9.fc15.x86_64 openvpn-2.1.4-1.fc15.x86_64 NetworkManager-vpnc-0.8.999-2.fc15.x86_64 When I try and connect I see this: Jun 6 10:29:50 raykj NetworkManager[1173]: <info> VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 9144 Jun 6 10:29:50 raykj kernel: [ 3754.236390] tun: Universal TUN/TAP device driver, 1.6 Jun 6 10:29:50 raykj kernel: [ 3754.236392] tun: (C) 1999-2004 Max Krasnyansky <maxk> Jun 6 10:29:50 raykj NetworkManager[1173]: <info> VPN service 'vpnc' appeared; activating connections Jun 6 10:29:50 raykj NetworkManager[1173]: <info> VPN plugin state changed: 1 Jun 6 10:29:52 raykj NetworkManager[1173]: <info> VPN plugin state changed: 3 Jun 6 10:29:52 raykj NetworkManager[1173]: <info> VPN connection 'xxxx xxx' (Connect) reply received. Jun 6 10:29:52 raykj NetworkManager[1173]: <warn> VPN connection 'xxxx xxx' failed to connect: 'No VPN secrets!'. Jun 6 10:29:52 raykj NetworkManager[1173]: <warn> error disconnecting VPN: Could not process the request because no VPN connection was active. Jun 6 10:29:52 raykj NetworkManager[1173]: <info> Policy set 'System eth0' (eth0) as default for IPv4 routing and DNS. Jun 6 10:29:57 raykj NetworkManager[1173]: <info> VPN service 'vpnc' disappeared I can re-create the VPN setting through the network manager and it works ONCE, but after I disconnect, I can not reconnect without re-creating the VPN profile.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping