From: "Björn JACKE" <bjacke@samba.org>
To: mptcp@lists.linux.dev
Subject: mtpcp not usable with ipv6 if built as module
Date: Wed, 5 Mar 2025 14:13:20 +0100 [thread overview]
Message-ID: <20250305131320.GA2676143@sernet.de> (raw)
Hi,
I know that this is a known issue and https://www.mptcp.dev/setup.html mentions
this but I would like to encourage the developers to fix the problem that mptcp
for ipv6 isn't available if ipv6 is built as a module.
The problem that mptcp doesn't work with ipv6 if built as a module is also not
very obvious when you are working on such a system. It simply does not work,
but no dmesg message or so is mentioning the lack of mptcp support at runtime.
The system where I hit this was as raspi system, where ipv6 is built as a
module due to size reasons, which is reasonable for small memory systems. See
https://github.com/raspberrypi/linux/issues/6518 and
https://github.com/raspberrypi/linux/pull/5487
Maybe this is a bit of a motivation to fix the module build of mptcp with ipv6,
raspberry users (and some more probably) would very much apreciate it.
Cheers
Björn
next reply other threads:[~2025-03-05 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 13:13 Björn JACKE [this message]
2025-03-05 13:36 ` mtpcp not usable with ipv6 if built as module Matthieu Baerts
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=20250305131320.GA2676143@sernet.de \
--to=bjacke@samba.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.