Hello developers,
We’re currently trying to install batman-adv on an ARM platform but we
ran into some issues and we would appreciate your help to answer our
questions below:
Is the batman-adv module compatible with an ARM processor (Raspberry PI 4)?
I’m trying to install batman-adv onto an ARM Raspberry PI 4 with a
Debian based Linux distribution (Pop OS). However, when I run
“modprobe batman-adv”, it returns a FATAL error complaining that the
module is not found in the “/lib/modules” directory. Where can I
find/download the “.ko” for batman-adv for the ARM platform?
And if I need to recompile the .ko file for ARM, is there an online
repository where I can find the original source code for the
batman-adv driver?
--
Regards,
Charles
Dear b.a.t.m.a.n. experts,
I'm reaching batman experts because I would like to know if batman could be used (or alternatives)
in the scope of our SOO framework (https://smartobject.gitlab.io/soo/).
SOO technology is usig a fully de-centralized approach where each local device (called smart object)
may run one or several entities. These entities (that you can consider as particular VMs) are (constantly) broadcast to their neighbours meaning that
a memory snapshot is performed, compressed and sent out (~700 KB - 2 MB). The entities are self-managed in term of lifecycle.
They cannot decide where to go in the network, but they are simply broadcast, and may decide to kill themselves or kill other entities
and stay resideng for further propagation (broadcast).
Smart objects are linked via WiFi and we consider any mesh tolpology of course.
Based on such a model, we do not need any routing, we just need that each local device broadcast their running entities to their neighbours,
which in turn do the same thing to their own neighbours, etc. Of course, we need to taken into aocount "hidden nodes" and
figure out each node does not interfer with other nodes.
In this context, we develop Winenet datalink protocol which relies on unicast and manage a list of neighbour where each
neighbour becomes speaker each at his turn. We observed that using a pure broadcast decreases the bandwidth and is harder to manage.
The protocol also manages hidden nodes.
We guess it is not optimal, it is working but there is still too much latency.
Do you think batman could help us to achieve this kind of broadcast in such a wireless configuration?
Or would you have any suggestion to improve the system?
Many thanks for your help
Kind regards
Daniel
