Bug 1293890

Summary: vpnc daemon terminates on connection setup attempt
Product: [Fedora] Fedora EPEL Reporter: Frank Zdarsky <fzdarsky>
Component: NetworkManager-vpncAssignee: Huzaifa S. Sidhpurwala <huzaifas>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: epel7CC: alex, ccheney, cdaley, huzaifas, markus, oliver, psimerda, ptalbert, stoty
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-14 07:44:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Output from "/usr/libexec/nm-vpnc-service --debug".
none
Output from journalctl. none

Description Frank Zdarsky 2015-12-23 11:55:18 UTC
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.

Comment 1 Frank Zdarsky 2015-12-23 11:57:00 UTC
Created attachment 1108955 [details]
Output from journalctl.

Comment 2 Chris Cheney 2016-01-13 04:51:28 UTC
I believe this is the same issue that bit me today. I am using libreswan as a workaround.

Comment 3 Markus Pohle 2016-01-28 09:42:19 UTC
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

Comment 4 István Tóth 2016-02-15 18:00:02 UTC
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.

Comment 5 Oliver Ilian 2016-04-14 07:44:23 UTC

*** This bug has been marked as a duplicate of bug 1298732 ***