Bug 2064779

Summary:	Unable to add Cisco Compatible VPN (vpnc) from NetworkManager UI
Product:	[Fedora] Fedora	Reporter:	Jacob Emcken <jacob>
Component:	NetworkManager-vpnc	Assignee:	Lubomir Rintel <lkundrak>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	36	CC:	bgalvani, code, dcbw, fedora, fgiudici, fschwarz, huzaifas, lkundrak, thaller
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-25 17:40:31 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:

Description Jacob Emcken 2022-03-16 14:19:18 UTC

Description of problem:
I am unable to create a new "Cisco Compatible VPN" connection.


Version-Release number of selected component (if applicable):
1:1.2.8-1.fc36


How reproducible:
Everytime.


Steps to Reproduce:
1. Open "Network Settings" in Gnome.
2. Click the "+" next to the VPN heading and the "Add VPN" modal appears.
3. Choose "Cisco Compatible VPN (vpnc)" option.
4. Fill in "Gateway", "User name" and "Group name"
5. Click "Add" button in the window header (top right).


Actual results:
The new VPN connection is never added (lacks in the UI, but presumably not only in the UI).
The system log (journalctl --since "1 minutes ago" -f) shows the following:

...
Mar 16 15:09:32 hostname gnome-control-c[78883]: Failed to add connection: connection.interface-name: '': interface name must not be empty
...

Expected results:
The new VPN connection would be added and useable.


Additional info:
I can add PPTP VPN connections just fine, so it is very likely specific to vpnc and not all types of VPN.

Comment 1 Felix Schwarz 2022-07-17 11:09:53 UTC

I think this problem is recorded in the following upstream issue: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/982

possible duplicate (+ proposed workaround: bug 2065053)

Comment 2 Tommi 2023-04-24 13:24:42 UTC

I am having the same issue, on Fedora 38.

Comment 3 Ben Cotton 2023-04-25 16:55:36 UTC

This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Ludek Smid 2023-05-25 17:40:31 UTC

Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.