lime-dev

lime-dev@lists.libremesh.org

338 discussions

by Paul Spooren

I pushed a new branch to libremesh/lime-packages called master. We should from now on use this one instead of develop. I'd the scripts of lime-sdk to use this branch in develop mode. To clean up the outdated branches and repositories of /libremesh please grant me the required GitHub permissions. Best

6 years, 6 months

New location for snapshots.libremesh.org

by Paul Spooren

Hi, we got a new snapshots server which can host (and build) CI stuff. I created a travis CI script so on each push it's building all LiMe packages and uploads them to the server. The LibreRouter specific stuff is also mirrored there. Whoever needs access to update these files please ping me. Who is in charge of the libremesh.org domain? Please forward snapshots.libremesh.org to: IPv4: 141.54.160.32 IPv6: 2001:470:6c:1f4::2 Thanks, Paul

6 years, 6 months

Add PKGARCH:=all to all possible packages

by Paul Spooren

Hi, dealing lately a bit with CI and build packages for all popular targets I found that most LiMe packages only use scripts like Lua and Bash and therefore don't really need to be compiled target specific. Idea is to add the PKGARCH:=all parameter which allows to install resulting packages on all targets without opkg protesting. I created an Pull request for that[1], please try! You can simply add `.diff` to the url and receive a diff which is usable with `git apply 370.diff`. Eventually we could offer generic feeds in the `/etc/opkg/limefeeds.conf` file and save a lot of build time. A few packages actually require compiling and are thereby not arch independent, namely: * dhcpdiscover * reghack * lime-webui Are the first two packages actively used? I've never stumbled across them. Best, Paul [1]: https://github.com/libremesh/lime-packages/pull/370

6 years, 6 months

Re: [lime-dev] Simplify the lime-packages branches

by Nicolas Pace

Agree! On May 29, 2018 2:17:13 AM CDT, Paul Spooren <p(a)aparcar.org> wrote: >Hi all, > >The lime-packages repository has currently a huge amount of branches >making it rather hard to spot active ones. I'd propose to use the >following structure (stolen from OpenWrt): > >* Use one branch for developing (currently called "development", may >better be unified to " master"). >* One brach per release > > >This is great because new people don't start developing on master and >eventually find out its "outdated". The structure is used on literally >every other GH project I'm working on, even on other LibreMesh repos. > >All pull requests should come from forked repos. > >Additionally, the dev branch is currently (partly) protected so that >most devs can't directly push there but need an approved PR, which is >good. However, the master branch aka current stable release lacks this >security measurement. > >Best, >Paul >_______________________________________________ >lime-dev mailing list >lime-dev(a)lists.libremesh.org >https://lists.libremesh.org/mailman/listinfo/lime-dev -- Enviado desde mi dispositivo Android con K-9 Mail. Por favor, disculpa mi brevedad.

6 years, 6 months

Snapshot builds

by Paul Spooren

Hello again, I think for development it would be nice to automatically compile all packages on the dev branch on every push. Offering them on a server making it easy to use in dev machines. As this introduces plenty of compiling of suggest to use cheap cloud service instead of burning our own (community) hardware. Scaleway offers 4 cores and 25GB SSD for 3€ a month, which should be just enough. Any reasons against pointing snapshots.libremesh.org to such a VM? I'd be happy to set it up and can also pay for now. Best, Paul

6 years, 6 months

Simplify the lime-packages branches

by Paul Spooren

Hi all, The lime-packages repository has currently a huge amount of branches making it rather hard to spot active ones. I'd propose to use the following structure (stolen from OpenWrt): * Use one branch for developing (currently called "development", may better be unified to " master"). * One brach per release This is great because new people don't start developing on master and eventually find out its "outdated". The structure is used on literally every other GH project I'm working on, even on other LibreMesh repos. All pull requests should come from forked repos. Additionally, the dev branch is currently (partly) protected so that most devs can't directly push there but need an approved PR, which is good. However, the master branch aka current stable release lacks this security measurement. Best, Paul

6 years, 6 months

Does the Version of the WDR3600 / WDR3500 Matter? Also, is the only difference between the 3500 and the 3600 gigabit ethernet ports?

by John W

I found a used WDR3600 version 1.1 and wanted to know if there is any advantage to any particular hardware version for libremesh? Am I correct in saying that the only difference between the WDR3500 and the WDR3600 is that the WDR3600 has gigabit ethernet ports?

6 years, 8 months

What LibreMesh Router Models receive the most development effort, the most timely security updates, are most stable / secure with the most developed features, etc?

by John W

What LibreMesh Router Models receive the most development effort, the most timely security updates, are most stable / secure with the most developed features, etc? Thanks! -John

6 years, 8 months

Request to support in compiling Libremesh for GL-INET AR750 router.

by senthil kumar

Hi Libremesh Dev Team, I am very actively using Libremesh to set up the community network in India. I have used GL-INet AR150 single band router. Now I would like to build libremesh firmware for AR750 router. More Details about the router https://openwrt.org/toh/hwdata/gl.inet/gl.inet_gl-ar750 This is officially supported in openwrt/LEDE https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=2e5252d346e2ec832… Can someone help me in compiling this? I am facing error while compiling. How to add the profile for gl-ar750 in libremesh? Looking forward to the reply. *senthilm@sencloud*:*~/lime-sdk*$ ./cooker -c ar71xx/generic --profile=gl-ar750 --flavor=lime_default --remote -> Using remote repository for ImageBuilder, architecture: mips_24kc -> Cooking ar71xx/generic/gl-ar750 -> Cooking firmware image --> Selected extra packages: lime-full lime-app -dnsmasq make: Entering directory '/home/senthilm/lime-sdk/17.01.4/ar71xx/generic/ib' *Profile "gl-ar750" does not exist!* PS gl-ar150 is compiling without error. -- Thanks and Regards, * • **Senthilkumar M* * • **Community Manager,* * • **Google Developer Group Madurai**,* *• **Mentor, Metoomentor.org* * • **Senior Research Engineer, Qualcomm. * * • allaboutsenthil.in <http://allaboutsenthil.in>* • +91 8095207092

6 years, 8 months

GSoC project

by Paul Spooren

Dear all, as some may know I've been working last year [1] in GSoC and like to repeat that. I checked the Freifunk project page [2] and found the following project of LibreMesh I liked most: LibreNet6 integration [3]. As discussed on GitHub [4] wireguard [5] could be a slim & fast replacement for Tinc. Problem is the missing auto provisioning of the clients, as stated on the official website as well [6]. I came up with a small PoC [7] as a centralized solution for the following tasks: * Granting administrators/supporters device access to help with network issues * Secure connection over an unencrypted mesh network * Offer public IPv4/6 to routers A second approach could be to use bmx7-sms plugin to distribute public keys within the mesh and enable not only the three points above but also secure connections between all nodes. The second approach may become obsolete as bmx7 might use `ip xfrm` [8] to encrypt tunnels directly. I'm aware that focus shouldn't be the coolest project but the one most usable for the (Libre)Mesh community. So please share you thoughts if you find other (not listed) project ideas I could work on. Please keep in mind the deadline to apply is within the next weeks. Best, Paul [1] https://github.com/aparcar/attendedsysupgrade-server [2] https://projects.freifunk.net/#/projects [3] https://projects.freifunk.net/#/projects?project=libremesh_librenet6_integr… [4] https://github.com/libremesh/lime-packages/issues/99 [5] http://wireguard.com/ [6] https://www.wireguard.com/todo/#dynamic-web-app-for-provisioning [7] https://github.com/aparcar/wireguard-provisioning [8] http://man7.org/linux/man-pages/man8/ip-xfrm.8.html#DESCRIPTION

6 years, 9 months

← Newer
1
2
3
4
5
6
7
...
34
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

lime-dev