Hi
What happens if I add an interface to batman-adv (on which to exchange mesh frames), and add that same interface to a bridge with bat0? E.g. on an openwrt, br-lan contains eth0, bat0 and wlan0; batman-adv is exchanging mesh frames on wlan1 and eth0.
Will I end up with BATMAN-on-BATMAN or will batman-adv filter out the batman frames it sees on bat0?
thanks
donald
Hey Donald,
please don't do that, at least batman-adv will print a warning:
You are about to enable batman-adv on 'eth0' which already is part of a bridge. Unless you know exactly what you are doing this is probably wrong and won't work the way you think it would.
batman-adv won't send any batman-adv frames (it checks for its Ethertype), so batman-on-batman is filtered out, so that is not the problem (can happen in other scenarios as well).
However using an interface as bridge port and something else (batman-adv, IP, etc) is just wrong in any case and will most probably lead to unexpected behaviour. I'd strongly discourage to do that.
You may want to explain your scenario, maybe we can come up with a solution together.
Cheers, Simon
On Tue, Oct 02, 2012 at 09:53:08AM +1300, Donald Gordon wrote:
Hi
What happens if I add an interface to batman-adv (on which to exchange mesh frames), and add that same interface to a bridge with bat0? E.g. on an openwrt, br-lan contains eth0, bat0 and wlan0; batman-adv is exchanging mesh frames on wlan1 and eth0.
Will I end up with BATMAN-on-BATMAN or will batman-adv filter out the batman frames it sees on bat0?
thanks
donald
Hi
(sorry for the very late reply)
On Tue, Oct 2, 2012 at 10:06 AM, Simon Wunderlich simon.wunderlich@s2003.tu-chemnitz.de wrote:
You are about to enable batman-adv on 'eth0' which already is part of a bridge. Unless you know exactly what you are doing this is probably wrong and won't work the way you think it would.
...
You may want to explain your scenario, maybe we can come up with a solution together.
I think what I really want to know is the answer to this question.
In a network with topology:
node 1: bat0 bridged to wired lan 0, over wifi batman can see node 2
node 2: bat0 bridged to wired lan 1, over wifi batman can see nodes 1,3
node 3: bat0 bridged to wired lan 1, over wifi batman can see nodes 2,4
node 4: bat0 bridged to wired lan 2, over wifi batman can see node 3
how will packets from wired lan 0 to wired lan 2 make their way between nodes 2 and 3? Will Batman be able to use the wired link or will they just go through wifi?
thanks
donald
On Friday 16 November 2012 12:04:08 Donald Gordon wrote:
Hi
(sorry for the very late reply)
On Tue, Oct 2, 2012 at 10:06 AM, Simon Wunderlich
simon.wunderlich@s2003.tu-chemnitz.de wrote:
You are about to enable batman-adv on 'eth0' which already is part of a bridge. Unless you know exactly what you are doing this is probably wrong and won't work the way you think it would.
...
You may want to explain your scenario, maybe we can come up with a solution together.
I think what I really want to know is the answer to this question.
In a network with topology:
node 1: bat0 bridged to wired lan 0, over wifi batman can see node 2
node 2: bat0 bridged to wired lan 1, over wifi batman can see nodes 1,3
node 3: bat0 bridged to wired lan 1, over wifi batman can see nodes 2,4
node 4: bat0 bridged to wired lan 2, over wifi batman can see node 3
how will packets from wired lan 0 to wired lan 2 make their way between nodes 2 and 3? Will Batman be able to use the wired link or will they just go through wifi?
Ethernet is not added as interface to bat0? Then it will only use the wifi- links for the mesh because it was told to do so by the person creating the configuration.
Kind regards, Sven
b.a.t.m.a.n@lists.open-mesh.org