Linus is correct. You cannot bridge the wireless interface with bat0. The wireless interface is managed by bat0. bat0 gets bridged with your lan port(s).
If you remove the line 'option network lan' from /etc/config/wireless it should start working.
I have batman-adv running quite well on both kamikaze and backfire with atheros/madwifi.
I did, however have to play around with MTU settings to get it working at an acceptable throughput. Also, by default, the interface 'wlan0' is in /etc/config/batman-adv and I had to change that to 'ath0' for atheros..
On 1/20/2011 4:52 AM, Linus Lüssing wrote:
On Thu, Jan 20, 2011 at 10:37:47AM +0200, wayne wrote:
Linus Lüssing wrote:
Hi Michael,
You have a bridge loop here, you cannot put an interface into batman-adv and bridge the same one with bat0 again which seems to be the case for wlan0. Packets will enter wlan0, batman will grab them, encapsulate it in its own batman header and send the same packet on wlan0 again, reaching another batman-adv node, which encapsulates the same packet again etc.
Hi All
If I can jump in here, I had the same prob with batman L3 in wrt with the bridge!
Killing the Br-lan bridge kills everything, I eventually solved it by flashing a old kamakaze version : pre bridge version, which provides the simple ,
eth0, eth1 , scenario!
Wayne A
Sorry, but I don't get it, how are the batman-adv and batmand bridge issues related? Why should an older OpenWRT "fix" this? In this scenario I'm 100% that using a different OpenWRT version will _not_ help Michael, as it is a conceptual issue, not a bug or so.
What kind of pre bridge version are you talking about?
Cheers, Linus