Hi Marek - > meaning you are maintaining batmand ? Should we change our wiki pages that > claim batmand has no maintainer ?
yes, I am glad to do this. I feel there is room for a simple Layer 3 implementation of Batman beside the exiting batman-adv. And hey, I have started the Batman project with the early bits of this code together with Thomas. Call it nostalgia ;-) And I am also thinking about using a scaled-down batmand version as a proactive mesh protocol for microcontrollers and for shortwave radio meshes with low bandwidth. As a sidenote: I have been playing with batman-adv on the Mesh-Potato, and I will come up with a batman-adv based version of the MP firmware. It opens up a exciting set of new features. Bridging a VAP AP with the LAN port and the bat0 interface is really cool. However I have seen interesting new challenges. For example, if the MPs just get their IP configuration from a DHCP server this eliminates the process of configuring an IP for each device. That is cool. On the other hand, not knowing which IP is assigned to which device introduces new problems. It makes debugging radio problems and hardware issues much harder in the field. So picking up a phone and punching in a static IP via the keypad for each device is not all bad, if you just want to be able to call one MP from the other by dialling the last octet of its IP. Is there a special way of handling IPv4 ARP packets in batman-adv? I figure ARP must be much more robust in a Layer 3 mesh. Cheers, Elektra
