Signed-off-by: Marek Lindner <lindner_marek(a)yahoo.de>
README | 13 +++++++------
1 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/README b/README
index a9ae038..7bcc9f4 100644
@@ -83,9 +83,9 @@ All mesh wide settings can be found in batman's own interface
# ls /sys/class/net/bat0/mesh/
-# aggregated_ogms gw_bandwidth hop_penalty
-# bonding gw_mode orig_interval
-# fragmentation gw_sel_class vis_mode
+# aggregated_ogms fragmentation gw_sel_class vis_mode
+# ap_isolation gw_bandwidth hop_penalty
+# bonding gw_mode orig_interval
There is a special folder for debugging information:
@@ -219,15 +219,16 @@ abled during run time. Following log_levels are defined:
0 - All debug output disabled
1 - Enable messages related to routing / flooding / broadcasting
-2 - Enable route or tt entry added / changed / deleted
-3 - Enable all messages
+2 - Enable messages related to route added / changed / deleted
+4 - Enable messages related to translation table operations
+7 - Enable all messages
The debug output can be changed at runtime using the file
# echo 2 > /sys/class/net/bat0/mesh/log_level
-will enable debug messages for when routes or TTs change.
+will enable debug messages for when routes change.
i thought it was a good idea to move the functions "start_mesh" and
"stop_mesh" from /etc/init.d/batman-adv script to a new file in
openwrt style "/lib/batman-adv/config.sh".
With this improvment it possible to recycle this two function to
operate with an hotplug script so when network restart, all batman
interface will be reconfigured automatically and I just work to do
In this mail you can find batman-adv initscript updated to work in
this way and the batman-adv library file that must be located in
Any comment are apprecciated
i have setup a mesh-network with batman-adv running on about 10 Foneras
and 4 TP-Link on OpenWRT.
At first everything seemed to work. A node on the one end could ping a
node on the other end over the mesh-network. The ping was hopping from
node to node as expected.
But sometimes some paths do not work anymore.
Some nodes can only reach their direct neighbors via a "normal ping". A
ping to a node via one hop does not work. A "batctl ping" does work!
This only happens to parts of the network and is not permanent. If i
wait it will recover, but then the problem appears at another node.
dmesg or the syslog does not report any errors.
Can anyone give me a hint where to look?
as most of us are concentrating batman-advanced now, Marek suggested
that we should create a new logo for our next generation mesh technology. ;)
The "old" ascii logo is still great, but most people associate it with
the layer 3 BATMAN ...
Therefore, I made some sketches and would like to ask for opinions from
the list. Any comments, suggestions, criticism are welcome. My current draft
is this one:
you can find some more sketches here (maybe you like another sketch more ...):
looking forward to your feedback,
I don't known if this is a old argument but exsist the possibility to
implement a secure mesh network?
For example a tecnique that crypt batman-adv traffic with a preshare
key or similar or
using ebtables to block all INPUT and OUTPUT traffic and allow only
the specified nodes mac?
EXTRA_CFLAGS is deprecated since v2.6.23-2309-gf77bf01 and should not be used
anymore to add additional flags for the c compiler.
Signed-off-by: Sven Eckelmann <sven(a)narfation.org>
Makefile.kbuild | 4 ++--
README | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Makefile.kbuild b/Makefile.kbuild
index 6377c17..bd7e93c 100644
@@ -25,10 +25,10 @@ ifeq ($(MAKING_MODULES),1)
-# EXTRA_CFLAGS += -DCONFIG_BATMAN_ADV_DEBUG
+# ccflags-y += -DCONFIG_BATMAN_ADV_DEBUG
-EXTRA_CFLAGS += -DSOURCE_VERSION=\"$(REVISION)\"
+ccflags-y += -DSOURCE_VERSION=\"$(REVISION)\"
obj-m += batman-adv.o
diff --git a/README b/README
index 1e000ee..5ba56b5 100644
@@ -1,4 +1,4 @@
@@ -206,7 +206,7 @@ option "B.A.T.M.A.N. debugging". When compiling outside of the
kernel tree it is necessary to edit the file Makefile.kbuild and
uncomment the line
-#EXTRA_CFLAGS += -DCONFIG_BATMAN_ADV_DEBUG
+#ccflags-y += -DCONFIG_BATMAN_ADV_DEBUG
Those additional debug messages can be accessed using a special
file in debugfs
we are using the following configuration in our freifunk network:
B.A.T.M.A.N. advanced 2011.0.0 (compatibility version 12)
ath1 (ad-hoc) as batman-adv-interfaces
ath0 (ap), tap0, eth0.1 and bat0 as a bridge
stp is enabled for the bridge.
Most of the nodes are connected via tinc and the network runs fine. But if two
nodes which have a tinc connection also get a ath1-connection, the whole
What are we doing wrong?
bjo.nord-west.org | nord-west.org | freifunk-ol.de