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.

Bug 1704308

Summary:	Cannot bring up ip6gre tunnel connection via NetworkManager
Product:	Red Hat Enterprise Linux 7	Reporter:	Davide F Bragalone <dbragalo>
Component:	NetworkManager	Assignee:	Beniamino Galvani <bgalvani>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	atragler, bgalvani, fgiudici, fpokryvk, lrintel, ptalbert, rkhan, sukulkar, thaller, tpelka, vbenes
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	NetworkManager-1.18.0-2.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1832170 (view as bug list)		Environment:
Last Closed:	2019-08-06 13:16:56 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:
Bug Depends On:
Bug Blocks:	1832170

Description Davide F Bragalone 2019-04-29 14:11:13 UTC

Description of problem:
Facing issues when a ip6gre tunnel is created via NetworkManager.

Same connection can be created/activated via 'ip' command but not with NetworkManager. Please refer to reproducer section for more info.

It seems that even though nmcli supports that, NM backend does not.

Support was added upstream in NetworkManager version 1.14:

- ip-tunnel: add support for ip6gre and ip6gretap tunnel connections
https://github.com/NetworkManager/NetworkManager/commit/3f9f9f7fa228615967efd6000804f30011f33576


Version-Release number of selected component (if applicable):
RHEL7.6
NetworkManager-1.12.0-8.el7_6.x86_64

How reproducible:


# nmcli connection add type ip-tunnel autoconnect yes ifname foobar mode ip6gre local fd01::170 remote fd02::172 con-name mytunnel0

# nmcli connection up mytunnel0 
Error: Connection activation failed: Failed to find a compatible device for this connection


Actual results:
Cannot bring up connection, always getting above error about device.

Expected results:
Being able to configure and use ip6gre tunnel via NetworkManager.



Additional info:

nmcli supports ip6gre type though:
# nmcli connection add type ip-tunnel mode 
gre     ip6gre  ip6ip6  ipip    ipip6   isatap  sit     vti     vti6


In RHEL8 works (NM version (1.14.0-14.el8.x86_64):

# nmcli con sh
NAME                UUID                                  TYPE      DEVICE 
Wired connection 1  a7b25632-c300-31fa-8b6e-b44ed03c29d9  ethernet  ens3   

# nmcli connection add type ip-tunnel con-name gre6msk mode ip6gre local fc00::10:10 remote fc00::10:11 ipv4.method disabled ifname gre123
Connection 'gre6msk' (24700519-33e5-4be8-afdd-2eb659f2591d) successfully added.

# nmcli con sh 
NAME                UUID                                  TYPE       DEVICE 
Wired connection 1  a7b25632-c300-31fa-8b6e-b44ed03c29d9  ethernet   ens3   
gre6msk             24700519-33e5-4be8-afdd-2eb659f2591d  ip-tunnel  gre123

Comment 3 Beniamino Galvani 2019-04-30 12:30:39 UTC

Hi, ip6gre tunnels are supported by NM on RHEL 7.7.

Comment 4 Davide F Bragalone 2019-04-30 12:43:29 UTC

Hello Beniamino,

Thanks for the quick answer. May I ask you if this implementation was tracked by any BZ? If yes could you point me to that? I tried to look for it with no luck.

Thanks again,
Davide

Comment 5 Beniamino Galvani 2019-04-30 12:54:03 UTC

The enhancement was request on the upstream bugzilla:

  https://bugzilla.gnome.org/show_bug.cgi?id=796645

As you already noticed, the commit was included in NM 1.14:

  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/2ee76c88c10c109d7607501033097a0a762f9687

RHEL 7.7 ships NM 1.18 so the feature is available there.

Comment 6 Davide F Bragalone 2019-04-30 13:15:41 UTC

Thanks a lot for the info.

Regards,
Davide

Comment 11 errata-xmlrpc 2019-08-06 13:16:56 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2302