14 Sep
2014
14 Sep
'14
11:06 p.m.
I don't know any con yet :) But we should see about the performance of both and
compare.
The layer1 (11s) links you with the direct neighbors, the layer2 is batman-adv but only
for your local cloud or neighborhood, then the layer3 (bmx6) attach all the clouds in a
single big routed network.
On 14/09/14 01:59, Charles N Wyble wrote:
On 9/13/2014 5:48 AM, Pau wrote:
--
./p4u
Hi.
Using 11s instead of adhoc for deploying our mesh networks can bring
some interesting features, among others:
1. Better support for 11n
2. Better compatibility with drivers (probably even ath_htc works fine)
3. You can bridge it to another interface if necessary.
4. It does NOT try to synchronize the TSF counter of your wifi card thus
you can create up to 8 11s VAP mixed with adhoc, AP, client, etc...
5. I don't know deeply 11s but it probably has better design for
deploying mesh networks
I like the pros.
What are the cons?
I've been testing it in a 12 nodes mesh network mixing it with bmx6 and
it worked as a charm. No more "strange" problems coming from the adhoc
layer.
Very nice.
Yesterday Gio the great added support for 11s in libre-mesh [1]. So now
we only need to test it a bit more with our already crazy network
architecture, so it may became even a bit more crazy for traditional
mesh folks (bmx6+bat-adv+11s, never done something like that!).
So 11s would be layer1, bat-adv l2, bmx6 l3 ?
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev