From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH v2 mptcp-next 0/3] mptcp: add support for mixed v4/v6
Date: Fri, 23 Dec 2022 20:00:11 +0100 [thread overview]
Message-ID: <cover.1671821017.git.pabeni@redhat.com> (raw)
The core MPTCP implementation is just a few bits of to support such
feature, we just need to allow specifying the subflow family explicitly
(patch 1/3) and remove the artificial constraint currently enforcing
no mixed subflow in place (patch 2/3)
Some self-tests added on patch 3/3
Merry Xmas ;)
v1 -> v2:
- only allow mixing family for ipv6 mptcp socket with no IPV6_ONLY
option (all the functional changes in 2/3 plus self-tests adaptation)
Paolo Abeni (3):
mptcp: explicitly specify sock family at subflow creation time
mptcp: let the in kernel PM use mixed ipv4 and ipv6 addresses
selftests: mptcp: add test-cases for mixed v4/v6 subflows
net/mptcp/pm_netlink.c | 68 ++++++++++++-------
net/mptcp/protocol.c | 2 +-
net/mptcp/protocol.h | 3 +-
net/mptcp/subflow.c | 9 +--
.../testing/selftests/net/mptcp/mptcp_join.sh | 53 ++++++++++++---
5 files changed, 94 insertions(+), 41 deletions(-)
--
2.38.1
next reply other threads:[~2022-12-23 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 19:00 Paolo Abeni [this message]
2022-12-23 19:00 ` [PATCH v2 mptcp-next 1/3] mptcp: explicitly specify sock family at subflow creation time Paolo Abeni
2022-12-26 17:00 ` Matthieu Baerts
2022-12-23 19:00 ` [PATCH v2 mptcp-next 2/3] mptcp: let the in kernel PM use mixed ipv4 and ipv6 addresses Paolo Abeni
2022-12-26 16:27 ` Matthieu Baerts
2022-12-23 19:00 ` [PATCH v2 mptcp-next 3/3] selftests: mptcp: add test-cases for mixed v4/v6 subflows Paolo Abeni
2022-12-23 19:37 ` selftests: mptcp: add test-cases for mixed v4/v6 subflows: Tests Results MPTCP CI
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1671821017.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--cc=mptcp@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox