On Wednesday, February 18, 2015 13:28:27 Andreas Pape wrote:
I adapted your patch to batman-adv-2014.4.0 without success. I got the additional issue that with the patched version of batman-adv I was not able to destroy the virtual wireless interface anymore used fot the adhoc connection over which I try to use batman-adv (error message was: unregister_netdevice: waiting for ath0 to become free).
It is very possible that the supplied patches have side effects. Right now, I am trying to figure out which part of the code introduced with 2013.2.0 causes the malfunction. I prepared some more patches which deactivate more code, most notably rtnl code added with 2013.2.0. Please give it a try and let me know how it goes.
With the unpatched 2014.4.0 I did the following test on two of my devices:
- created a virtual wireless interface ath0 in adhoc mode
- iwconfig ath0 essid TEST
- iwconfig ath0 channel 40
- ifconfig ath0 up
- batctl if add ath0
After this the two devices connected and I could see the repective neighbor via the batctl o command on both devices. So far so good.
At this point the mesh is working to your expectation ? Can you transport payload across the mesh ? If so, this is a deviation from #173 - wouldn't you agree ?
But I can see via batctl td bat0 OGM packets sent with the MAC address of the wlan interface of the device itself and also from the neigbour this device is connected to via wlan. Is this OK?
Yes, batman-adv continues to use the mac addresses of the interfaces you configure.