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?
Hi!
I wrote some documentation in Italian for Libre-Mesh firmware :)
http://wiki.ninux.org/Libre-Mesh
Bye!!
Ilario
--
Ilario Gelmetti
iochesonome(a)gmail.com
ilario.gelmetti(a)sns.it
This is a braindump while i'm trying to understand the whole mess of
repos and feeds, in addition to lime-build and such, looking forward to
having a libre-mesh release codenamed "bigbang", and the steps we need
in order to do that.
the objective is to have a "snapshot" of everything, so that cloning
lime-build release and running make, will produce the same binary, at
any future time, no matter what happens with 3rd party repos.
* https://github.com/libre-mesh/lime-build.git
starting point, it contains the references to all other repos.
--> Make a staging branch "release/14.08"
* https://github.com/libre-mesh/lime-packages.git
(referenced in lime-build/feeds.conf)
libre-mesh packages.
--> Make a staging branch "release/14.08"
then, other repos we cloned and "snapshotted":
* https://github.com/libre-mesh/openwrt.git
(referenced in lime-build/config.mk)
base openwrt buildroot.
cloned from git://git.openwrt.org/openwrt.git
--> Make an immortal branch "release/14.08"
* https://github.com/libre-mesh/openwrt-packages.git
(referenced in lime-build/feeds.conf)
maintained packages feed.
cloned from git://github.com/openwrt/packages.git
original repo has a branch named "for-14.07"
--> Make an immortal branch "release/14.08" tracking "for-14.07"
* https://github.com/libre-mesh/openwrt-oldpackages.git
(referenced in lime-build/feeds.conf)
old packages feed.
cloned from git://git.openwrt.org/packages.git
--> Make an immortal branch "release/14.08"
* https://github.com/libre-mesh/openwrt-routing-packages.git
(referenced in lime-build/feeds.conf)
cloned from git://github.com/openwrt-routing/packages.git
original repo has a branch named "for-14.07"
--> Make an immortal branch "release/14.08" tracking "for-14.07"
* https://github.com/libre-mesh/openwrt-luci.git
(referenced in lime-build/feeds.conf)
cloned from git://git.openwrt.org/project/luci.git
--> Make an immortal branch "release/14.08"
* https://github.com/libre-mesh/libremap-agent.git
(referenced in lime-build/feeds.conf)
cloned from git://github.com/libremap/libremap-agent-openwrt.git
--> Make an immortal branch "release/14.08"
i know this means a loooot of repos that we have to "maintain" on our
own (in a way), but:
* it's the only method to have something that we control completely
* normally they will be just mirrors of the original repo, and pulling
changes from upstream should be as easy as "git pull upstream ; git push
github-lime"
not all of those repos were mirrored, and currently lime-build is
pointing at the original (upstream) repos. I'll fix that in a minute.
also, i changed the "default" branch of lime-packages to *develop*, to
make development progress more visible.
so now if you git clone lime-packages, you'll get bleeding edge code,
unless you checkout "stable" branch (i.e. what was previously called
master) or some particular release
while this deviates just a little bit from nvie "gitflow" branching
model, i think it is aligned with what people expect when looking at a
github repo.
Hello.
I've updated the git repository for the openwrt packages snapshot in
lime-build. Merge was very problematic because OpenWRT developers are
splitting the repositories, so I had to remove, create and mirror it
again. Unfortunately, this new repository is not compatible with the
old, so if you are using lime-build you should do:
cd lime-build
git pull
rm -rf build/trunk-packages
rm .checkout_owrt_pkg
make update_all
The packages feed was completely broken, so it is recommended to rebuild
again.
Cheers.
--
./p4u
Hi.
Yesterday I set up a server with generic pre-compiled images for
LibreMesh. Find it here: http://downloads.libre-mesh.org/
ToDo: Set up the nightly compile, so we will have fresh compiled images
every night if there is some change in the code
--
./p4u
Hi everyone,
I’ve some problems to set up the 1043nd using the pre-compiled images of pau. For the two 703n, they are working out of the box.
I’m not able to get a ip address over ethernet, also joining the lime SSID is buggy (shortly after obtaining an IP address, mac os is reporting that there are some issues, well could be also a strange osx behaviour…).
I managed to get a access to web gui over wifi. The mesh is working. I tried to compare the different configs (703n and 1043nd). They are more or less the same. As Pau recalled me, often the switch section is difficult to get working.
So: WAN got an ip address from my local network an Port 2 (connected to my computer) is for vlan id 1 : untagged / vlan 2 id 2 : off. I’ve no idea what’s wrong, my technical background for this is limited.
Btw, currently I’m working on my bachelor thesis (UAV communications) and so libremesh fits perfect for my use.
Thank you,
max
On Aug 1, 2014, at 2:00 PM, dev-request(a)lists.libre-mesh.org wrote:
> Send Dev mailing list submissions to
> dev(a)lists.libre-mesh.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.libre-mesh.org/mailman/listinfo/dev
> or, via email, send a message with subject or body 'help' to
> dev-request(a)lists.libre-mesh.org
>
> You can reach the person managing the list at
> dev-owner(a)lists.libre-mesh.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Dev digest..."
>
>
> Asuntos del día:
>
> 1. downloads.libre-mesh.org (Pau)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 01 Aug 2014 13:45:00 +0200
> From: Pau <pau(a)dabax.net>
> To: libre-mesh <dev(a)lists.libre-mesh.org>
> Subject: [lime-dev] downloads.libre-mesh.org
> Message-ID: <53DB7DBC.2090102(a)dabax.net>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi.
> Yesterday I set up a server with generic pre-compiled images for
> LibreMesh. Find it here: http://downloads.libre-mesh.org/
>
> ToDo: Set up the nightly compile, so we will have fresh compiled images
> every night if there is some change in the code
> --
> ./p4u
>
> ------------ próxima parte ------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 473 bytes
> Desc: OpenPGP digital signature
> URL: <http://lists.libre-mesh.org/pipermail/dev/attachments/20140801/d36a0d3d/att…>
>
> ------------------------------
>
> _______________________________________________
> Dev mailing list
> Dev(a)lists.libre-mesh.org
> https://lists.libre-mesh.org/mailman/listinfo/dev
>
>
> Fin de Resumen de Dev, Vol 16, Envío 1
> **************************************
