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
DEAUTH/REMOVE)
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
wifi disconnects.
I tried also reflashing firmware and same issue.
How can i proceed?
Regards.
Gabriel
--
*Gabriel H. Giovaniello*
*+54 2216230146*
@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
> scenarios.
>
>
> abrazos,
> Nico
>
>
> _______________________________________________
> Dev mailing list
> Dev(a)lists.libre-mesh.org
> https://lists.libre-mesh.org/mailman/listinfo/dev
>
--
./p4u
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*,
https://chef.altermundi.net/downloads/ib/r42398/ar71xx/
then prepared an image for *DeltaLibre* with that
https://chef.altermundi.net/fwprofile/deltalibreorgar-r42398/
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)
http://libremap.net/#bbox/-34.40620151141123,-58.57924103736878,-34.4006246…
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
http://libremap.net/#bbox/-34.419973858189636,-58.56451034545898,-34.408821…
giving a current total of 17 lime-based nodes, servicing real people
everyday
this is the WAN port traffic at the gateway in the 9 LiMe-Full cloud
http://status.red.libre.social/graphs/type=port_bits/id=216/
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
http://article.gmane.org/gmane.network.ssh.dropbear/1573https://lists.openwrt.org/pipermail/openwrt-devel/2014-September/027815.html
[0]: 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
>
--
./p4u
Hi!
I just discovered this other SoC style funding [0], didn't readed much yet but
it seems interesting, are we interested?
[0] http://vps.semesterofcode.com/
Hi!
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
users(a)lists.libre-mesh.org
?
Thanks,
Ilario
--
Ilario Gelmetti
iochesonome(a)gmail.com
ilario.gelmetti(a)sns.it
Why do we have a dash "-" in the name of Libre-Mesh and in the name of
the site?
I suggest to register also libremesh.org (without dash) before someone
else does.
Bye,
Ilario
--
Ilario Gelmetti
iochesonome(a)gmail.com
ilario.gelmetti(a)sns.it
Is this normal?
5 of these interfaces have mac address dc:9f:db:30:c1:36
1 of these interfaces has mac address de:9f:db:30:c1:36
I'm using Libre-Mesh compiled with lime-build yesterday.
Ciao,
Ilario
10: wlan0_adhoc: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1536 qdisc mq
state UP group default qlen 1000
link/ether dc:9f:db:30:c1:36 brd ff:ff:ff:ff:ff:ff
inet6 fe80::de9f:dbff:fe30:c136/64 scope link
valid_lft forever preferred_lft forever
11: wlan0_adhoc-11@wlan0_adhoc: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu
1500 qdisc noqueue master bat0 state UP group default
link/ether dc:9f:db:30:c1:36 brd ff:ff:ff:ff:ff:ff
inet6 fe80::de9f:dbff:fe30:c136/64 scope link
valid_lft forever preferred_lft forever
12: wlan0_adhoc-13@wlan0_adhoc: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu
1398 qdisc noqueue state UP group default
link/ether dc:9f:db:30:c1:36 brd ff:ff:ff:ff:ff:ff
inet6 fd66:66:66:c:de9f:dbff:fe30:c136/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::de9f:dbff:fe30:c136/64 scope link
valid_lft forever preferred_lft forever
14: wlan0_ap: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master
br-lan state UP group default qlen 1000
link/ether de:9f:db:30:c1:36 brd ff:ff:ff:ff:ff:ff
inet6 fe80::dc9f:dbff:fe30:c136/64 scope link
valid_lft forever preferred_lft forever
15: wlan0_ap-11@wlan0_ap: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500
qdisc noqueue master bat0 state UP group default
link/ether dc:9f:db:30:c1:36 brd ff:ff:ff:ff:ff:ff
inet6 fe80::de9f:dbff:fe30:c136/64 scope link
valid_lft forever preferred_lft forever
16: wlan0_ap-13@wlan0_ap: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1398
qdisc noqueue state UP group default
link/ether dc:9f:db:30:c1:36 brd ff:ff:ff:ff:ff:ff
inet6 fd66:66:66:10:de9f:dbff:fe30:c136/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::de9f:dbff:fe30:c136/64 scope link
valid_lft forever preferred_lft forever
--
Ilario Gelmetti
iochesonome(a)gmail.com
ilario.gelmetti(a)sns.it
I added some debug output,
(logs output to /tmp/lime-config.log on firstboot run)
and most importantly basic error handling to lime-config,
so that the whole script does not die if
a single module has a bug. Example result:
root@LiMeNode-ee01b4:/# cat /tmp/lime-config.log
Configuring LiMe for first boot...
Clearing wireless config...
Clearing network config...
Disabling odhcpd
Cleaning dnsmasq
Disabling 6relayd...
Adding macvlan interface to uci network...
Clearing bmx6 config...
/usr/lib/lua/lime/network.lua:17: 2
stack traceback:
/usr/lib/lua/lime/network.lua:142: in function </usr/lib/lua/lime/network.lua:142>
[C]: in function 'assert'
/usr/lib/lua/lime/network.lua:17: in function 'get_mac'
/usr/lib/lua/lime/proto/batadv.lua:29: in function 'setup_interface'
/usr/lib/lua/lime/network.lua:141: in function </usr/lib/lua/lime/network.lua:141>
[C]: in function 'xpcall'
/usr/lib/lua/lime/network.lua:141: in function </usr/lib/lua/lime/network.lua:110>
[C]: in function 'xpcall'
/usr/bin/lime-config:17: in function 'main'
/usr/bin/lime-config:21: in main chunk
[C]: ?
/usr/lib/lua/lime/network.lua:17: 2
stack traceback:
/usr/lib/lua/lime/network.lua:142: in function </usr/lib/lua/lime/network.lua:142>
[C]: in function 'assert'
/usr/lib/lua/lime/network.lua:17: in function 'get_mac'
/usr/lib/lua/lime/proto/batadv.lua:29: in function 'setup_interface'
/usr/lib/lua/lime/network.lua:141: in function </usr/lib/lua/lime/network.lua:141>
[C]: in function 'xpcall'
/usr/lib/lua/lime/network.lua:141: in function </usr/lib/lua/lime/network.lua:110>
[C]: in function 'xpcall'
/usr/bin/lime-config:17: in function 'main'
/usr/bin/lime-config:21: in main chunk
[C]: ?
Configuring system...
Let uhttpd listen on IPv4/IPv6
###### uci changes generated by lime-config run: ######
batman-adv.bat0=mesh
batman-adv.bat0.bridge_loop_avoidance=1
batman-adv.bat0.multicast_mode=0
batman-adv.bat0.distributed_arp_table=0
bmx6.general=bmx6
[...]
in this particular case, the errors are due to trying to get network.get_mac from a wlan0_ap interface which doesn't exist yet on firstboot.
So, this new debug possibility is already proving veeery useful :)
will push this branch in a bit, after rebasing and tidying things up
Hi,
I installed the new image from download.libre-mesh.org, for the 703n issued on 5 August. The name of the image is sounding fine, however once installed, the router seems to run a regular openwrt binary, no LiMe flavour.
Seems that some things are missing or did I?
