Hello Wu,
you can set an IP address on the bat0 interface, or include it in a bridge with eth0 or other devices which are not used for the mesh. You might as well use DHCP to provide addresses to your nodes (which is not possible with layer 3 daemons, btw). You don't need to set IP addresses of the "base interfaces" which are used by batman - just make sure they are up (ifconfig wlan0 up). The bat0 interface can be used like any other ethernet-compatible network interface - you can consider it as port to a virtual distributed switch.
best regards, Simon
On Wed, Dec 16, 2009 at 01:13:47AM +0800, wu xiaofei wrote:
Thank you for your reply! I just used olsrd. I am a newbie for BATMAN. I want to try it.
From open-mesh.net and your description I almost know batman-adv is on layer 2 . But some applications need IP addresses, so use DHCP server to allocate IP address in the same network, or config manually? Could you give me a guide document about setting and config steps of a mesh network (about 30 nodes) using batman-adv in detail.
in "README" : # insmod batman-adv.ko # echo wlan0 > /proc/net/batman-adv/interfaces The module will create a new interface 'bat0'
What's the difference between 'wlan0' and 'bat0'? Should I bridge the non-batman interface (e.g. eth0 ...) with bat0 or wlan0 ? config the IP address of wlan0 , bat0 separately ?
-- Wu
B.A.T.M.A.N mailing list B.A.T.M.A.N@lists.open-mesh.net https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n