Hello:
This series was applied to netdev/net.git (main) by Jakub Kicinski kuba@kernel.org:
On Fri, 12 Sep 2025 14:52:19 +0200 you wrote:
During the connection establishment, a peer can tell the other one that it cannot establish new subflows to the initial IP address and port by setting the 'C' flag [1]. Doing so makes sense when the sender is behind a strict NAT, operating behind a legacy Layer 4 load balancer, or using anycast IP address for example.
When this 'C' flag is set, the path-managers must then not try to establish new subflows to the other peer's initial IP address and port. The in-kernel PM has access to this info, but the userspace PM didn't, not letting the userspace daemon able to respect the RFC8684.
[...]
Here is the summary with links: - [net,1/5] mptcp: set remote_deny_join_id0 on SYN recv https://git.kernel.org/netdev/net/c/96939cec9940 - [net,2/5] mptcp: pm: nl: announce deny-join-id0 flag https://git.kernel.org/netdev/net/c/2293c57484ae - [net,3/5] selftests: mptcp: userspace pm: validate deny-join-id0 flag https://git.kernel.org/netdev/net/c/24733e193a0d - [net,4/5] mptcp: tfo: record 'deny join id0' info https://git.kernel.org/netdev/net/c/92da495cb657 - [net,5/5] selftests: mptcp: sockopt: fix error messages https://git.kernel.org/netdev/net/c/b86418beade1
You are awesome, thank you!