From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Linux <mptcp@lists.linux.dev>
Subject: TCP-in-UDP to avoid middleboxes interfering with MPTCP
Date: Mon, 14 Jul 2025 17:33:29 +0200 [thread overview]
Message-ID: <011abe39-2d60-4e69-a792-102efd219717@kernel.org> (raw)
Hello,
FYI, a new TCP-in-UDP tool is available, using eBPF to translate TCP
packets into UDP to avoid middleboxes interfering with some TCP
extensions like MPTCP.
Blog post explaining why it has been created, and its particularities:
https://blog.mptcp.dev/2025/07/14/TCP-in-UDP.html
Code and instructions:
https://github.com/multipath-tcp/tcp-in-udp
Enjoy!
Cheers,
Matt
reply other threads:[~2025-07-14 15:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=011abe39-2d60-4e69-a792-102efd219717@kernel.org \
--to=matttbe@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.