Hi.
I've been working on a huge modification for lime-build. The idea was to
simplify it by removing some functions which were not used anymore and
make it more adapted to our current needs. I hope this way we will
manage to use it by default.
I've add a new concept for Profile, which might be for instance:
generic, freifunk or chef (easy configurable in profile.mk). So this
should be enough to compile one of them:
make info
make T=ar71xx P=freifunk
But please, take a look on the README to know more:
https://github.com/libre-mesh/lime-build/tree/v2.0
I've based it on develop, so right now only compiles develop. If
everything works as expected and we all agree, we can migrate the rest
of the branches.
Testing, bugs, pull-request are welcome!
Cheers.
Hey folks,
i just revived the old redmine (that suffered an extended downtime
around may), in order to look for content that needs to be migrated or
recovered,
http://old.libremesh.org (https will give a cert warning since domain
changed)
the site is only meant to recover data, since it will probably be down
again at some point in the future. (i.e. don't link to it)
also it would be great to make a list of URLs and try to make them work
(redirect to relevant content) in the new site, in order to not break
all the links that are already published around pointing to
dev.libre-mesh.org or anything in /projects for example
I can take care of the second idea (say, in a few weeks) with an nginx
redirect table (legacy link -> new location)
but i'd need help for the first (migration), most probably from the
content creators? al, pau, gio, ilario, etc?
cheers!
ps.
Hi all!
As pointed out in the LiMeCat notes, Chef adds to Libre-Mesh a few scripts.
Some of these are needed for Chef to customize the build, some others
should be included in lime-packages if we want lime-build to produce
images as good as the ones from chef.
For example
/etc/uci-defaults/95_add-sshkeys
/etc/config/lime-defaults
/etc/chef_version
are needed for some of the customization features of chef (but the
lime-defaults file should be up to date with the one in
lime-packages).
While *in my opinion* these files should be moved from chef to
somewhere in lime-packages:
/usr/sbin/reset_deaf_phys.sh
/etc/uci-defaults/93_enable-reset-deaf-phys
/etc/config/libremap
/etc/uci-defaults/93_ugly-fixes
/etc/uci-defaults/95_reboot-daily
/etc/uci-defaults/95_snmpd
/etc/uci-defaults/95_set-timezone
/etc/uci-defaults/95_set-remote-syslog
Gui, is there some of these files we can skip as won't be useful in
the next stable release?
Byyee!
Ilario
I'm working in a new look for the libre-mesh web, again based on the
work made in lede-project.org
This time we are using jekyll + asciidoc to generate the pages. So the
syntax will be the same, just the generation of HTML will be different.
Good points are that it is more automatic so more comfortable for
adding/modifying content, more flexible than just using raw asciidoc and
the CSS stuff rocks (web responsive!).
Bad point is that it depends on ruby, gems, bundler and more stuff, but
it is only a server requirement, we can keep editing the pages using
plain text and git.
Here you can visit the current status of it: http://test.libre-mesh.org
Once I finish the migration I'll push it to the lime-web git repository.
Comments, critics, advises are welcome.
Cheers.
Hi!
I'm currently helping to switch from some ancient OLSR1-based
hand-crafted and hard-to-maintain firmware to a Libre-Mesh based
environment. In order to integrate with the existing OLSR1 mesh, some
nodes should run BMX6/7 as well as OLSRd (using 2 devices is not an
option, we just don't have enough of them). While this generally works
nicely due to the routing-table-import features of BMX6, there is a
single very annoying problem:
Both routing daemons try changing sysctl settings in conflicting ways
without any means for the user to disable that 'egocentric' behaviour.
olsrd[21487]: Writing '0' (was 2) to /proc/sys/net/ipv4/conf/all/rp_filter
bmx7[1237]: INFO check_proc_sys_net(): changing /proc/sys/net/ipv4/conf/all/rp_filter from 0 to 2
I generally believe that a routing daemon shouldn't take-over the OS to
a degree which makes co-existence with other routing daemons or other
networking stuff impossible. Currently both, OLSRd and BMX repeatingly
try to enforce settings even in /proc/sys/net/ipv*/conf/all/ which thus
affects all interfaces and not only the ones governed by that specific
protocol.
I had a discussion with Henning about a similar issue I had with OLSRd
changing send_redirects without any way to configure it not to touch
sysctl values. Now the problem came back and kinda confirms my opinion
that setting sysctl options (/proc/sys/net/*) is a task to be carried
out by the OS, ie. netifd on OpenWrt/LEDE or connman or NetworkManager
or whatever-you-use.
Thus my demand to routing protocols developers: Please at least create
a way to tell your routing daemon "don't touch my sysctl, I'll take
care of it myself!". This should imho be the default for the
OpenWrt/LEDE build of the routing daemons and netifd should handle
stuff like rp_filter and send_redirects -- the routing daemon might
still warn you about UCI settings known to cause problems under certain
conditions.
Cheers
Daniel
