Description of problem: Starting sometime in the last few days, I can no longer connect to a VPN concentrator using either OpenVPN or vpnc protocols. Both of these VPN configurations work properly if I switch to the GNOME 3 desktop, so it's not a configuration error. Also, they both previously worked from KDE. Version-Release number of selected component (if applicable): kde-plasma-networkmanagement-0.9.0.5-2.fc18.x86_64 How reproducible: Every time Steps to Reproduce: 1. Configure an OpenVPN or vpnc connection in NetworkManager (I originally configured these from GNOME 3 before I switched to KDE, but they worked just fine until recently). The configuration should require entering a password at connection time (e.g. using an OTP or personal password) 2. Click on the VPN from the Plasma widget. Actual results: VPN connection fails for either prototocol (maybe others as well, but those are the two I can test). I am never prompted for the password. Expected results: The user should be prompted for the connection password and the VPN should be established when the proper password is given. Additional info: OpenVPN: Nov 30 10:54:17 sgallagh520 NetworkManager[9219]: <info> Starting VPN service 'openvpn'... Nov 30 10:54:17 sgallagh520 NetworkManager[9219]: <info> VPN service 'openvpn' started (org.freedesktop.NetworkManager.openvpn), PID 9424 Nov 30 10:54:17 sgallagh520 NetworkManager[9219]: <info> VPN service 'openvpn' appeared; activating connections Nov 30 10:54:23 sgallagh520 NetworkManager[9219]: <info> VPN plugin state changed: starting (3) Nov 30 10:54:23 sgallagh520 NetworkManager[9219]: <info> VPN connection 'Red Hat OpenVPN' (Connect) reply received. Nov 30 10:54:23 sgallagh520 nm-openvpn[9428]: OpenVPN 2.2.2 x86_64-redhat-linux-gnu [SSL] [LZO2] [EPOLL] [PKCS11] [eurephia] built on Sep 26 2012 Nov 30 10:54:24 sgallagh520 nm-openvpn[9428]: WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page). Nov 30 10:54:24 sgallagh520 nm-openvpn[9428]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Nov 30 10:54:24 sgallagh520 nm-openvpn[9428]: UDPv4 link local: [undef] Nov 30 10:54:24 sgallagh520 nm-openvpn[9428]: UDPv4 link remote: 209.132.183.3:443 Nov 30 10:54:25 sgallagh520 nm-openvpn[9428]: [ovpn-phx2.redhat.com] Peer Connection Initiated with 209.132.183.3:443 Nov 30 10:54:27 sgallagh520 nm-openvpn[9428]: AUTH: Received AUTH_FAILED control message Nov 30 10:54:27 sgallagh520 NetworkManager[9219]: <warn> VPN plugin failed: 0 Nov 30 10:54:27 sgallagh520 NetworkManager[9219]: <info> VPN plugin state changed: stopped (6) Nov 30 10:54:27 sgallagh520 NetworkManager[9219]: <info> VPN plugin state change reason: 10 Nov 30 10:54:27 sgallagh520 nm-openvpn[9428]: SIGTERM[soft,auth-failure] received, process exiting Nov 30 10:54:27 sgallagh520 NetworkManager[9219]: <info> Policy set 'burke-wep' (wlan0) as default for IPv4 routing and DNS. Nov 30 10:54:27 sgallagh520 NetworkManager[9219]: <warn> error disconnecting VPN: Could not process the request because no VPN connection was active. Nov 30 10:54:32 sgallagh520 NetworkManager[9219]: <info> VPN service 'openvpn' disappeared VPNC: Nov 30 10:55:13 sgallagh520 NetworkManager[9219]: <info> Starting VPN service 'vpnc'... Nov 30 10:55:13 sgallagh520 NetworkManager[9219]: <info> VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 9448 Nov 30 10:55:13 sgallagh520 NetworkManager[9219]: <info> VPN service 'vpnc' appeared; activating connections Nov 30 10:55:13 sgallagh520 NetworkManager[9219]: <info> VPN plugin state changed: starting (3) Nov 30 10:55:13 sgallagh520 NetworkManager[9219]: <info> VPN connection 'VPNC (RDU)' (Connect) reply received. Nov 30 10:55:13 sgallagh520 NetworkManager[9219]: <warn> /sys/devices/virtual/net/tun0: couldn't determine device driver; ignoring... Nov 30 10:55:13 sgallagh520 avahi-daemon[851]: Withdrawing workstation service for tun0. Nov 30 10:55:13 sgallagh520 NetworkManager[9219]: <warn> VPN plugin failed: 1 Nov 30 10:55:13 sgallagh520 NetworkManager[9219]: <info> VPN plugin state changed: stopped (6) Nov 30 10:55:13 sgallagh520 NetworkManager[9219]: <info> VPN plugin state change reason: 0 Nov 30 10:55:13 sgallagh520 NetworkManager[9219]: <info> Policy set 'burke-wep' (wlan0) as default for IPv4 routing and DNS. Nov 30 10:55:13 sgallagh520 NetworkManager[9219]: <warn> error disconnecting VPN: Could not process the request because no VPN connection was active. Nov 30 10:55:18 sgallagh520 NetworkManager[9219]: <info> VPN service 'vpnc' disappeared
just checked now, my openconnect-based vpn connection still works ok for me at least... using NetworkManager-0.9.7.0-8.git20121004.fc18.x86_64 so may be specific to vpnc/openvpn support somehow. have up instaled any NM-related updates recently, like, https://admin.fedoraproject.org/updates/FEDORA-2012-19154/NetworkManager-0.9.7.0-8.git20121004.fc18 or https://admin.fedoraproject.org/updates/FEDORA-2012-19137/NetworkManager-0.9.7.0-7.git20121004.fc18 ? mind testing if downgrading those helps any?
I experienced this with both 1:NetworkManager-0.9.7.0-6.git20121004.fc18.x86_64 and NetworkManager-0.9.7.0-8.git20121004.fc18.x86_64
http://lamarque-lvs.blogspot.co.at/2012/12/workaround-for-vpn-problem-with.html Looks like there's both a quick workaround and a proper fix in upstream kde-plasma-networkmanagement git for this issue now.
Wanna try this out? http://koji.fedoraproject.org/koji/taskinfo?taskID=4764135
kde-plasma-networkmanagement-0.9.0.5-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/kde-plasma-networkmanagement-0.9.0.5-3.fc18
Package kde-plasma-networkmanagement-0.9.0.5-3.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kde-plasma-networkmanagement-0.9.0.5-3.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19928/kde-plasma-networkmanagement-0.9.0.5-3.fc18 then log in and leave karma (feedback).
kde-plasma-networkmanagement-0.9.0.6-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/kde-plasma-networkmanagement-0.9.0.6-1.fc18
Package kde-plasma-networkmanagement-0.9.0.6-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kde-plasma-networkmanagement-0.9.0.6-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-0324/kde-plasma-networkmanagement-0.9.0.6-1.fc18 then log in and leave karma (feedback).
kde-plasma-networkmanagement-0.9.0.6-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.