Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Cannot connect to Cisco VPN with NetworkManager-openswan. Using openswan directly works as expected.
Version-Release number of selected component (if applicable):
NetworkManager-openswan-0.9.3.995-2.git20120302.el7
NetworkManager-0.9.4-3.git20120403.el7
openswan-2.6.37-3.el7
How reproducible:
100%
Steps to Reproduce:
1. Create a VPN profile to connect to a Cisco VPN endpoint
2. Attempt to connect
Actual results:
nothing happens, connection fails, but there is no notification why.
Expected results:
connection is established.
Additional info:
Proposing as a blocker since openswan is only VPN solution provided by Networkmanager.
openswan does not use tun interface, so ip_iface and ip_ifindex are not valid.
Aug 3 16:07:04 dhcp-29-57 NetworkManager[1067]: nm_system_iface_set_up: assertion `ifindex > 0' failed
Aug 3 16:07:04 dhcp-29-57 NetworkManager[1067]: nm_system_apply_ip4_config: assertion `ifindex > 0' failed
Aug 3 16:07:04 dhcp-29-57 NetworkManager[1067]: <warn> VPN connection 'RH' did not receive valid IP config information.
The assertions are fixed by:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=383a397a92621cdc299be561674fd3ad8b8304e5
However, we need to make some changes in both NM and the NM-openswan plugin in order to make openswan work again. See attached patches.
Created attachment 663111[details]
[PATCH] NM patch correcting the behaviour when no tun device is used
This patch allows VPN connections not to use tun device.
Created attachment 663112[details]
[PATCH] NM-openswan plugin patch indicating no tun is used
This patch makes NM-openswan tell NM that tun device is not used.
(In reply to comment #6)
> Created attachment 663112[details]
> [PATCH] NM-openswan plugin patch indicating no tun is used
>
> This patch makes NM-openswan tell NM that tun device is not used.
I can add this patch to NM-openswan, but on RHEL6 it works without this patch. Thats why I created bug 865883 as it is a regression.