mptcp: fallback to TCP after 3 MPC drop + cache #156
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After 3 failed attempts, there is a fallback to TCP. Link: multipath-tcp/mptcp_net-next#477 Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
After 3 failed attempts, there is a fallback to TCP. If this "plain" TCP connection was a success, it likely means that MPTCP is blocked. The next connections now directly falls back to TCP. Link: multipath-tcp/mptcp_net-next#57 Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
|
(The kernel patches have just been sent on the ML) |
|
(FYI, the kernel patches have just been applied in the |
|
I suggest merging these because the new feature is already in net-next, best to make sure there are no regressions later on. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A new series has been recently shared to force a fallback to TCP after 3 failed MPC attempts. If the "plain" TCP connection is a success after this fallback, it likely means that MPTCP is blocked. The next connections will directly fall back to TCP.
That's what is being validated here.
See these tickets for more details: