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 1832170 - Cannot bring up ip6gre tunnel connection via NetworkManager
Summary: Cannot bring up ip6gre tunnel connection via NetworkManager
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.9
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1704308
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-06 09:09 UTC by Vladimir Benes
Modified: 2020-09-29 20:30 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1704308
Environment:
Last Closed: 2020-09-29 20:30:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
[PATCH] ip-tunnel: set the cloned-mac-address only for L2 tunnel devices (2.43 KB, patch)
2020-05-06 14:56 UTC, Beniamino Galvani 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4003 0 None None None 2020-09-29 20:30:52 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 503 0 None None None 2020-05-14 12:52:34 UTC

Comment 6 Beniamino Galvani 2020-05-06 14:56:55 UTC 
Created attachment 1685764 [details]
[PATCH] ip-tunnel: set the cloned-mac-address only for L2 tunnel devices

On RHEL 7.9 there was this kernel commit [1] that started to set a permanent hardware address for L3 tunnels like ipgre and ip6gre. On RHEL7 NM tries to restore the permanent MAC (if any exists) during activation, and this fails for such devices.

I think we should apply the RHEL7-only patch attached to skip setting the MAC on L3 tunnels.

[1] http://git.app.eng.bos.redhat.com/git/rhel7.git/commit/?id=02b67e205e335edfd1e3444e39f94296fd770c69
Comment 8 Thomas Haller 2020-05-06 19:03:02 UTC 
>    On master the default value for cloned-mac-address is 'preserve' and
>    so there is the guarantee that NM never tries to change the MAC for L3
>    tunnels.
>
>    RHEL7 has a downstream patch that changes the default
>    cloned-mac-address to 'permanent'; therefore we have to ensure that
>    the tunnel mode allows it before trying to change the MAC.

Yes, this default makes it more critical, but it's an issue in general. "never tries to change" is not true. As always, it depends on the configuration. "ethernet.cloned-mac-address" should behave sensibly, regardless of what's the default it.


The patch looks god to me, but I think we should not backport to RHEL-7 only.
As always, let's fix the issue on master first, then on nm-1-24 (preferably by cherry-picking), then on nm-1-22, etc.pp.

Maybe on master it doesn't apply exactly the same way. So on master it may need a different solution (or is already fixed).

I think it's important to ensure that every fix in a version is also fixed in all newer versions.
Comment 9 Beniamino Galvani 2020-05-13 08:39:51 UTC 
I've opened a merge request to fix the problem on master:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/503
Comment 14 Vladimir Benes 2020-05-19 13:37:23 UTC 
test passing now.
Comment 16 errata-xmlrpc 2020-09-29 20:30:25 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 (Moderate: NetworkManager security and bug fix update), 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/RHSA-2020:4003
Note You need to log in before you can comment on or make changes to this bug.