All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: "Björn JACKE" <bjacke@samba.org>, mptcp@lists.linux.dev
Subject: Re: mtpcp not usable with ipv6 if built as module
Date: Wed, 5 Mar 2025 14:36:02 +0100	[thread overview]
Message-ID: <bad1e8bc-8ac1-40dd-a63b-be25a812035f@kernel.org> (raw)
In-Reply-To: <20250305131320.GA2676143@sernet.de>

Hi Björn,

On 05/03/2025 14:13, Björn JACKE wrote:
> 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.

In most deployments, it doesn't make sense today to have IPV6 as a
module, because very likely, the IPV6 module will be loaded in RAM if
there is a network connection. Or simply when having the loopback
interface with the ::1 IPv6 address assigned to it.

Also, the effort looks consequent to properly support MPTCP as a module.

I just added a comment on the ticket you mentioned. To me, MPTCP_IPV6
should be enabled on all RPI >= 2, like it is on other major
distributions for the RPIs.

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


      reply	other threads:[~2025-03-05 13:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 13:13 mtpcp not usable with ipv6 if built as module Björn JACKE
2025-03-05 13:36 ` Matthieu Baerts [this message]

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=bad1e8bc-8ac1-40dd-a63b-be25a812035f@kernel.org \
    --to=matttbe@kernel.org \
    --cc=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.