Bug 2120473

Summary:	[RFE] Support MPTCP
Product:	Red Hat Enterprise Linux 9	Reporter:	Gris Ge <fge>
Component:	nmstate	Assignee:	Gris Ge <fge>
Status:	CLOSED ERRATA	QA Contact:	Mingyu Shi <mshi>
Severity:	medium	Docs Contact:	Marc Muehlfeld <mmuehlfe>
Priority:	medium
Version:	9.1	CC:	ferferna, jiji, jishi, network-qe, sfaye, till
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	9.2	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	.The `nmstate` API now supports MPTCP flags This update enhances the `nmstate` API with support for MultiPath TCP (MPTCP) flags. As a result, you can use `nmstate` to set MPTCP address flags on interfaces with static or dynamic IP addresses.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-09 07:31:48 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:

Description Gris Ge 2022-08-23 03:25:48 UTC

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Gris Ge 2022-08-23 03:27:12 UTC

Patch posted to upstream: https://github.com/nmstate/nmstate/pull/2014

Support configure interface level MPTCP flags:

```yml
---
interfaces:
  - name: eth1
    type: ethernet
    state: up
    mptcp:
      address-flags:
      - subflow
      - backup
      - fullmesh
```

When querying, also include MPTCP flags per IP address:

```yml
address:
  - ip: 192.0.2.2
    prefix-length: 24
    mptcp-flags:
      - signal
      - subflow
```

For interface level MPTCP flags, will apply flags to all valid IP
addresses(both static and dynamic). Plugin might has their own rule on
excusing special scope of IP address, e.g. IPv6 multicast address.

Limitations:
 * Per IP address MPTCP flags is ignored with an warning message when
   different from interface level MPTCP flags.
 * Cannot set `signal` along with `fullmesh` due to kernel restriction.
 * If sysctl has `net.mptcp.enabled` set to 0, NetworkManager cannot
   apply MPTCP flags. User will get an failure suggest them to use
   third-party tools.

Comment 14 errata-xmlrpc 2023-05-09 07:31:48 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 (nmstate bug fix and enhancement 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/RHBA-2023:2190