25 May
2016
25 May
'16
1:08 p.m.
On 25/05/16 09:55, Daniel Golle wrote:
Hi!
Thanks for building that great set of packages enabling (almost)
stateless autoconfiguration mesh routers! I hope to use all that in my
local freifunk environment; many people here are interested in LIME and
I'll help getting it to interoperate with our local legacy OLSRv1 mesh
and the way we use batman-adv... My main goal is to start collaboration
(software development, bug fixing, ...) beyond the local firmware
projects which are either half-abandonned or do not offer anything near
to how lime's webui is enabling new people to get into the story and of
course, none of them (meshkit, gluon, ...) are truely modular and/or
offer good support for more than the single routing protocol they were
originally written for. It should also be easy to have some
meta-packages in LIME which would select the packages needed for
typical freifunk OLSRv1 and/or batman-adv setups (expect pull-requests
for that to hit your github repo soon).
However, while preparing the switch to libremesh some questions and
oddities arrised.
I'm building from source, ie. enabled lime-packages and libremap feeds.
I can't use the binaries as most of the hardware I use is unsupported
or works really bad on BB.
Questions which came up for now:
* what's missing to run LibreMesh on more recent versions of OpenWrt?
A lot of hardware was added since BB and certainly won't waste time
backporting stuff to BB, but rather spend it on helping to get LIME
run on bleeding-edge LEDE or at least OpenWrt's CC release (as people
will still be backporting hardware support for CC for a while...)
try https://github.com/libre-mesh/lime-build/tree/develop (it's based on
CC), that will turn into a release soon
* http://chef.libre-mesh.org is unavailble...
what's supposed to be
there and how to bring it back?
mmh, dns is unset for some reason
anyway it points to http://chef.altermundi.net
* lime-eb-ip-tables: why not use fw3?
personal preferences :P
in my case, i do install and use fw3, but other devs prefer not to
bundle the firewall, so we give the option
(i.e. if you install fw3 everything will work as well and be integrated
as expected)
* why redundantly create per-device images instead of
just using
OpenWrt/LEDE ImageBuilder? ie. the downloads here
http://downloads.libre-mesh.org/firmware/
are hard to understand for outsiders, also for long-term OpenWrt
hackers like myself. E.g. for which hw-revision is supported by the
image for the TL-WR841N(D)?
good point :)
currently, pau is the only one vouching for custom renaming,
i'm personally against, and Gio i think doesn't really care
I had that build-a-wrapper vs.
use-OpenWrt-SDK-and-ImageBuilder
debate a bunch of times and I'm sure that most people building
wrappers just don't know what they are missing and/or how much extra
work they have to go through compared to just using OpenWrt/LEDE in
the way it was meant to be used...
totally agree, but doing a project together involves trying to reach
consensus, and when that's impossible, concessions :)
* How can I reproduce the way the images on
downloads.libre-mesh.org
have been built (ImageBuilder? List of packages/files added/removed)?
it's supposed to be a simple "git clone lime-build ; cd lime-build ;
make", but Pau can clarify
I'll certainly have more questions soon :)
keep them coming! :D
Cheers
Daniel