On Monday, April 16, 2012 12:46:35 Mitar wrote:
Note: Whoever is going to implement that should think about the implications of mesh clouds periodically connecting and disconnecting. A lot of events could be fired over and over again.
We made such extension to olsrd (which runs given bash script) and I think it is the consumer who needs to take care to aggregate/average those events and so on. Batman logic could be very simple.
If you already have a shell script uevent definitely is the way to go. It is far easier to script than netlink.
How does your logic handle network splits / join ? Do you have the source somewhere ?
You don't need to run another routing protocol "on top" of batman-adv. You only run it to announce "stuff". You can simply run your routing protocol of choice to announce the routes.
Announcing and checking for node reachability, no? And the second part still require some additional bandwidth, no?
Batman would also need to announce the route. What are we saving? How reachability is handled / verified depends on the routing daemon you choose. You could even connect your routing daemon to the uevents mentioned above.
I don't see any benefit of putting this into batman-adv - only a loss of flexibility / choice.
Cheers, Marek