Micha, another freifunker who is testing libremesh at the moment is very
confused about having bmx7 packages when using bmx6 (in developer brunch).
bmx6 is used at the moment, because bmx7 was very unstable in daniels
first setup (also to much packages for 4mb routers)
while daniel was patching that adhoc, micha made some commits, and is
still on testing:
whats your opinion about that problem?
Freifunk Leipzig http://leipzig.freifunk.net
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.
are needed for some of the customization features of chef (but the
lime-defaults file should be up to date with the one in
While *in my opinion* these files should be moved from chef to
somewhere in lime-packages:
Gui, is there some of these files we can skip as won't be useful in
the next stable release?
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: Writing '0' (was 2) to /proc/sys/net/ipv4/conf/all/rp_filter
bmx7: 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
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
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