From: Sven Eckelmann <sven@narfation.org>
To: cchien@creonexsystems.com
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: Question about batman for ARM
Date: Mon, 20 Jun 2022 14:50:54 +0200 [thread overview]
Message-ID: <20961862.b4RiU9qLUR@ripper> (raw)
In-Reply-To: <014301d8848f$5874d0b0$095e7210$@creonexsystems.com>
[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]
On Monday, 20 June 2022 12:20:19 CEST cchien@creonexsystems.com wrote:
> Does BATMAN ADV interfaces with the radio via the network driver or does
> BATMAN include the network driver?
As said before, it is interfacing with the generic ethernet netdev layer of
the kernel. For example in:
* https://git.open-mesh.org/batman-adv.git/blob/caa1eb0cf7bf8ebfe43bba06b890252a865efa91:/net/batman-adv/hard-interface.c#l727
* https://git.open-mesh.org/batman-adv.git/blob/caa1eb0cf7bf8ebfe43bba06b890252a865efa91:/net/batman-adv/send.c#l108
* https://git.open-mesh.org/batman-adv.git/blob/caa1eb0cf7bf8ebfe43bba06b890252a865efa91:/net/batman-adv/hard-interface.c#l185
There are a lot of other places when it uses the abstraction interfaces of the
kernels for ethernet related communication.
For B.A.T.M.A.N. V, it is also trying to get throughput information via
various generic kernel functionality:
* https://git.open-mesh.org/batman-adv.git/blob/caa1eb0cf7bf8ebfe43bba06b890252a865efa91:/net/batman-adv/bat_v_elp.c#l67
There is also one detection for wifi interfaces to decide whether broadcast
messages should be repeated or not:
* https://git.open-mesh.org/batman-adv.git/blob/caa1eb0cf7bf8ebfe43bba06b890252a865efa91:/net/batman-adv/hard-interface.c#l877
> Can you provide some guidance on where the network driver or interface to
> network driver is located within BATMAN?
It is not talking directly to the driver. It is always using abstraction
layers. Either the normal network core, ethernet or cfg80211 abstraction
interfaces. But these don't abstract the requirement for ethernet
compatibility away - the underlying device must provide this either directly
or via a wrapper. Just perform a `git grep -e ETH_ -e eth_ -e ethhdr` to
see that it is build around the concept of ethernet packets.
Also things like originators and the complete translation table only works
with ethernet addresses.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-20 12:50 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
2022-06-20 12:50 ` Sven Eckelmann [this message]
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=20961862.b4RiU9qLUR@ripper \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=cchien@creonexsystems.com \
/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