Bug 1296220 - No longer connects to Red Hat VPN
Summary: No longer connects to Red Hat VPN
Keywords:
Status: CLOSED DUPLICATE of bug 1298732
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: NetworkManager-vpnc
Version: epel7
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Huzaifa S. Sidhpurwala
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-06 15:56 UTC by Tom Sorensen
Modified: 2016-04-14 07:44 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-14 07:44:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tom Sorensen 2016-01-06 15:56:32 UTC
Description of problem: Updated to NetworkManager-vpnc-1.0.8-1.el7 and NetworkManager-vpnc-gnome-1.0.8-1.el7 and can no longer connect to Red Hat VPN. Connecting via vpnc directly still works. 


Version-Release number of selected component (if applicable): 1.0.8-1


How reproducible: Always


Steps to Reproduce:
1. Click on VPN in top bar
2. Click Connect
3. Enter secret and OTP


Actual results:
Immediately fails to connect

Expected results:
A VPN connection

Additional info:
vpnc --gateway X --username Y --id Z
and then providing the secret and password works.

If I run "nmcli c up Name_of_VPN" then I get:
Error: Connection activation failed: no valid VPN secrets.

Output of jounalctl -u NetworkManager (from clicking in Gnome):
Jan 06 09:28:20 ts440s.tom.rh NetworkManager[1391]: <info>  Starting VPN service 'vpnc'...
Jan 06 09:28:20 ts440s.tom.rh NetworkManager[1391]: <info>  VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 16563
Jan 06 09:28:20 ts440s.tom.rh NetworkManager[1391]: <info>  VPN service 'vpnc' appeared; activating connections
Jan 06 09:28:26 ts440s.tom.rh NetworkManager[1391]: <info>  VPN plugin state changed: starting (3)
Jan 06 09:28:26 ts440s.tom.rh NetworkManager[1391]: <info>  VPN connection 'X' (ConnectInteractive) reply received.
Jan 06 09:28:26 ts440s.tom.rh NetworkManager[1391]: <info>  VPN plugin state changed: stopped (6)
Jan 06 09:28:26 ts440s.tom.rh NetworkManager[1391]: <info>  VPN plugin state change reason: unknown (0)
Jan 06 09:28:26 ts440s.tom.rh NetworkManager[1391]: ** Message: vpnc started with pid 16579
Jan 06 09:28:26 ts440s.tom.rh NetworkManager[1391]: ** Message: Terminated vpnc daemon with PID 16579.

Output of journalctl -u NetworkManager (from running nmcli):
Jan 06 10:19:38 ts440s.tom.rh NetworkManager[1391]: <info>  Starting VPN service 'vpnc'...
Jan 06 10:19:38 ts440s.tom.rh NetworkManager[1391]: <info>  VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 19213
Jan 06 10:19:38 ts440s.tom.rh NetworkManager[1391]: <info>  VPN service 'vpnc' appeared; activating connections
Jan 06 10:19:38 ts440s.tom.rh NetworkManager[1391]: ** (NetworkManager:1391): CRITICAL **: dbus_g_proxy_cancel_call: assertion 'pending != NULL' failed
Jan 06 10:19:38 ts440s.tom.rh NetworkManager[1391]: ** (NetworkManager:1391): CRITICAL **: dbus_g_proxy_cancel_call: assertion 'pending != NULL' failed
Jan 06 10:19:38 ts440s.tom.rh NetworkManager[1391]: <error> [1452093578.386224] [vpn-manager/nm-vpn-connection.c:1980] get_secrets_cb(): Failed to request VPN secrets #3: (4) No agents were available for this request.

Comment 1 Oliver Ilian 2016-04-14 07:44:06 UTC

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


Note You need to log in before you can comment on or make changes to this bug.