Hi!
2) bmx6 won the last battlemesh competition.
OK. But this does not mean anything. Winning Battlemesh is a very
abstract term and does not tell much about concrete needs and properties
for the mesh you want to have: max size of the mesh, what features does
the routing protocol have (client roaming), how fast does it converge,
does it support multicast, how does it work with different classes of
traffic (voip vs. bulk). All this things are different things to
consider and it is hard to say that somebody is the best for all of them
because some of things are just design decisions.
3) Yes I'm well aware of the firmware projects and
that they spin
openwrt a certain way. Unfortunately most of them don't push changes
back upstream or use openwrt features to make integration easier
(like feeds).
This is true and is also something I wanted to propose. Using custom
firmware is not a problem (and I personally would encourage it because
it allows you that you learn things and are independent), if you make
all your OpenWrt changes as packages in a Git(Hub) feed. I would also
add that you should think about a way to automatize your
deployment/building of the firmware. OpenWrt has a nice toolchain and
having a script which does everything is really a nice way to develop.
And then things can also be nicely replicable.
4) qmp is used by
guifi.net. They are the largest mesh
network in the
world with 15k+ nodes.
guifi.net is not a mesh network for the most part of the common
understanding of a mesh network. (Links are mostly manually configured,
with the help of their
guifi.net node database. You cannot just move
nodes around and expect things to work.)
6) Actually nodeshot is pretty much the standard for
mapping, used by
pretty much all the mesh projects as a map/dashboard system.
What? Not really.
guifi.net uses its own:
https://www.guifi.net/en/node/2413/view/map
AWMN as well:
http://wind.awmn.net/?page=nodes
In fact there are too many node database and mapping projects around.
Mostly every network develops its own. This is why we tried to
consolidate them together with the
http://interop.wlan-si.net/ project.
And nodeshot is really nicely done. It is a nice idea to have a map as a
central point of the interface. But sadly not really very customizable.
:-( We are working to fix this with the next version of nodewatcher.
Mitar
--
http://mitar.tnode.com/
https://twitter.com/mitar_m