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 1509210

Summary:	dlm: Add ability to recognise multiple source IP addresses per node for the TCP transport
Product:	Red Hat Enterprise Linux 8	Reporter:	Steve Whitehouse <swhiteho>
Component:	kernel	Assignee:	Alexander Aring <aahringo>
kernel sub component:	DLM	QA Contact:	cluster-qe <cluster-qe>
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	unspecified
Priority:	medium	CC:	aahringo, cfeist, coughlan, dhowells, gfs2-maint, rhandlin, rpeterso, swhiteho, teigland
Version:	CentOS Stream	Keywords:	FutureFeature, Reopened, Triaged
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	8.7
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:	2022-07-08 07:27:49 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:	1509204
Bug Blocks:

Description Steve Whitehouse 2017-11-03 10:54:35 UTC

Add the ability to specify multiple IP addresses per node for the TCP transport so that multi-homed configurations can use any of a set of IP addresses as a source address and still be recognised by the receiving node. Currently we only support a single source IP address per node when accepting connections.

This will allow support of a wider variety of network configurations.

This will likely need some userland changes too, but for the time being I've only opened a kernel bug to track this item. We can clone more bugs later as required, but this is enough to have a placeholder and a location for any discussion.

Comment 1 Mark Ferrell 2017-11-28 21:07:25 UTC

Is this envisioned as a potential multipath (with a connection per IP) or as a method by which to attempt to reestablish a lost connection with a node and possible round-robin through available IPs?

Comment 2 Steve Whitehouse 2017-11-29 09:36:08 UTC

The connection re-establishment is covered in other bugs. This is just to allow the use of multiple IPs per node, which will allow a wider set of network configs. The intention is that they could be used in combination of course.

Comment 3 Steve Whitehouse 2018-03-26 13:28:46 UTC

I'm guessing that this one should be a reasonable target for 7.6 ?

Comment 14 RHEL Program Management 2021-01-08 07:25:11 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 16 Steve Whitehouse 2021-01-08 09:15:26 UTC

Actively being worked on, and patches are going upstream at the moment

Comment 21 RHEL Program Management 2021-07-08 07:30:43 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 22 Steve Whitehouse 2021-07-08 08:27:43 UTC

Actively being worked on, so reopening.

Comment 26 RHEL Program Management 2022-01-08 07:26:59 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 27 Steve Whitehouse 2022-01-08 08:49:48 UTC

Reopening again

Comment 31 RHEL Program Management 2022-07-08 07:27:49 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.