public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: <cchien@creonexsystems.com>
To: 'Sven Eckelmann' <sven@narfation.org>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: RE: Question about batman for ARM
Date: Mon, 20 Jun 2022 03:20:19 -0700	[thread overview]
Message-ID: <014301d8848f$5874d0b0$095e7210$@creonexsystems.com> (raw)
In-Reply-To: <3826484.QQW5a1qdB9@ripper>

Hi Sven,

Thank you for the insight.
We definitely do not want to reimplement BATMAN.
Does BATMAN ADV interfaces with the radio via the network driver or does
BATMAN include the network driver?
Can you provide some guidance on where the network driver or interface to
network driver is located within BATMAN?

Regards,
Charles

-----Original Message-----
From: Sven Eckelmann <sven@narfation.org> 
Sent: Friday, June 17, 2022 1:46 AM
To: cchien@creonexsystems.com
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: Question about batman for ARM

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.

Kind regards,
	Sven


  parent reply	other threads:[~2022-06-20 10:20 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
2022-06-20 10:20         ` cchien [this message]
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='014301d8848f$5874d0b0$095e7210$@creonexsystems.com' \
    --to=cchien@creonexsystems.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --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