Hi,
some time ago I created chef.libremesh.org as a "demo" for the used
backend [0]. It's kinda hacked as I learned JavaScript while
implementing it. I'm quite unsatisfied by the JS code quality so I
wanted to ask if somebody would help me to rewrite it in a better way,
using some minimal framework?
Best,
Paul
[0]: https://github.com/aparcar/attendedsysupgrade-server
as in subject you can reproduce it by creating an image for the canmasdeu/
bridge profile with plain lede flavour
I suspect it is because the profile get opkgized and it may be installed before
lime-system and then the file get overwritten
haven't tested if with last cooker it happens or not to confirm my theory
Cheers
Check the .travis.yml files, feel free to add stuff to a readmeOn Jun 24, 2018 3:45 AM, guifipedro <guifipedro(a)gmail.com> wrote:
>
> I'm very happy you did that.
>
> Can you add the details to do the openwrt base image? [1]
>
> Thanks
>
> [1] https://github.com/aparcar/openwrt-docker
>
> On Sat, Jun 23, 2018 at 7:00 PM, Paul Spooren <mail(a)aparcar.org> wrote:
> > Hi all,
> >
> > to simplify image testing for users which are not familiar with qemu I
> > created a docker image containing LibreMesh.
> >
> > If you like check it out at aparcar/libremesh with the tags "latest" or
> > "stable"
> >
> > All further information for usage are described in the README [0], feel
> > free to extend it.
> >
> > In case the docker thing turns out to be of any use, I'd swap it to the
> > official libremesh account.
> >
> > Sunshine,
> > Paul
> >
> > [0]: https://github.com/aparcar/libremesh-docker/blob/master/README.md
> >
> > _______________________________________________
> > lime-dev mailing list
> > lime-dev(a)lists.libremesh.org
> > https://lists.libremesh.org/mailman/listinfo/lime-dev
> _______________________________________________
> lime-dev mailing list
> lime-dev(a)lists.libremesh.org
> https://lists.libremesh.org/mailman/listinfo/lime-dev
Hi all,
to simplify image testing for users which are not familiar with qemu I
created a docker image containing LibreMesh.
If you like check it out at aparcar/libremesh with the tags "latest" or
"stable"
All further information for usage are described in the README [0], feel
free to extend it.
In case the docker thing turns out to be of any use, I'd swap it to the
official libremesh account.
Sunshine,
Paul
[0]: https://github.com/aparcar/libremesh-docker/blob/master/README.md
Hi all,
OpenWrt 18.06 is just around the corner with fun new stuff, like options
to encrypted 11s mesh & support for tons of new devices!
To create a LibreMesh release that satisfies all tastes, we should think
a bit of new flavors, meaning the combination of preinstalled packages.
Some points to consider:
* There is a new lime-proto-babeld plugin allowing babeld routing
* The lime-proto-bmx7 plugin and BMX7 itself became way more stable and
has various advances over BMX6
* Using encrypted mesh requires wpand-mesh-{openssl, wolfssl} installed,
aka big crypto libs
* The lime-app shows some basic infos which could satisfy basic user
requirements.
I'm happy to merge flavor PRs and build them on our new snapshot server
for all common targets.
Sunshine,
Paul
Hi all,
does anyone has a TL-WR941ND laying around? If so, please send me the
content of /etc/board.json, that would greatly help me to improve LibreMesh.
Best
Hi,
for my bachelor thesis I created some tools which hopefully simplify
monitoring & managing of mesh networks. The scope wasn't exactly
community networks (sorry, not my choice) but we can may bend the stuff
to make it work for LibreMesh real purpose as well!
All source is found here https://github.com/aparcar/meshrc
To simplify my own tests with it, I'd like to setup a package feed. If
nobody minds I'd create an additional feed at snapshots.libremesh.org
called meshrc.
Best,
Paul
Hi, I found some old GitHub repo forks which rather confuse users then
do any good, if everyone is okay with that I'd remove them:
* openwrt
* openwrt-packages
* openwrt-oldpackages
* demeshtify
What happens at lime-ui-ng? Isn't that covered in lime-packages-ui which
uses lime-app?
Best
Hi,
in various parts of lime-packages I found the following code snipped:
define Build/Compile
@rm -rf ./build || true
@cp -r ./src ./build
@sed -i '/^--!.*/d' build/*.lua
endef
It removes all comments from the source code before applying it to the
devices.
Is the size impact worth the fact that
a) people locally developing may accidentally change files in ./build
rather then ./src and by running make overwriting all their changes
b) Make on device developing harder due to missing comments?
I'm guessing there are other parts of LibreMesh bloated which could
improve storage footprint more than this little hack, what do you think?
Best,
Paul
