If you are a sysadmin, feel free to enable MPTCP support on NGINX and any other server side services: no impact on “plain” TCP connections because “plain” TCP requests will trigger the creation of a “plain” TCP socket on the server side when being accepted. MPTCP will only be used when requested by the clients, which are usually the ones benefiting from using MPTCP 🔀.
More details here.
NGINX 🌐 1.29.7 mainline version introduces support for Multipath TCP 🔀 🎉
This comes a bit after two NGINX’s forks – freenginx and Angie – with a different approach, but still with the same way to enable it: simply by adding the multipath parameter to the listen instruction, e.g.
listen <address|port> multipath
More details here.
Did you know you can have MPTCP support with any devices running Android 16? 😯
OK, it is not easily accessible, but using the included Terminal app 🖥️, you can use MPTCP! 🔀
(Android 16 has a Terminal app which runs a full Linux VM with Debian Bookworm and a kernel 6.1 with MPTCP support. Sadly, Google still didn't add full MPTCP support, despite now using kernels supporting it. If you know people who can change that, please contact me 🙂)
Do you use SSH with MPTCP 🔀 for better resilience in mobility use cases or to increase the throughput? Then, feel free to check the new script to pass to ProxyCommand in the SSH config instead of using mptcpize: https://www.mptcp.dev/faq.html#how-to-enable-mptcp-support-with-openssh
Thanks to @shoragan for having shared this script!
(Hopefully the SSH maintainers will allow one of the suggested (1) (2) native MPTCP support at some points!)