On Saturday 13 June 2015 19:17:57 Carlos Meralto wrote:
Thanks for the answer Sven.
You can patch the driver to allow this (it is just a simple check which disallows it in most drivers... or actually in wireless core [1]). But you should make sure that you still use the same mac addresses for vif + bridge and don't end up with 4 address packets.
Can you explain how I can apply this "patch”? I saw the file attached but i don't know what parameters must change.
You have to modify this file or similar ones yourself to avoid that it sets IFF_DONT_BRIDGE. And then you have to recompile your kernel with your patch and run it - but you should be aware that this is only a hack. It was already discussed on this mailing list how the wifi stack avoids that the bridge accepts specific types of interfaces [1].
You should also find in this thread a patch [2] which shows how some ebtables functionality could in theory also be added to something like batman-adv. You should be aware that this is not in the upstream version because it is considered not acceptable by the Linux networking subsystem maintainer.
You should also be aware that it is problematic to test to different protocols by using two different, protocol/implementation specific ways to force them to a specific topologies.
Kind regards, Sven
[1] https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2010-May/002718.html [2] https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2010-May/002731.html