I am using batman (2012) for a wireless network where we have a polling based or star type network /mac topology. Similar to wifi PCF but proprietary instead of DCF.
I have noticed that if i have just 2 nodes and one node sends broadcast data (say video 192.168.1.255) that the other batman node will turn around and also re-transmit the same data back out. So basically i see twice the data on the over the air network which the originating batman node drops since it originated from him.
Two Questions: 1) given that there are only two nodes , does BATMAN adv have a way to realize there aren't other nodes wanting to receive the broadcast and since the source of the broadcast is the only other batman node it shouldn't transmit it again?
2) For cases of where batman is used in a more structured network instead of a true mesh/adhoc topology, are there parameters that could be used to limit re-broadcasting data received via wlan interface?
On Donnerstag, 28. Juli 2016 09:04:24 CEST jorge power wrote:
I am using batman (2012)
"batman (2012)"? What's that?
Two Questions:
- given that there are only two nodes , does BATMAN adv have a way to
realize there aren't other nodes wanting to receive the broadcast and since the source of the broadcast is the only other batman node it shouldn't transmit it again?
Sounds like you are interested in the patch from Linus [1] which he send some days ago. Maybe you can check this out and discuss it with him (mbox for the reply is available from patchwork).
- For cases of where batman is used in a more structured network
instead of a true mesh/adhoc topology, are there parameters that could be used to limit re-broadcasting data received via wlan interface?
Are still talking about batman-adv here? Hm, I will just assume that.
There are currently none which can be adjusted manually. There are some people which want to have a no-reproadcast flag [2] (which only solves their problem - and really only theirs and nothing else) but this was postponed until the original author of the patch tests a more general approach.
I also had a patch [3] which splitted the information about the number of re- broadcasts into a "received via this interface" and "received via a different interface" counter for each interface. But this one didn't export the settings to the user. But maybe it can be used as a starting point for whatever you want to do.
Kind regards, Sven
[1] https://patchwork.open-mesh.org/patch/16569/ [2] https://patchwork.open-mesh.org/patch/4384/ [3] https://patchwork.open-mesh.org/patch/15945/
b.a.t.m.a.n@lists.open-mesh.org
-
jorge power -
Sven Eckelmann