Since it's not standardized, isn't it more logical to proceed with either
user-space implementation or kernel implementation of something that has
RFC assigned to the name (just asking, no troll/flame here)? Other than
that I have some experience with BMX, Babel and OLSR. Also, i'm personally
not convinced that kernel level implementation is the most appropriate
choice for routing protocol (still i may be wrong).
> >> Are there any reasons to choose B.A.T.M.A.N. instead of bmx or babel?
> ... or
> >> OLSR? ... or HSLS?
> > I've seen BATMAN work at a local Linux club meeting, and I was pretty
> > much impressed by how easy it is to setup. I don't know about the
> > other protocols you listed, but BATMAN is in the stock Linux kernel,
> > making it a practical choice. I might be wrong but it seems to me that
> > it, contrasted to 802.11s, requires no special support from the wifi
> > driver side, making it easier to implement. Other than that, no, I
As mentioned already 802.11s is link-layer technology (that from our
experiments and research seems to be limited to some 30 devices), in
contrast those are network layer (L3) protocols that operate on top of IP.
I think it a better version of the Optimized Link State Routing
> Protocol (OLSR) which is an IP routing algoritm, 802.11s is link level
> routing, which needs a wifi driver that permits changing the mac
> But there is no standard for it I think.