No subject

	uci set wireless.mesh0.mode=mesh
	uci set wireless.mesh0.mesh_id=wibed
	uci set wireless.mesh0.mesh_fwding=0

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'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.

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!).

Opinion? Concerns? Ideas?

[1] https://github.com/libre-mesh/lime-packages/tree/feature/80211s

-- 
./p4u