[oc-flyfish]

It still would be difficult to implement though. You would need static routes defined to route traffic to the mesh network, assign IPs, etc. Most people would have no idea how to integrate into their existing network even if they wanted to.

[Myrddin]

You don't need static routes. OLSR has node discovery and sophisticated routing built in. That's why I chose it for my application. The user side can be accomplished with a common wireless access point with its own DHCP server. You would still need some form of DNS service or static host files for well known servers. My application was strictly peer to peer UDP. The set of IP addresses was a well known set. That isn't the case with the Freifunk network in Germany. There are over 40,000 nodes working there. It is used is 3rd world countries to share limited internet connectivity over a broad area

See OLSR research, OLSR code, English Wiki for Freifunk for actual working code, research papers and descriptions of networks currently in place. OLSR supports IPv6 and IPv4. If you use the version of the protocol that evaluates signal strength, that will be factored into the optimal routing. On the railcars, I had the routes updating at 10 times per second. I did that to ensure minimum latency as the packets contained control information for brakes, anglecock valves, cut levers as well as feedback on bearing temperatures, limit switches and control system status off each rail car.