There's a lot I'd like to learn about mesh networking. I thought I'd collate the questions I have floating in my head out here along with references to relevant discussions I've come across on various mailing lists.
I plan to keep updating this list as I discover relevant information or find myself dwelling on further questions.Hopefully this would help someone else too and hopefully someone reading this can offer pointers in the right direction :)
How should IP addresses be assigned in a pure ad-hoc (multipoint to multipoint) mesh network?
The prerequiste here is an automated mechanism with minimal user intervention, static assigned IPs are undesireable.
Useful references and discussion on this topic:
http://www.mail-archive.com/b.a.t.m.a.n@lists.open-mesh.org/msg01951.html http://ml.ninux.org/pipermail/battlemesh/2011-April/000729.html
Interesting resources/solutions recommended by others:
Zeroconf: http://en.wikipedia.org/wiki/Zeroconf
Avahi: http://en.wikipedia.org/wiki/Avahi_(software)
Dynamic Configuration of IPv4 Link-Local Addresses: http://tools.ietf.org/html/rfc3927
IPv6 Stateless Address Autoconfiguration: http://tools.ietf.org/html/rfc4862
How can we map the proximity of different nodes in the mesh and approximate their throughput?
Do OLSR and other protocols allow us to deduce which nodes are closer (1 hop) and which are further (> 1 hop)? How does this information translate to actual throughput we can expect from these nodes?
Discussions:
http://lists.olsr.org/pipermail/olsr-dev/2011-April/004431.html
Power management/optimization of devices in ad-hoc mode
As the above discussion also mentions, simply putting a mobile device in ad-hoc mode in devices based on Android,etc often disables power management features and causes devices to drain, regardless of routing protocols like olsr,batman,etc are running. What mechanisms can be put in place to optimize power management for devices in ad-hoc mode.