As some of you already know, the last days I have been testing the
possibility of use 802.11s as link layer instead of adhoc.
By default 11s comes with a kind of layer2 routing (same as bat-adv
does) by using HWMP (hybrid wireless mesh protocol) which in general is
quite shitty compared to other well known solutions.
However, if the option mesh_fwding is set to 0, this l2 routing layer is
disabled and 11s can be used just as layer1 protocol in the same level
of Ad-Hoc or AP/Infrastructure.
From OpenWRt these are the needed options to enable 11s as link layer:
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
Yesterday Gio the great added support for 11s in libre-mesh . 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?
Hi, congratulations for this new tool, and your great support.
I’m doing first steps with libre-mesh firmware.
I flashed a WR841nd with dev binary corresponding to that router.
I can connect to router through switch ports and i receive IP but when i
connect through wifi, my connection is kicked.
Here I send Log details of syslog in lime node web interface:
Sat Sep 13 12:18:30 2014 daemon.info hostapd: wlan0_ap: STA
00:1e:c2:b7:f6:42 IEEE 802.11: disassociated
Sat Sep 13 12:18:31 2014 daemon.info hostapd: wlan0_ap: STA
00:1e:c2:b7:f6:42 IEEE 802.11: deauthenticated due to inactivity (timer
Also i receive a list of:
kern.warn kernel: [ 1479.000000] br-lan: received packet on bat0 with own
address as source address
I tried to keep pinging interface but i’m kicked, i tried from 2 different
notebooks and my cellphone and no luck. My ip is assigned and seconds later
I tried also reflashing firmware and same issue.
How can i proceed?
*Gabriel H. Giovaniello*
@Gui, 802.11s have many parameters which can be tunned, we will probably need to understand deeply how it works and make the proper configuration.
I'll ask to open 11s mailing list about this thing, that could give us some good input.
@David, thank you for the document, looks quite good. I think when you disable HWMP this frame is not used thus ignored. Batman-adv adds another ethernet encapsulation which IMO should be able to coexist with 11s.
On 15/09/14 07:05, Nicolás Echániz wrote:
> On 09/14/2014 09:09 PM, Gui Iribarren wrote:
> > On 14/09/14 20:06, Pau wrote:
> >> I don't know any con yet :) But we should see about the performance of both and compare.
> > veeery very promising,
> I would very much like to test/compare network performance in both modes
> on a live network. It sounds promising indeed.
> In particular we have had lots of trouble with highly interconnected
> meshes of >50 nodes; I believe this is more of a wi-fi layer problem,
> but it would be interesting to see if 11s has a positive impact in those
> Dev mailing list
Today is a very happy day, even though i slept only two hours in the
whole weekend :P
after preparing the lime release candidate these past weeks,
with all the *code written by Gio*,
i compiled an imagebuilder from scratch using *p4u's lime-build* ath-ib
uploaded it to *altermundi's chef*,
then prepared an image for *DeltaLibre* with that
and cooked the first *LiMe-based AlterMesh* complete release
flashed that to a pair of lab devices at hand, and after confirming
nothing would blow out badly, i sysupgraded 8 devices in DeltaLibre's
gambado river (where it all started, 3 years ago, and which was still
running one of the first altermesh versions)
everything went out reasonably smooth (i'm still counting how many hours
till i bump into some nasty, ugly ath9k hang :P)
well, to be honest, i spotted already in my table-lab a new ath9k issue,
where 802.11n speeds are not initially negotiated in IBSS VIF, and
apparently starts to work after a wifi reset or something. Didn't care
to debug it much, since i wanted to focus on having LiMe-AlterMesh deployed.
These 8 sysupgraded nodes are not the first ones; the are 9 "LiMe-Full"
nodes in a cloud that has been running since march in angostura river
giving a current total of 17 lime-based nodes, servicing real people
this is the WAN port traffic at the gateway in the 9 LiMe-Full cloud
so, to put it in perspective: even though i haven't touched legacy
AlterMesh code for months, this marks the official abandonment of that
codebase, since we now have an equivalent firmware built with LiMe, as
we had originally planned back in Berlin's WCW 2013 - having achieved
this milestone i want to share a hurray! with you all :D
coding and developing takes some time, yet coordinating efforts between
different communities is incomparably harder, so this determines the
project progress, which then is basically a reflection of the members'
social bonds strength :)
code is just code; insignificant, even ugly code, in comparison to what
happened behind the scenes that originated it
it's no coincidince that during these last few months, Nico, Jesi and I
had the opportunity to share time together, in person so that we could
smell each other (as Isaac coined once :D), as well as Gio and Pau on
their side too, which also helped hold mumble meetings,
or that Al & Gri recently went to Mexico, to materialize the workshops
that (unknowingly to Al) we had informally imagined with Peter Bloom at
the start of the year; then crossing borders to visit SudoRoom, to weave
one more strand in the free networks social fabric ;)
speaking of which, a few days ago surian (from Brasil!) met pau and
gio... and now jow is dropping in the party as well!? you sure are
having fun, so cheers to all \o/ \o/ \o/
ps: (or back to topic?)
while crashtesting the release, i took the time to report two
"pseudoblocker" bugs, not particular to lime; they don't affect the
(clients) end-user experience, but greatly annoy admins work on ssh
sessions and debugging
: lime-altermesh is basically a subset of lime-full that runs only
batman-adv, i.e. without lime-proto-bmx6 and lime-proto-anygw.
Thanks to Gio's work, it was trivial to create the metapackage and have
a fully working firmware equivalent to the old AlterMesh.
I'm not attached to any University if it is what you mean for "academic".
On 15/09/14 11:53, Gioacchino Mazzurco wrote:
> On Monday 15 September 2014 11:51:05 Pau wrote:
> > We should apply as Organization, the dead line is the 17th so we must hurry
> > up.
> > Any volunteer to send the organization subscription? I can do it but it must
> > be done today.
> I believe it is better for non academic of us to be the admins, lets see if
> someother read in time
I think that we need a mailing list for users, like the openwrt-users
mailing list for openwrt.
Is it possible to have something like
Why do we have a dash "-" in the name of Libre-Mesh and in the name of
I suggest to register also libremesh.org (without dash) before someone