I am using BATMAN on a raspberry pi b+ with a kernel version of 4.1.13+ but my problem also occured on an older kernel (I tried updating, which did not help). My BATMAN is on batctl debian-2012.1.0-1 [batman-adv: 2015.0].
I try to get the vis_mode up and running, which fails in multiple ways, because I can't even create logs.
sudo batctl loglevel -> "Error - can't open file '/sys/class/net/bat0/mesh/log_level': No such file or directory"
sudo batctl vm -> "Error - can't open file '/sys/class/net/bat0/mesh/log_level': No such file or directory"
and so on. The thing is, when I try:
sudo batmand s -> "Not using interface s (retrying later): interface not active" whereas if I try:
sudo batmand s IP bat0 -> batman cannot be pinged from any other interface any more
did I forget to install something?
Thanks Richard
Hi Richard,
On Thursday 19 November 2015 15:04:56 no name wrote:
I am using BATMAN on a raspberry pi b+ with a kernel version of 4.1.13+ but my problem also occured on an older kernel (I tried updating, which did not help). My BATMAN is on batctl debian-2012.1.0-1 [batman-adv: 2015.0].
please use a recent batctl which matches your version. There are newer debian packages out there, too.
I try to get the vis_mode up and running, which fails in multiple ways, because I can't even create logs.
For vis, please use alfred. Vis is not included in more recent batman-adv versions anymore.
sudo batctl loglevel -> "Error - can't open file '/sys/class/net/bat0/mesh/log_level': No such file or directory"
sudo batctl vm -> "Error - can't open file '/sys/class/net/bat0/mesh/log_level': No such file or directory"
and so on. The thing is, when I try:
sudo batmand s -> "Not using interface s (retrying later): interface not active" whereas if I try:
batmand is not batman-adv. batmand is the original Layer 3 version, while batman-adv is the layer 2 version. batctl only works with batman-adv. I'd suggest to use batman-adv only.
sudo batmand s IP bat0 -> batman cannot be pinged from any other interface any more
did I forget to install something?
I'd suggest to install recent versions of batman-adv and batctl and possibly alfred if you want vis, and deinstall batmand. After that, consider reading our docs again, we have a couple of nice getting started docs. :)
Cheers, Simon
in addition to that see Descriptions here on raspberry pi and installation for Freifunk Networks (which uses many of the tools) you really want to build the tools on the Raspbian (or whatever Distro you have) itself
https://forum.freifunk.net/t/raspberry-pi-fit-fuer-freifunk/8915/8 https://viisauksena.de/blog/raspberry-pi-und-freifunk-freiburg-or-batman-adv... https://cccfr.de/wiki/freifunk:debian
On 19.11.2015 15:04, no name wrote:
I am using BATMAN on a raspberry pi b+ with a kernel version of 4.1.13+ but my problem also occured on an older kernel (I tried updating, which did not help). My BATMAN is on batctl debian-2012.1.0-1 [batman-adv: 2015.0].
I try to get the vis_mode up and running, which fails in multiple ways, because I can't even create logs.
sudo batctl loglevel -> "Error - can't open file '/sys/class/net/bat0/mesh/log_level': No such file or directory"
sudo batctl vm -> "Error - can't open file '/sys/class/net/bat0/mesh/log_level': No such file or directory"
and so on. The thing is, when I try:
sudo batmand s -> "Not using interface s (retrying later): interface not active" whereas if I try:
sudo batmand s IP bat0 -> batman cannot be pinged from any other interface any more
did I forget to install something?
Thanks Richard
b.a.t.m.a.n@lists.open-mesh.org
-
jens -
no name -
Simon Wunderlich