Hi,
From the beginning, I am using batman-adv 3.2 compiled along with batctl.
batman-adv 3.2 ? I guess you mean 0.2 ?
$ insmod batman-adv.ko $ iwconfig wlan0 mode ad-hoc essid BATMAN_NET $ echo wlan0 > /proc/net/batman-adv/interfaces $ ifconfig wlan0 192.168.1.xxx up $ ifconfig bat0 up
The wlan0 device does not need an IP address. It needs to be up & running but the IP goes on the bat0 device.
I get a new bat0 interface, iwconfig shows nodes properly part of the ad-hoc network. I see correct $batctl o output but i cannot $batctl ping $mac_address
Would you mind showing us the batctl o output and the batctl ping call plus error message(s) ?
There are no bridges between interfaces. I just want to run batman-adv on wlan0. Do I need to set an IP address for wlan0, for bat0 or for both? Or I have to bridge bat0 and wlan0 together?
No, don't bridge bat0 and wlan0. Imagine you had another wifi interface in managed mode for non-batman nodes to connect to (e.g. wlan1). Then you would want to make the mesh accessible for the managed clients by bridging bat0 with wlan1.
Regards, Marek