From: "Nicolas Escande" <nico.escande@gmail.com>
To: "Linus Lüssing" <linus.luessing@c0d3.blue>
Cc: "Sven Eckelmann" <sven@narfation.org>, <b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [PATCH v2] batman-adv: add dynamic, bridged-in TT VID detection support
Date: Thu, 21 Nov 2024 16:10:45 +0100 [thread overview]
Message-ID: <D5RYB29K4VH1.2I26Q6OMZX39J@gmail.com> (raw)
In-Reply-To: <ZzY8CdiUV_sYsHul@sellars>
On Thu Nov 14, 2024 at 7:06 PM CET, Linus Lüssing wrote:
> Hi Nicolas,
>
> Many thanks for your feedback!
>
[...]
>
> > >
> > > I am not in favour of changing the behavior of batman-adv. Now everyone can
> > > increase the number of managed VLANs without any control by the node admin.
>
> Valid concern. Especially as each added VLAN is quite costly for
> an OGM at the moment. A VLAN with one MAC address adds 12 bytes to
> a 24 bytes base OGM IV length (excluding ethernet header and other
> TVLVs).
>
> However in a way for non-VLAN TT entries this is also partially a concern,
> right? Someone could also flood source MAC addresses in an uncontrolled
> way, too. (Though would likely have to actively keep roaming to create a
> constant extra overhead.)
>
> Maybe it would make sense to check how the Linux bridge approaches
> this?
>
> It seems there is an admin configurable limit of
> BR_MULTICAST_DEFAULT_HASH_MAX = 4096 entries for the MDB
> (multicast MAC addresses).
> And a configurable fdb_max_learned (disabled by default, for
> backwards compatibility reasons according to bdb4dfda3b) for the
> FDB (unicast MAC addresse).
> Thirdly, it seems 4096 VLANs are allowed (VLAN_N_VID), the maximum
> amount. Though this one does not seem configurable.
>
> Would it maybe make sense to have a knob and by default set the
> limit to 8 or 16 VLANs? A default which could maybe be increased if the
> OGM size was decoupled from the amount of VLANs in the future?
>
I really like this idea. This either could be a compile time knob or a dynamic
one to ensure we don't easilly have a too big OGM
> ---
>
> The two reasons I would like to have a dynamic VLAN feature,
> especially for wireless community mesh networks:
>
> Allow a group of people to setup and use their own address space
> when the centrally managed, default one does not match their
> needs. -> decentralization
>
> Allow to get rid of the unused VID=0 and VID=1 entries by default,
> only dynamically learn them, to typically reduce the OGM overhead
> by at least 2*12 bytes. To partially mitigate the overhead regression
> we introduced by adding TT in compat 15.
>
> ---
>
> Just my overall, conceptual thoughts on this feature. Will look into the
> refcount issue later, thanks for reporting!
>
> Regards, Linus
Thanks
next prev parent reply other threads:[~2024-11-21 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 21:39 [PATCH v2] batman-adv: add dynamic, bridged-in TT VID detection support Linus Lüssing
2024-06-16 20:38 ` Linus Lüssing
2024-07-12 22:13 ` Linus Lüssing
2024-11-14 13:48 ` Nicolas Escande
2024-11-14 13:58 ` Sven Eckelmann
2024-11-14 14:53 ` Nicolas Escande
2024-11-14 18:06 ` Linus Lüssing
2024-11-21 15:10 ` Nicolas Escande [this message]
2024-11-24 9:47 ` Sven Eckelmann
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=D5RYB29K4VH1.2I26Q6OMZX39J@gmail.com \
--to=nico.escande@gmail.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=linus.luessing@c0d3.blue \
--cc=sven@narfation.org \
/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.