From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: "Sven Eckelmann" <sven@narfation.org>,
"Martin Hundebøll" <martin@hundeboll.net>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH 0/2] batman-adv: remove network coding support
Date: Mon, 1 Sep 2025 03:50:12 +0200 [thread overview]
Message-ID: <aLT71OlX6b7YUZQj@sellars> (raw)
In-Reply-To: <20250831-drop-catwoman-v1-0-1071bb2a159a@narfation.org>
On Sun, Aug 31, 2025 at 05:40:00PM +0200, Sven Eckelmann wrote:
> This assumption no longer holds for modern wireless mesh networks, which
> are heterogeneous and make overhearing increasingly unreliable.
.oO(I was wondering if it could be interesting again with IEEE
802.11ah HaLow. Recently read that AREDN mesh had added
experimental support in their firmware (though with using Babel,
not batman-adv), with ALFA Network Tube-AHM R0C devices.
https://www.arednmesh.org/content/aredn-production-release-32580-now-available
But testing and tuning HaLow + batman-adv + NC would still
be quite some work...)
Have had the pleasure to play with this ages ago on 802.11g
hardware. It generally semeed to work and was a lot of fun to
experiment with. But it wasn't easy to use it reliably, it needed
quite some precise placement of nodes. Rate control algorithms
wouldn't be aware of network coding opportunities, would have
been nice if it had sometimes chosen slower rates for more
NC opportunities. (Also CPU usage with promisc mode was maybe
an issue back then on many devices? But maybe I misremember that.)
I'd maybe try to ask around one more time on Freifunk or
Battlemesh channels if anyone would be interested in reviving
this, a final call. But as to my knowledge no one has used it in
practical scenarios I guess the chances are low. And I agree that
it might maybe be better to remove it then in the upstream Linux
kernel.
Many thanks for the awesome work on this exciting experiment though,
Martin! I think it inspired quite some people and contributed to
the crazy mesh excitment and pioneering back then that was going
on at all fronts.
Regards, Linus
prev parent reply other threads:[~2025-09-01 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 15:40 [PATCH 0/2] batman-adv: remove network coding support Sven Eckelmann
2025-08-31 15:40 ` [PATCH 1/2] " Sven Eckelmann
2025-08-31 16:14 ` Martin Hundebøll
2025-09-01 13:08 ` Marek Lindner
2025-08-31 15:40 ` [PATCH 2/2] batman-adv: keep skb crc32 helper local in BLA Sven Eckelmann
2025-09-01 1:50 ` Linus Lüssing [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=aLT71OlX6b7YUZQj@sellars \
--to=linus.luessing@c0d3.blue \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=martin@hundeboll.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox