From: Florian Westphal <fw@strlen.de>
To: <netdev@vger.kernel.org>
Cc: <mptcp@lists.01.org>
Subject: [PATCH net-next 0/3] mptcp: add REUSEADDR/REUSEPORT/V6ONLY setsockopt support
Date: Sun, 5 Jul 2020 01:30:14 +0200 [thread overview]
Message-ID: <20200704233017.20831-1-fw@strlen.de> (raw)
restarting an mptcp-patched sshd yields following error:
sshd: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
sshd: error: setsockopt IPV6_V6ONLY: Operation not supported
sshd: error: Bind to port 22 on :: failed: Address already in use.
sshd: fatal: Cannot bind any address.
This series adds support for the needed setsockopts:
First patch skips the generic SOL_SOCKET handler for MPTCP:
in mptcp case, the setsockopt needs to alter the tcp socket, not the mptcp
parent socket.
Second patch adds minimal SOL_SOCKET support: REUSEPORT and REUSEADDR.
Rest is still handled by the generic SOL_SOCKET code.
Last patch adds IPV6ONLY support. This makes ipv6 work for openssh:
It creates two listening sockets, before this patch, binding the ipv6
socket will fail because the port is already bound by the ipv4 one.
Florian Westphal (3):
net: use mptcp setsockopt function for SOL_SOCKET on mptcp sockets
mptcp: add REUSEADDR/REUSEPORT support
mptcp: support IPV6_V6ONLY setsockopt
net/mptcp/protocol.c | 64 ++++++++++++++++++++++++++++++++++++++++++++++++++++
net/socket.c | 13 ++++++++++-
2 files changed, 76 insertions(+), 1 deletion(-)
next reply other threads:[~2020-07-04 23:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 23:30 Florian Westphal [this message]
2020-07-04 23:30 ` [PATCH net-next 1/3] net: use mptcp setsockopt function for SOL_SOCKET on mptcp sockets Florian Westphal
2020-07-04 23:30 ` [PATCH net-next 2/3] mptcp: add REUSEADDR/REUSEPORT support Florian Westphal
2020-07-04 23:30 ` [PATCH net-next 3/3] mptcp: support IPV6_V6ONLY setsockopt Florian Westphal
2020-07-05 0:57 ` [PATCH net-next 0/3] mptcp: add REUSEADDR/REUSEPORT/V6ONLY setsockopt support David Miller
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=20200704233017.20831-1-fw@strlen.de \
--to=fw@strlen.de \
--cc=mptcp@lists.01.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).