So, this release was meant to be announced many months ago (as the
numbering suggests) but lack of coordination (me, gio, pau) delayed it.
In the meantime, some more fixes and improvements were introduced, and
most importantly, several (unpublished) intermediate "release
candidates" have been running for months now, in different community
networks (QuintanaLibre mainly, thanks to persevering NicoEchaniz, and
other smaller deployments)
Highlights are that ieee80211s is used by default (instead of adhoc)
which breaks "backward" connectivity with previous releases,
as well as changes in vlan tagging policy of bmx6 and batadv (which also
are not backwards compatible by default)
most notably, this vlan change fixes a hard-to-debug mtu shrinking bug
that pestered all releases so far (symptoms were varied and bizarre,
like having timeouts when trying to browse certain https sites,
sometimes, on random devices)
the biggest highlight on the dev side, is that we now use upstream SDK
(thanks to dangowrt for pushing this, and pau for implementing it!)
which brings us much closer to LEDE/OpenWrt and allows reporting
upstream ath9k bugs or such, among other benefits
* generic binaries, meant for testing or setting up temporary networks
(i.e. when having the default AP SSID = LibreMesh.org is fine)
http://downloads.libremesh.org/dayboot_rely/17.06/targets/
(build is running right now, binaries should be ready tomorrow for sure)
* for custom builds, the recommended tool at this point is lime-sdk
http://libremesh.org/getit.html#cook_your_own_firmware_using_lime_sdkhttps://github.com/libremesh/lime-sdk
* chef builds are not available at this point. there are plans to
integrate this release into chef in the future, but no ETA :(
###
Most of the following changelog was accomplished during the 2017/03
hackaton (https://www.youtube.com/watch?v=5UX1FwhIKGY)
Changelog Dayboot Rely 17.06 (since 16.07)
* based on LEDE 17.01.2
* build everything using LEDE SDK, via new lime-sdk cooker (instead of
lime-build)
* use ieee80211s instead of adhoc
* reintroduced "firewall" package (to keep closer to upstream)
* lime-system: fix ieee80211s proto, correctly construct ifnames
* lime-system: sanitize hostname (transform everything into
alphanumeric and dash)
* lime-system: new proto static
* lime-system: new wifi mode client
* lime-system: set dnsmasq force=1 to ensure dnsmasq never bails out
* lime-system: explicitly populate /etc/config/lime with calculated values
* lime-webui: enable i18n, finally webinterface is available in Spanish
* lime-webui: Major rework by NicoPace, thanks!
* bmx6 node graph now uses colors in a clever way
* simple way to add "system notes" that are shown along with
/etc/banner and webui
* luci-app-lime-location: fix google maps api key
* new read-only view: switch ports status
* alert luci-mod-admin users that their changes might get
overwritten by lime-config
* fix batman-adv status webui
* new package available to install lighttpd instead of uhttpd (needed
for an upcoming android app)
* added a lime-sysupgrade command: does a sysupgrade but only
preserving libremesh configuration file
* added a lime-apply command: basically calls reload_config, but also
applies hostname system-wide without rebooting
* lime-hwd-ground-routing: ground routing now supports untagged ports too
* lime-proto-anygw: unique mac based on ap_ssid (using %N1, %N2)
* lime-proto-anygw: integrate better into /etc/config/dhcp instead of
/etc/dnsmasq.d/
* lime-proto-wan: allow link-local traffic over wan (useful for local
ping6 and ssh, without global exposure)
* lime-proto-batadv: set batadv gw_mode=client by default to
counteract rogue DHCP servers
* lime-proto-bmx6: introduce bmx6_pref_gw option, adds priority (x10)
to a specific bmx6 gateway
* lime-proto-bmx6: don't tag bmx6 packets over ethernet and so use at
least mtu=1500 everywhere
* lime-proto-bmx6: avoid autodetected wan interface use vlan for bmx6
* bmx6: doesn't flood log with some spurious warnings anymore (syslog=0)
* bmx6: sms plugin now enabled by default
* bmx6: daemon is now supervised by procd, so it is restarted in case
of crashes
* bmx6: doesn't "configSync" by default anymore (no more "uci pending
changes" because of auto-gw-mode)
* new bmx6hosts tool: maintain an /etc/hosts that resolves fd66: <->
hostnames.mesh
* watchping: convert to procd and add reload triggers
* safe-reboot: fix, use /overlay/upper instead of /overlay
* safe-reboot: add "discard" action
* ath9k: debugged some hangs (interface is deaf) and workaround it,
with new package "smonit"
* set wifi default "distance" parameter to 1000 metres and make it
configurable through webui
* alfred: fix bat-hosts facter, check for errors and don't nuke
/etc/bat-hosts in case of failure
* introduce new lime-basic-noui metapackage
* new packages separated: lime-docs and lime-docs-minimal
* various Makefile dependency problems fixed
known bugs:
* safe-reboot: newly introduced "discard" action is half-baked, avoid
usage until next release:
It doesn't check whether there's a backup to restore or not -
https://github.com/libremesh/lime-packages/issues/203
so executing "safe-reboot discard" without having done "safe-reboot"
first, will brick the router.
(unbricking is possible via failsafe boot, and doing "mount_root &&
firstboot")
In the commit log authors you can see the usual suspects ;)
but happily many new names!
https://github.com/libremesh/lime-packages/graphs/contributors?from=2016-09…
and remember it's not only code/commits what matters, so big thanks as
well to everyone participating in mailing lists, maintaining website,
documentation (spread around the web, in many languages!)
hi,
I did a new pull request in lime-web with the translation of howto.
I'm tring also to do a guide of the web interface of LibreMesh.
This is a first idea:
https://uploads.knightlab.com/storymapjs/b6a9a4c44954565a32b64198c73cb6e7/1…
the problem for me is that doc is not to improve, but to write, and I'm
not enough in deep to do these.
Can someone help me.
thanks
Ignifugo
Cooking with this command i get this strange messages, should we mind about
them?
./cooker -c ar71xx/generic --flavor=lime_newui_test --extra-pkg="lime-app
collectd collectd-mod-network collectd-mod-interface collectd-mod-syslog
collectd-mod-load collectd-mod-memory collectd-mod-ping" --
community=NonoLibre/comun --profile=tl-wdr3500-v1
tmp/.config-package.in:7:warning: ignoring type redefinition of
'PACKAGE_busybox' from 'boolean' to 'tristate'
tmp/.config-package.in:27:warning: ignoring type redefinition of
'PACKAGE_dnsmasq' from 'boolean' to 'tristate'
tmp/.config-package.in:101:warning: ignoring type redefinition of
'PACKAGE_firewall' from 'boolean' to 'tristate'
tmp/.config-package.in:122:warning: ignoring type redefinition of
'PACKAGE_jsonfilter' from 'boolean' to 'tristate'
tmp/.config-package.in:166:warning: ignoring type redefinition of 'PACKAGE_libc'
from 'boolean' to 'tristate'
tmp/.config-package.in:194:warning: ignoring type redefinition of
'PACKAGE_libgcc' from 'boolean' to 'tristate'
tmp/.config-package.in:251:warning: ignoring type redefinition of
'PACKAGE_libpthread' from 'boolean' to 'tristate'
tmp/.config-package.in:373:warning: ignoring type redefinition of 'PACKAGE_rpcd'
from 'boolean' to 'tristate'
tmp/.config-package.in:436:warning: ignoring type redefinition of 'PACKAGE_ubus'
from 'boolean' to 'tristate'
tmp/.config-package.in:451:warning: ignoring type redefinition of
'PACKAGE_ubusd' from 'boolean' to 'tristate'
tmp/.config-package.in:465:warning: ignoring type redefinition of 'PACKAGE_uci'
from 'boolean' to 'tristate'
tmp/.config-package.in:1384:warning: ignoring type redefinition of
'PACKAGE_kmod-ath' from 'boolean' to 'tristate'
tmp/.config-package.in:1458:warning: ignoring type redefinition of
'PACKAGE_kmod-ath9k' from 'boolean' to 'tristate'
tmp/.config-package.in:1488:warning: ignoring type redefinition of
'PACKAGE_kmod-ath9k-common' from 'boolean' to 'tristate'
tmp/.config-package.in:1889:warning: ignoring type redefinition of
'PACKAGE_kmod-cfg80211' from 'boolean' to 'tristate'
tmp/.config-package.in:2158:warning: ignoring type redefinition of
'PACKAGE_kmod-mac80211' from 'boolean' to 'tristate'
tmp/.config-package.in:2731:warning: ignoring type redefinition of
'PACKAGE_libiwinfo-lua' from 'boolean' to 'tristate'
tmp/.config-package.in:2746:warning: ignoring type redefinition of 'PACKAGE_lua'
from 'boolean' to 'tristate'
tmp/.config-package.in:2851:warning: ignoring type redefinition of
'PACKAGE_libip4tc' from 'boolean' to 'tristate'
tmp/.config-package.in:2865:warning: ignoring type redefinition of
'PACKAGE_libip6tc' from 'boolean' to 'tristate'
tmp/.config-package.in:2895:warning: ignoring type redefinition of
'PACKAGE_libxtables' from 'boolean' to 'tristate'
tmp/.config-package.in:2964:warning: ignoring type redefinition of
'PACKAGE_libblobmsg-json' from 'boolean' to 'tristate'
tmp/.config-package.in:3065:warning: ignoring type redefinition of
'PACKAGE_libiwinfo' from 'boolean' to 'tristate'
tmp/.config-package.in:3080:warning: ignoring type redefinition of
'PACKAGE_libjson-c' from 'boolean' to 'tristate'
tmp/.config-package.in:3093:warning: ignoring type redefinition of
'PACKAGE_liblua' from 'boolean' to 'tristate'
tmp/.config-package.in:3209:warning: ignoring type redefinition of
'PACKAGE_libnl-tiny' from 'boolean' to 'tristate'
tmp/.config-package.in:3322:warning: ignoring type redefinition of
'PACKAGE_libubox' from 'boolean' to 'tristate'
tmp/.config-package.in:3348:warning: ignoring type redefinition of
'PACKAGE_libubus' from 'boolean' to 'tristate'
tmp/.config-package.in:3361:warning: ignoring type redefinition of
'PACKAGE_libubus-lua' from 'boolean' to 'tristate'
tmp/.config-package.in:3375:warning: ignoring type redefinition of
'PACKAGE_libuci' from 'boolean' to 'tristate'
tmp/.config-package.in:3388:warning: ignoring type redefinition of
'PACKAGE_libuci-lua' from 'boolean' to 'tristate'
tmp/.config-package.in:4329:warning: ignoring type redefinition of
'PACKAGE_luci-base' from 'boolean' to 'tristate'
tmp/.config-package.in:4355:warning: ignoring type redefinition of
'LUCI_LANG_hu' from 'boolean' to 'tristate'
tmp/.config-package.in:4358:warning: ignoring type redefinition of
'LUCI_LANG_pt' from 'boolean' to 'tristate'
tmp/.config-package.in:4361:warning: ignoring type redefinition of
'LUCI_LANG_sk' from 'boolean' to 'tristate'
tmp/.config-package.in:4364:warning: ignoring type redefinition of
'LUCI_LANG_no' from 'boolean' to 'tristate'
tmp/.config-package.in:4367:warning: ignoring type redefinition of
'LUCI_LANG_en' from 'boolean' to 'tristate'
tmp/.config-package.in:4370:warning: ignoring type redefinition of
'LUCI_LANG_el' from 'boolean' to 'tristate'
tmp/.config-package.in:4373:warning: ignoring type redefinition of
'LUCI_LANG_uk' from 'boolean' to 'tristate'
tmp/.config-package.in:4376:warning: ignoring type redefinition of
'LUCI_LANG_ru' from 'boolean' to 'tristate'
tmp/.config-package.in:4379:warning: ignoring type redefinition of
'LUCI_LANG_vi' from 'boolean' to 'tristate'
tmp/.config-package.in:4382:warning: ignoring type redefinition of
'LUCI_LANG_de' from 'boolean' to 'tristate'
tmp/.config-package.in:4385:warning: ignoring type redefinition of
'LUCI_LANG_ro' from 'boolean' to 'tristate'
tmp/.config-package.in:4388:warning: ignoring type redefinition of
'LUCI_LANG_ms' from 'boolean' to 'tristate'
tmp/.config-package.in:4391:warning: ignoring type redefinition of
'LUCI_LANG_pl' from 'boolean' to 'tristate'
tmp/.config-package.in:4394:warning: ignoring type redefinition of
'LUCI_LANG_zh-cn' from 'boolean' to 'tristate'
tmp/.config-package.in:4397:warning: ignoring type redefinition of
'LUCI_LANG_ko' from 'boolean' to 'tristate'
tmp/.config-package.in:4400:warning: ignoring type redefinition of
'LUCI_LANG_he' from 'boolean' to 'tristate'
tmp/.config-package.in:4403:warning: ignoring type redefinition of
'LUCI_LANG_zh-tw' from 'boolean' to 'tristate'
tmp/.config-package.in:4406:warning: ignoring type redefinition of
'LUCI_LANG_tr' from 'boolean' to 'tristate'
tmp/.config-package.in:4409:warning: ignoring type redefinition of
'LUCI_LANG_sv' from 'boolean' to 'tristate'
tmp/.config-package.in:4412:warning: ignoring type redefinition of
'LUCI_LANG_ja' from 'boolean' to 'tristate'
tmp/.config-package.in:4415:warning: ignoring type redefinition of
'LUCI_LANG_ca' from 'boolean' to 'tristate'
tmp/.config-package.in:4418:warning: ignoring type redefinition of
'LUCI_LANG_es' from 'boolean' to 'tristate'
tmp/.config-package.in:4421:warning: ignoring type redefinition of
'LUCI_LANG_pt-br' from 'boolean' to 'tristate'
tmp/.config-package.in:4424:warning: ignoring type redefinition of
'LUCI_LANG_cs' from 'boolean' to 'tristate'
tmp/.config-package.in:4427:warning: ignoring type redefinition of
'LUCI_LANG_fr' from 'boolean' to 'tristate'
tmp/.config-package.in:4430:warning: ignoring type redefinition of
'LUCI_LANG_it' from 'boolean' to 'tristate'
tmp/.config-package.in:4435:warning: ignoring type redefinition of
'PACKAGE_luci-mod-admin-full' from 'boolean' to 'tristate'
tmp/.config-package.in:4540:warning: ignoring type redefinition of
'PACKAGE_luci-theme-bootstrap' from 'boolean' to 'tristate'
tmp/.config-package.in:4580:warning: ignoring type redefinition of
'PACKAGE_luci-lib-ip' from 'boolean' to 'tristate'
tmp/.config-package.in:4618:warning: ignoring type redefinition of
'PACKAGE_luci-lib-jsonc' from 'boolean' to 'tristate'
tmp/.config-package.in:4632:warning: ignoring type redefinition of
'PACKAGE_luci-lib-nixio' from 'boolean' to 'tristate'
tmp/.config-package.in:5197:warning: ignoring type redefinition of
'PACKAGE_ip6tables' from 'boolean' to 'tristate'
tmp/.config-package.in:5245:warning: ignoring type redefinition of
'PACKAGE_iptables' from 'boolean' to 'tristate'
tmp/.config-package.in:6525:warning: ignoring type redefinition of
'PACKAGE_uhttpd' from 'boolean' to 'tristate'
tmp/.config-package.in:6561:warning: ignoring type redefinition of
'PACKAGE_uhttpd-mod-ubus' from 'boolean' to 'tristate'
tmp/.config-package.in:6760:warning: ignoring type redefinition of
'PACKAGE_hostapd-common' from 'boolean' to 'tristate'
tmp/.config-package.in:6923:warning: ignoring type redefinition of 'PACKAGE_iw'
from 'boolean' to 'tristate'
tmp/.config-package.in:7136:warning: ignoring type redefinition of
'PACKAGE_wpad-mini' from 'boolean' to 'tristate'
tmp/.config-package.in:7172:warning: ignoring type redefinition of
'PACKAGE_iwinfo' from 'boolean' to 'tristate'
tmp/.config-package.in:7185:warning: ignoring type redefinition of
'PACKAGE_jshn' from 'boolean' to 'tristate'
tmp/.config-package.in:7256:warning: ignoring type redefinition of
'PACKAGE_libjson-script' from 'boolean' to 'tristate'
Config-build.in:10099:warning: defaults for choice values not supported
Config-build.in:10103:warning: defaults for choice values not supported
Config-build.in:10107:warning: defaults for choice values not supported
Config-build.in:10111:warning: defaults for choice values not supported
Config-build.in:10115:warning: defaults for choice values not supported
Config-build.in:10119:warning: defaults for choice values not supported
Config-build.in:10135:warning: defaults for choice values not supported
I cite from Marcos:
> I was analyzing the licensing situation in the lime-packages
> repository. There is no file that indicates the global license, there
> is no CLA (Contributor License Agreements) and there are copyright
> headers set in some files inconsistently.
>> Talking with some of the developers we consider it appropriate to
> establish a license (such as GLPv3 or AGPLv3). This would affect future
> contributions, but it would be necessary for contributors to accept
> that their already written code is also licensed.
>
> To solve this situation I propose:
>
> * Set a license
> * Clarify that the contributions made in this repository respect that
> license.
> * Change existing headers and add missing ones.
> * Create a pull request with all these changes and approve the merge
> among all contributors as a form of acceptance.
The discussion started here:
https://github.com/libremesh/lime-packages/issues/213
Hi everyone,
I've following the list for quite some time and it was only in the last
month that I got myself together and installed LiMe in some Mesh Potatoes
(based on Dragino MS14) that I had with me. In Zenzeleni we've been using
MPs and VillageTelco firmware from the beginning, and although they are
"very Plug & Play" and easy to use for non-geeks, I was pretty impressed by
LiMe. What you have done making IP disappear is quite something as it is
one of the concepts people struggle with the most.
So now, we are seriously considering using LiMe at Zenzeleni. However, we
need a bit of guidance on creating a built for the MP02-AWD which is the
hardware we have in our networks. It is based on the Dragino MS14, so the
internal radio works from scratch after flashing. However, I'd like to add
the secondary radio (ralink usb) to the build, and have the wireless config
files modified accordingly, so it works directly after being flashed.
Anyone keen to guide me about how to do it?
Thanks in advance,
carlos
--
Carlos Rey-Moreno, PhD
PostDoctoral Fellow University of the Western Cape
Zenzeleni Networks: zenzeleni.nethttps://www.youtube.com/watch?v=YxTPSWMX26M
Cel: +27 (0) 76 986 3633 <+27%2076%20986%203633>
Skype: carlos.reymoreno Twitter: Creym
Hi,
Sometimes I feel shy to ask in the mailing list things that have been
answered before. Sometimes it is not easy to find those old answers.
If someone is new to the list, maybe she should first browse within the
old archives published in the web [0] so that you don't get sick of us.
I do not know an easy way to browse those old mail archives in the web.
Would you be interested in having the mailing list published as a web
forum too? That might boost the learning curve for just-arrived people.
New users would have all the answers easily accessible in a web forum.
In Trisquel the mailing list [1] and the web forum [2] -which has a very
useful 'search' box- are connected. They are the same thing, they have
the same contents, published in real time. You can use either the
mailing list or the web forum to both read and write.
I do not know if you find this interesting to have it for LibreMesh.
I do not know if this is something easy to implement. But I am sure the
animals in the Trisquel community would be happy to share with you. (Or
maybe you know better solutions)
I do not know whether old LiMe mail archives could be dumped into a web
forum so that old mail is also published there, or the forum would need
to start from scratch.
It was just a suggestion, if you do nothing it's alright, you normally
answer everything we ask.
[0] https://lists.libremesh.org/pipermail/lime-users/
[1] https://listas.trisquel.info/mailman/listinfo/
[2] https://trisquel.info/en/forum
Hello everyone,
Ilario and I finally finished to have everything configured to have
continuous integration for the lime-packages repository.
https://github.com/libremesh/lime-packages/pull/186
Continuous Integration (CI) is the practice of having tests done on
every branch that is going to become part of your master branch, in
order to fulfill a certain level of quality.
The current stake on doing CI runs a build on all the repo and verifies
that it runs successfully.
So, if you have any tests on your code (hint: nothing there for the
moment) it will be run with your build and fail if something changed
that broke the code.
Also, the CI will publish the resulting images from the build as a
comment on the Pull Request to facilitate the testing... no more need
to build locally to test the branch. Just download the image, run it on
qemu and test. That way we reduce preparation time for testing from 30+
minutes to 5 minutes or less.
if you are interested in adding tests to the code, I've written a
blogpost on freifunk blog about talking about lua and testing (one of
the languages we use on LibreMesh):
https://blog.freifunk.net/2017/06/29/tdd-unit-testing-lua-openwrtlede-c
ase/
If you want to check past previous executions, you can check them here:
https://travis-ci.org/libremesh/lime-packages
Also we have a badge that indicates the health of the branch on the
README:
https://github.com/libremesh/lime-packages/blob/develop/README.md
Hope this helps people get more involved on coding for LibreMesh!
Regards,
Hello,
deploying a weak router (like wr841) as gateway might be a bottleneck
for the network.
Would it be possible to generate simple monitoring/alerting solution for
network performance affected parameters (load?).
A possible alert could be via the routers LEDs (like blinking all at
once rapidly) or triggering a slack-like webhook[1]?
This could enable users to detect them selfs an overload and possibly
upgrade to a better hardware.
Best,
Paul
[1]: https://api.slack.com/incoming-webhooks
Hi Everyone,
We have a first trial on having Continuous Integration for LiMe:
https://github.com/libremesh/lime-packages/pull/186https://travis-ci.org/libremesh/lime-packages
It runs a build for each pull request and each commit in each pull
request and each merge. If the build fails, it fails.
If the build succeds... don't know, because now is failing :)
This builds an x86 image so you can download an test fast using qemu.
For that I need a server where to upload the image. If anyone can
provide me with that, I can add that feature later.
I think it would be great to also build ar71xx so we can test phisical
things.
Regards,
