kernel: enable MPTCP support #3248
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
![home-assistant[bot]](https://avatars.githubusercontent.com/in/97978?s=60&v=4){kind=small}
|
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
home-assistant
bot
added
cla-recheck
cla-signed
and removed
cla-recheck
cla-needed
labels
agners
reviewed
Mar 14, 2024
The official description says: Multipath TCP (MPTCP) connections send and receive data over multiple subflows in order to utilize multiple network paths. Each subflow uses the TCP protocol, and TCP options carry header information for MPTCP. Thanks to MPTCP, being able to use multiple paths in parallel or simultaneously brings new use-cases: - Seamless handovers: switching from one path to another while preserving established connections -- Apple is using it for this reason since 2013. - Best network selection: using the "best" available path (latency, losses, cost, bandwidth) -- one path can be used as a "backup" one. - Network aggregation: using multiple paths at the same time to have a higher throughput -- e.g. to combine a fixed an mobile network to send files faster. For example, for HA, it is possible to keep a SSH connection alive when switching from one network to another (e.g. while travelling). To be able to use MPTCP, both ends need to support it. An application has to request it, by creating an MPTCP socket instead of a TCP one. The rest in unchanged. An alternative is to use 'mptcpize' tool, which relies on LD_PRELOAD to create an MPTCP socket instead of a TCP one. Note that a MPTCP-enabled server continues to accept regular TCP connections that do not use the Multipath TCP extension without any performance impact. When a connection request is received, and is linked to a listening socket with MPTCP support, the kernel will simply check if MPTCP options are present. If not, the accepted socket will be a "plain" TCP one, with the same impact as before. To use multiple paths at the same time, additional IP addresses need to be configured, e.g. via the 'ip' tool (IPRoute2). MPTCP in the kernel is enabled in most main Linux distributions (Debian, Ubuntu, RedHat, Fedora, etc.), but in more specific ones like Raspbian. It is available in the Linux kernel since v5.6. Signed-off-by: Matthieu Baerts (NGI0) <[email protected]>
agners
approved these changes
Mar 14, 2024
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.
First, thank you for all the work around the Home-Assistant, it is a really useful project that we can control
The official description says:
Thanks to MPTCP, being able to use multiple paths in parallel or simultaneously brings new use-cases:
Seamless handovers: switching from one path to another while preserving established connections -- Apple is using it for this reason since 2013.
Best network selection: using the "best" available path (latency, losses, cost, bandwidth) -- one path can be used as a "backup" one.
Network aggregation: using multiple paths at the same time to have a higher throughput -- e.g. to combine a fixed an mobile network to send files faster.
For example, for HA, it is possible to keep a SSH connection alive when switching from one network to another (e.g. while travelling).
To be able to use MPTCP, both ends need to support it. An application has to request it, by creating an MPTCP socket instead of a TCP one. The rest in unchanged. An alternative is to use
mptcpizetool, which relies onLD_PRELOADto create an MPTCP socket instead of a TCP one.Note that a MPTCP-enabled server continues to accept regular TCP connections that do not use the Multipath TCP extension without any performance impact. When a connection request is received, and is linked to a listening socket with MPTCP support, the kernel will simply check if MPTCP options are present. If not, the accepted socket will be a "plain" TCP one, with the same impact as before.
To use multiple paths at the same time, additional IP addresses need to be configured, e.g. via the
iptool (IPRoute2).MPTCP in the kernel is light, and enabled in most main Linux distributions (Debian, Ubuntu, RedHat, Fedora, etc.), but in more specific ones like Raspbian. It is available in the Linux kernel since v5.6.
It would be nice to have it supported in hassio, to let apps using it.