From: Matthieu Baerts <matttbe@kernel.org>
To: Mat Martineau <martineau@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next 0/3] mptcp: blackhole: sysctl SYN retrans + fix conditions
Date: Fri, 17 Jan 2025 15:33:42 +0100 [thread overview]
Message-ID: <34877829-ddd6-4d2d-858e-d057da9c1dba@kernel.org> (raw)
In-Reply-To: <99988d16-43a3-bdd3-c9e7-ccc992570eb2@kernel.org>
H Mat,
On 17/01/2025 01:13, Mat Martineau wrote:
> 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>
Thank you for the review!
I already applied these two patches:
New patches for t/upstream-net and t/upstream:
- 34dc1c307f30: doc: mptcp: sysctl: blackhole_timeout is per-netns
- Results: 1b76b0bd2522..551c1dba2a68 (export-net)
- Results: 2a6dfa001e66..2d16bea74b90 (export)
New patches for t/upstream:
- 5fb87b001602: mptcp: sysctl: add syn_retrans_before_tcp_fallback
- Results: 2d16bea74b90..b7be33140cc3 (export)
Tests are now in progress:
- export-net:
https://github.com/multipath-tcp/mptcp_net-next/commit/70769bbce0f766c3583cb1caa791722685884f19/checks
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/caa6490e85f954f97ad955a2496c1b1297efee89/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2025-01-17 14:33 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
2025-01-17 14:33 ` Matthieu Baerts [this message]
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=34877829-ddd6-4d2d-858e-d057da9c1dba@kernel.org \
--to=matttbe@kernel.org \
--cc=martineau@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