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 2060905 - [RFE] Support connection for loopback interface
Summary: [RFE] Support connection for loopback interface
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.6
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: Desktop QE
Jaroslav Klech
URL:
Whiteboard:
Depends On:
Blocks: 2059655 2073512 2130221
TreeView+ depends on / blocked
 
Reported: 2022-03-04 13:45 UTC by Gris Ge
Modified: 2023-02-08 15:16 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2073512 (view as bug list)
Environment:
Last Closed: 2022-11-29 22:57:37 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-248 0 None None None 2023-02-06 12:31:28 UTC
Red Hat Issue Tracker RHELPLAN-114533 0 None None None 2022-03-04 13:46:58 UTC
Red Hat Knowledge Base (Solution) 2108251 0 None None None 2022-07-12 13:30:27 UTC
Red Hat Knowledge Base (Solution) 6844771 0 None None None 2022-03-30 05:47:06 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 1287 0 None opened [Draft] Support loopback interface 2022-08-04 12:38:26 UTC

Description Gris Ge 2022-03-04 13:45:48 UTC 
Description of problem:

Supporting loopback interface allows us:
 * Add extra IP to loopback.
 * Define DNS configuration.
 * Define special route which does not bind to a interface.
 * Define route rule which is not interface related.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Jamie Bainbridge 2022-03-30 05:46:22 UTC 
Customers running Oracle often want to change the MTU of the loopback to 16 KiB (down from the default 64 KiB).

I'm not sure why this is. It seems Oracle sends MTU-sized UDP messages, however it can't handle such large messages as 64 KiB at once without dropping them. Reducing the MTU to 16 KiB resolves this.

As far as I know, every system running Oracle needs to manage the loopback MTU.
Comment 15 Thomas Haller 2022-11-25 16:00:11 UTC 
fixed upstream (1.41.6+) by https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1332
Comment 16 Jamie Bainbridge 2022-11-29 22:57:37 UTC 
This work is done upstream but it is a large set of code changes and introduces undesirable risk to backport to RHEL 8. To ensure the stability of NetworkManager in RHEL8, this feature will be delivered in RHEL 9 and later. That work is being done on Bug 2073512.

For RHEL 8 and earlier, there are multiple viable workarounds depending on specific need. These include:

- a dummy interface to hold IP addresses
- a systemd unit to apply loopback settings on boot
- use the network initscript to manage loopback settings/IPs

These are documented on the knowledgebase at:

 How do I manage the "lo" loopback interface using NetworkManager? 
 https://access.redhat.com/solutions/2108251
Comment 17 Jaroslav Klech 2023-02-06 12:30:54 UTC 
(In reply to Jamie Bainbridge from comment #16)
> This work is done upstream but it is a large set of code changes and
> introduces undesirable risk to backport to RHEL 8. To ensure the stability
> of NetworkManager in RHEL8, this feature will be delivered in RHEL 9 and
> later. That work is being done on Bug 2073512.
> 
> For RHEL 8 and earlier, there are multiple viable workarounds depending on
> specific need. These include:
> 
> - a dummy interface to hold IP addresses
> - a systemd unit to apply loopback settings on boot
> - use the network initscript to manage loopback settings/IPs
> 
> These are documented on the knowledgebase at:
> 
>  How do I manage the "lo" loopback interface using NetworkManager? 
>  https://access.redhat.com/solutions/2108251

Hi Jamie,

does it mean that for RHEL 8 there does not need to be a release note for this feature?

Thanks for your clarification,
Jaroslav
Comment 18 Jamie Bainbridge 2023-02-07 01:54:43 UTC 
(In reply to Jaroslav Klech from comment #17)
> does it mean that for RHEL 8 there does not need to be a release note for
> this feature?

I don't expect this would be in the Release Notes for RHEL 8.

This isn't a feature at all in RHEL 8, so we wouldn't say that we haven't put the feature in.

For customers who ask the specific "how do I do this?" question, we have the knowledgebase to answer that.

However, I expect this feature would be in the RHEL 9.2 Release Notes, and that work can be done on Bug 2073512 which includes this feature in 9.2.

lmk if I can help any time.
Comment 19 Jaroslav Klech 2023-02-08 15:16:35 UTC 
(In reply to Jamie Bainbridge from comment #18)
> (In reply to Jaroslav Klech from comment #17)
> > does it mean that for RHEL 8 there does not need to be a release note for
> > this feature?
> 
> I don't expect this would be in the Release Notes for RHEL 8.
> 
> This isn't a feature at all in RHEL 8, so we wouldn't say that we haven't
> put the feature in.
> 
> For customers who ask the specific "how do I do this?" question, we have the
> knowledgebase to answer that.
> 
> However, I expect this feature would be in the RHEL 9.2 Release Notes, and
> that work can be done on Bug 2073512 which includes this feature in 9.2.
> 
> lmk if I can help any time.

Based on the previous comment, im removing this from 8.8 RN schedule. Setting "No Doc Update", removing from tickets.yml
Note You need to log in before you can comment on or make changes to this bug.