-
Notifications
You must be signed in to change notification settings - Fork 349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add MPTCP socket protocol (optional) #466
Conversation
note: this PR will fail until socket2 make a new release with the new Protocol::MPTCP, but the content can still be reviewed |
Add the possibility to use the MPTCP protocol. (recently added here too: actix/actix-net#466) Check the link above (PR 466) to see the details about this change (it's pretty much the same). Signed-off-by: Martin Andre <martin.andre@tessares.net>
Add the possibility to use the MPTCP protocol. (recently added here too: actix/actix-net#466) Check the link above (PR 466) to see the details about this change (it's pretty much the same). Signed-off-by: Martin Andre <martin.andre@tessares.net>
Unfortunately, the I see there was a comment |
Add the possibility to use the MPTCP protocol at the socket level for users of ServerBuilder. MPTCP is now more widely available since Linux Kernel version >= 5.6. But it still need to be enabled manually using: `sysctl net.mptcp.enabled=1`. (of course, MPTCP is only available on Linux) The new MPTCP struct give the user the option to determine how we'll handle the case where MPTCP is not available on the host, either we crash, or we fallback to regular TCP. Signed-off-by: Martin Andre <martin.andre@tessares.net>
Signed-off-by: Martichou <m@rtin.fyi>
Thanks for pushing this. My tweaks are mostly mechanical. We're expecting Windows CI failures atm so no worries there. |
PR Type
Feature
Overview
Add the possibility to use the MPTCP protocol at the socket level for users of ServerBuilder.
MPTCP is now more widely available since Linux Kernel version >= 5.6. But it still need to be enabled manually using:
sysctl net.mptcp.enabled=1
(of course, MPTCP is only available on Linux).The new MPTCP struct give the user the option to determine how we'll handle the case where MPTCP is not available on the host, either we crash, or we fallback to regular TCP.