Created attachment 1108954 [details] Output from "/usr/libexec/nm-vpnc-service --debug". Description of problem: Establishing a VPN connection via NetworkManager-vpnc fails on RHEL 7.2 machine since recent update to 1.0.8 ("Terminated vpnc daemon with PID xxx"). Version-Release number of selected component (if applicable): NetworkManager-vpnc.x86_64 1:1.0.8-1.el7 @epel NetworkManager-vpnc-gnome.x86_64 1:1.0.8-1.el7 @epel vpnc.x86_64 0.5.3-22.svn457.el7 @epel vpnc-script.noarch 0.5.3-22.svn457.el7 @epel uname -r: 3.10.0-327.3.1.el7.x86_64 How reproducible: On RHEL 7.2 with EPEL repos, update to NetworkManager-vpnc 1.0.8. Try re-establishing a previously working VPN connection via NetworkManager-vpnc-gnome. Steps to Reproduce: 1. Choose a VPN connection from the Gnome Network Manager. 2. Enter your credentials. Actual results: VPN connection establishment fails. Expected results: VPN connection establishment succeeds. Additional info: Establishing a connection manually via vpnc using the same connection info and credentials works.
Created attachment 1108955 [details] Output from journalctl.
I believe this is the same issue that bit me today. I am using libreswan as a workaround.
This hits me also on my CentOS 7.2 X86_64 after "yum update". My workaround was to erase the NetworkManager-vpnc\* packages and reinstall these packages from nux-dextop repository
I think that the bug is actually not in NetworkManager-vpnc, but in NetworkManager-vpnc-gnome. After configuring my VPN (name VPNCName) via the GUI, and separately via a vpnc config file in /etc/vpnc starting from command line "vpnc" -> works starting from NetworkManager cli "nmcli con up id VPNCName" -> works!!! starting the same networkmanager interface from gnome-classic GUI -> fail so the NetworkManager-vpnc plugin itself works when started from the command line, it only breaks when I try to start it from the GUI.
*** This bug has been marked as a duplicate of bug 1298732 ***