I am trying to connect to my VPN network using vpnc and the network manager. Unfortunately this has no effect. The only thing I obtain is the following in /var/log/messages May 9 14:03:49 toaster NetworkManager[6879]: <warn> connection /org/freedesktop/NetworkManager/Settings/1 failed to activate: (5) Base connection for VPN connection not active How to reproduce: 1) start pc 2) login (in my case kde) 3) go to network manager 4) connect to wlan (vpn connections appear) 5) connect to vpnc obtained effect, nothing connecting as root using the command line works (i.e. using "vpnc") The connection worked without a problem in F14. In F15 this is not the case any more. version number: NetworkManager-vpnc-0.8.999-2.fc15.x86_64 kde-plasma-networkmanagement-vpnc-0.9-0.47.20110323.fc15.x86_64
$ killall -TERM nm-vpnc-service nm-vpnc-service: no process found $ VPNC_DEBUG=1 /usr/libexec/nm-vpnc-service this gives no information at all
Same problem for me. Connecting via vpnc with NetworkManager works in Gnome3 but not in KDE 4.6.2 (both F15). /var/log/messages show the same message
me three
The total lack of feedback when clicking the VPN connection in the network management widget is pretty unimpressive. I wasn't even sure that's how I was meant to connect until I su'd to root and realised there was a new line in /var/log/messages every time I clicked it.
Same here (i386), a real pitta!
Identical troubles with openVPN connections. Gnome3-NetworkManager works, KDE reports: NetworkManager[1080]: <warn> connection /org/freedesktop/NetworkManager/Settings/0 failed to activate: (5) Base connection for VPN connection not active.
Same message for PPTP, also running KDE. No feedback in the gui of any attempts to connect.
the same for me F15 x86_64 KDE 4.6.3 pptp
F15 x86_64 KDE on connect to vpn, put in /var/log/messages: <warn> connection /org/freedesktop/NetworkManager/Settings/0 failed to activate: (5) Base connection for VPN connection not active. in Gnome 3 work correct. Sorry for my bad English.
Confirmed on F15 x86_64 with openvpn. May 27 16:32:23 asdasd NetworkManager[816]: <warn> connection /org/freedesktop/NetworkManager/Settings/2 failed to activate: (5) Base connection for VPN connection not active. May 27 16:32:23 asdasd NetworkManager[816]: <warn> connection /org/freedesktop/NetworkManager/Settings/2 failed to activate: (5) Base connection for VPN connection not active
Fixed in the latest update NetworkManager-0.8.999-3.git20110526.fc15.x86_64 I think we can close this bug! thanks
Latest update (NetworkManager 0.8.999-3.git20110526) fixed the problem. Unfortunately, it also opens a security hole with a log record: NetworkManager[1059]: destroy_one_secret: destroying ***real_password_here*** The password is related to my x509 OpenVPN keys. I would suggest you to not use the update. On the other hand, #703136 was fixed.
After the upgrade, I no longer get the "Base connection" error, but the VPN still doesn't work. /var/log/messages has this: May 28 22:41:47 sepiroth NetworkManager[788]: <info> Starting VPN service 'openvpn'... May 28 22:41:47 sepiroth NetworkManager[788]: <info> VPN service 'openvpn' started (org.freedesktop.NetworkManager.openvpn), PID 7442 May 28 22:41:48 sepiroth kernel: [21333.384853] tun: Universal TUN/TAP device driver, 1.6 May 28 22:41:48 sepiroth kernel: [21333.384856] tun: (C) 1999-2004 Max Krasnyansky <maxk> May 28 22:41:48 sepiroth NetworkManager[788]: <info> VPN service 'openvpn' appeared; activating connections May 28 22:41:48 sepiroth NetworkManager[788]: <info> VPN plugin state changed: 1 May 28 22:41:48 sepiroth NetworkManager[788]: <info> Policy set 'tempest' (wlan0) as default for IPv4 routing and DNS. May 28 22:41:53 sepiroth NetworkManager[788]: <info> VPN service 'openvpn' disappeared
This bug is fixed for me with NetworkManager 0.8.999, and VPN is working with none of the problems reported above. I also vote that bug can be closed.
I can confirm the security leak mentioned by Leo. Networkmanager is now putting way to much info in the log files.
the security leak is mentioned in bug 708583.
Oded, I think the problems you encounter are related to a different bug unrelated to this issue now. I think you should file a new bug.
As none of the admins closes this bug, I will close it myself. Open if needed.