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
> **************************************
so i finally spent a couple of days and resumed working on libre-mesh :D
* first task was to make an "altermesh-system" that would include only
batman-adv, but no bmx6 or anygw magic.
This would not be retrocompatible with legacy altermesh, since batman
versions are incompatible (2012.4.0 vs 2014.2.0) but the setup and
functionality should be similar.
Thanks to the impressive modularization work made by gioacchino all
these past months, it was unexpectedly simple as compiling an image with
lime-system, lime-proto-batadv, and that was it, mostly everything
worked out of the box :D (i didn't even needed to create a metapackage
to test)
So, it is all very very promising! I estimate this week we can have with
nico an "altermesh" cloud running live, but based completely on
libre-mesh codebase.
instead of going ahead and creating the altermesh-system metapackage, i
went back and refactored a little bit of code to tidy things up,
addressing some bad/unexpected details i have been seeing in lime-system
these past months, but didn't have time to fix yet
a quick summary:
* /etc/resolv.conf was overwritten, which kinda break the normal
resolution system
(it should only contain 127.0.0.1, and dnsmasq reads
/tmp/resolv.conf.auto to find out about upstream servers)
now lime-defaults.network.resolvers are copied to
dhcp.(a)dnsmasq[0].server and everything works as expected again
* /etc/uci-defaults/95-lime-init-enable failed with 1 on boot
the whole lime-init unique-in-its-kind hack was split into scripts
placed at the "expected" places: /etc/firewall.user.d/* for iptables or
ebtables stuff, /etc/rc.local.d/* for other hacky stuff.
* iptables -t nat -A POSTROUTING -o $wan -j MASQUERADE
needed to be manually added on gateways. Now the stock firewall system
is back in place, we have the MASQUERADE rule for free.
* dnsmasq-2.66-5 had a hardcoding bug on the dns lifetime announced in
RAs, which triggered clients disconnect and reconnect every 20 mins
(very annoying)
openwrt-BB-rc1 ships with dnsmasq-2.71-3, a version where the bug is
fixed (dns lifetime is now equal to router lifetime)
* reworked dnsmasq-lease-share to use a different approach, instead of
maintaining the leases database, and restarting every 5 minutes (yuck!)
it writes a dhcp-hostsfile, which dnsmasq can re-read without a full
restart.
* found out another shortcoming of the anygw black magic and dnsmasq
white magic: the ra-names feature doesn't work at all in lime-full,
since the icmpv6 packet dnsmasq uses to SLAAC-CONFIRM hosts, goes out
through anygw but comes back through br-lan, and dnsmasq misses it. So,
there's no AAAA resolution at all in lime-full :(
we encountered a similar issue with dhcpv4 but worked around it with
dhcp-needs-broadcast. At some point, we should bump the thread at
dnsmasq-discuss and look for a proper solution.
* the dhcp-hostsfile approach vs leasefile-ro approach: dhcp-hostsfile
has the benefit of not having to do a full restart, but on the other
hand ra-names is not tried at all. Given the previous item / bug,
(ra-names is not working anyway), it's better to stay with
dhcp-hostsfile approach, and avoid dnsmasq restarts.
will continue working tomorrow, but wanted to send huge kudos to gio for
all the work done so far, a heads-up to the rest of the team, and that
i'm back in business :D
cheers!!
gui
Hi.
I've add libre-mesh packages repository to tip4commit.
http://tip4commit.com/projects/804
Maybe we might put the link (or any other thing available in the project
page) to the main web page. So people can make donations using BitCoin.
--
./p4u
Hi all!
I was trying to use a Ubiquiti NanoStation M5 with firmware stock
(AirOS) as a client for a Ubiquiti NSM5 running Libre-Mesh, but when I
do a site survey on AirOS I notice strange things:
if the country code is Italy no LiMe network is displayed [1];
if the country code is Uzbekistan I can see the LiMe network [2].
I put the LiMe network on a channel (40, 5.2GHz) allowed in Italy, so it
should be visible (if you notice, in [1] you can see that 5.2GHz is in
the list of frequencies scanned by AirOS). For reference I added another
NSM5 running OpenWrt in ap mode.
Do you have any idea of why this happens?
Thanks,
Ilario
[1] https://imgur.com/S8etw0y,snjFc9w#0
[2] https://imgur.com/S8etw0y,snjFc9w#1
--
Ilario Gelmetti
iochesonome(a)gmail.com
ilario.gelmetti(a)sns.it
