From: Simon Wunderlich <sw@simonwunderlich.de>
To: cchien@creonexsystems.com, b.a.t.m.a.n@lists.open-mesh.org
Cc: Sven Eckelmann <sven@narfation.org>
Subject: Re: Question about batman for ARM
Date: Fri, 17 Jun 2022 15:53:07 +0200 [thread overview]
Message-ID: <2037952.ni6AN7iZ1R@prime> (raw)
In-Reply-To: <3826484.QQW5a1qdB9@ripper>
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
On Friday, June 17, 2022 10:45:48 AM CEST Sven Eckelmann wrote:
> On Friday, 17 June 2022 10:41:46 CEST cchien@creonexsystems.com wrote:
> [...]
>
> > We would like to use batman with a custom radio and are trying to figure
> > out what part of the source code we may need to modify to allow batman to
> > work with a custom radio. Custom radio means that the radio is not a
> > commercial radio, such as wi-fi or Bluetooth.
> batman-adv (especially with the B.A.T.M.A.N. IV algo) only requires that the
> device itself can transport ethernet frames (with proper unicast and
> broadcast behavior). If you need something else then you either need a
> virtual interface which does the translation from $whatever to ethernet
> (and back) - or you need to reimplement the B.A.T.M.A.N. IV/V algorithms
> yourself.
In other words, if your radio comes up as a regular Ethernet interface in
Linux (like WiFi, for example), then you can easily run batman-adv on top of
it. If that's not the case, then you can write a driver to present a (virtual)
interface to the system like Sven suggested.
Cheers,
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-17 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 6:18 Question about batman for ARM Charles Chien
2022-05-20 7:43 ` Sven Eckelmann
2022-05-20 15:51 ` cchien
2022-06-17 8:41 ` cchien
2022-06-17 8:45 ` Sven Eckelmann
2022-06-17 13:53 ` Simon Wunderlich [this message]
2022-06-20 10:20 ` cchien
2022-06-20 12:50 ` Sven Eckelmann
2022-11-01 18:49 ` cchien
2022-11-01 19:31 ` Moritz Warning
2022-11-01 19:32 ` 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=2037952.ni6AN7iZ1R@prime \
--to=sw@simonwunderlich.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=cchien@creonexsystems.com \
--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.