From: Mat Martineau <martineau@kernel.org>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next 0/3] mptcp: blackhole: sysctl SYN retrans + fix conditions
Date: Thu, 16 Jan 2025 16:13:15 -0800 (PST) [thread overview]
Message-ID: <99988d16-43a3-bdd3-c9e7-ccc992570eb2@kernel.org> (raw)
In-Reply-To: <20250114-mpc-no-blackhole-v1-0-994bd2a357fb@kernel.org>
On Tue, 14 Jan 2025, Matthieu Baerts (NGI0) wrote:
> Recently, I found a network having weird behaviours with MPTCP packets:
>
> - The first connection to a server had a successful 3WHS, then MPTCP
> options got stripped off.
>
> - The next one had the first SYN (with or without MPTCP) and 5
> retransmissions dropped, before being apparently intercepted and
> proxied to the end server.
>
> - (The next ones were sometimes intercepted, sometimes not, or dropped
> at the beginning. I'm trying to find out which kind of "optimiser" is
> causing this.)
>
> The result of this was a blackhole being "wrongly" detected, and no ways
> to force connections with quite a few SYN drops to finally use MPTCP at
> the end.
>
> In this series, we have:
>
> - A small fix for the doc.
>
> - A new sysctl to change the number of SYN retransmitted with MPTCP
> options before falling back to TCP. The modification looks simple
> enough to still be sent to netdev before the closure I think.
>
Hi Matthieu -
Patches 1 and 2 LGTM:
Reviewed-by: Mat Martineau <martineau@kernel.org>
> - A fix to only turn on the blackhole protection only when the first SYN
> retransmitted without MPTCP option is accepted, instead of any after.
> The blackhole feature was supposed to do that from the beginning, but
> a check was wrongly placed. I think we should consider this as a fix,
> even if there are also risks of not detecting a blackhole if the first
> SYN retransmitted without MPTCP is dropped by accident. But that seems
> more unlikely for an "MPTCP firewall blackhole", and I guess not all
> future MPTCP connections will behave exactly like that. It sounds then
> safer to reduce the possibilities of enabling the blackhole protection
> by accident, and apply this patch.
I have one comment on patch 3, see my reply there.
- Mat
>
> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
> ---
> Matthieu Baerts (NGI0) (3):
> doc: mptcp: sysctl: blackhole_timeout is per-netns
> mptcp: sysctl: add syn_retrans_before_tcp_fallback
> mptcp: blackhole only if 1st SYN retrans w/o MPC is accepted
>
> Documentation/networking/mptcp-sysctl.rst | 18 +++++++++++++++++-
> net/mptcp/ctrl.c | 25 +++++++++++++++++++------
> 2 files changed, 36 insertions(+), 7 deletions(-)
> ---
> base-commit: 9336324d1aec351496e048ec5b6bbda07944ad16
> change-id: 20250114-mpc-no-blackhole-526a61ea0334
>
> Best regards,
> --
> Matthieu Baerts (NGI0) <matttbe@kernel.org>
>
>
>
next prev parent reply other threads:[~2025-01-17 0:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 17:37 [PATCH mptcp-next 0/3] mptcp: blackhole: sysctl SYN retrans + fix conditions Matthieu Baerts (NGI0)
2025-01-14 17:37 ` [PATCH mptcp-next 1/3] doc: mptcp: sysctl: blackhole_timeout is per-netns Matthieu Baerts (NGI0)
2025-01-14 17:37 ` [PATCH mptcp-next 2/3] mptcp: sysctl: add syn_retrans_before_tcp_fallback Matthieu Baerts (NGI0)
2025-01-14 17:37 ` [PATCH mptcp-next 3/3] mptcp: blackhole only if 1st SYN retrans w/o MPC is accepted Matthieu Baerts (NGI0)
2025-01-17 0:26 ` Mat Martineau
2025-01-17 15:10 ` Matthieu Baerts
2025-01-21 22:36 ` Mat Martineau
2025-01-22 11:41 ` Matthieu Baerts
2025-01-14 18:50 ` [PATCH mptcp-next 0/3] mptcp: blackhole: sysctl SYN retrans + fix conditions MPTCP CI
2025-01-17 0:13 ` Mat Martineau [this message]
2025-01-17 14:33 ` Matthieu Baerts
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=99988d16-43a3-bdd3-c9e7-ccc992570eb2@kernel.org \
--to=martineau@kernel.org \
--cc=matttbe@kernel.org \
--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