3 Mar
2020
3 Mar
'20
11:25 a.m.
Hello!
I have been out for a long while, and now I would like to resume my
libremeshing. I don't remember many things, and I see the website did
not change much.
Is 17.06 still the recommended version?
I remember when you wanted to precook binaries for your own network
there was this chef thing you could use. Is that thing still available?
I don't remember where it was.
I'd be happy if you could give me some updates on versions,
methodologies and URLs.
Thank you!
23 Mar
23 Mar
3:50 p.m.
On 3/3/20 12:25 PM, amuza wrote:
I have been out for a long while, and now I would like
to resume my
libremeshing. I don't remember many things, and I see the website did
not change much.
Is 17.06 still the recommended version?
I remember when you wanted to precook binaries for your own network
there was this chef thing you could use. Is that thing still available?
I don't remember where it was.
I'd be happy if you could give me some updates on versions,
methodologies and URLs.
Hi!
As there was no answer on this topic in 20 days, I'll copy and paste
here spiccinini's answer that was posted on the Riot/Matrix chat [1] and
I'll add some more observations:
spiccinini wrote:
some of us are mainly working in master, trying to
maintain it as stable as possible. Many communities in south america have been using this
"rolling un-release" libremesh firmwares.
In my opinion we should performa a release based on 18.06 with what we have now, stating
the current issues. But I know that not everyone has the same opinion (at least ilario and
daniel).
We currently don't have a way to colectively take decisions (for example to release
or not, etc) other than the github pull requests. I would be very happy (and I beleave it
will impact positively in the project) if we find a way to build a decision mechanism.
In my opinion it would be better to have an OpenWrt19.07-based release
but to have a OpenWrt18.06-based release is much much better than no
release at all (which is the current situation: LibreMesh17.06 is 3
years old now).
Chef backend and frontend is currently being rewritten by aparcar and
coworkers in a completely different shape [2,3] and anyway does not make
sense to have a Chef for something that is not a release.
So, currently the suggested compilation method is the one described on
the website on "Compiling LibreMesh from source code" [4].
The pending issues for making a release based on OpenWrt18.06 or on
OpenWrt19.07 does not differ much [5] but there is at least a
significant one regarding Batman-adv configuration.
I started selecting some high-priority issues which in my opinion would
be good to fix/implement before releasing [6]. Any contribution and
comment is welcome!
Hugs,
Ilario
[1] https://libremesh.org/communication.html
[2] https://github.com/aparcar/asu/issues/211
[3] https://github.com/aparcar/asu
[4] https://libremesh.org/development.html
[5] https://github.com/libremesh/lime-packages/labels/OpenWrt%2019.07
[6] https://github.com/orgs/libremesh/projects/2
--
Ilario
iochesonome(a)gmail.com
ilario(a)sindominio.net
3:53 p.m.
New subject: [lime-users] Unsubscribe
________________________________
From: lime-users <lime-users-bounces(a)lists.libremesh.org> on behalf of Ilario
Gelmetti <iochesonome(a)gmail.com>
Sent: 23 March 2020 15:50
To: lime-users(a)lists.libremesh.org <lime-users(a)lists.libremesh.org>
Subject: [EXT] Re: [lime-users] Catching up
[RECEIVED FROM EXTERNAL SENDER]
On 3/3/20 12:25 PM, amuza wrote:
I have been out for a long while, and now I would like
to resume my
libremeshing. I don't remember many things, and I see the website did
not change much.
Is 17.06 still the recommended version?
I remember when you wanted to precook binaries for your own network
there was this chef thing you could use. Is that thing still available?
I don't remember where it was.
I'd be happy if you could give me some updates on versions,
methodologies and URLs.
Hi!
As there was no answer on this topic in 20 days, I'll copy and paste
here spiccinini's answer that was posted on the Riot/Matrix chat [1] and
I'll add some more observations:
spiccinini wrote:
some of us are mainly working in master, trying to
maintain it as stable as possible. Many communities in south america have been using this
"rolling un-release" libremesh firmwares.
In my opinion we should performa a release based on 18.06 with what we have now, stating
the current issues. But I know that not everyone has the same opinion (at least ilario and
daniel).
We currently don't have a way to colectively take decisions (for example to release
or not, etc) other than the github pull requests. I would be very happy (and I beleave it
will impact positively in the project) if we find a way to build a decision mechanism.
In my opinion it would be better to have an OpenWrt19.07-based release
but to have a OpenWrt18.06-based release is much much better than no
release at all (which is the current situation: LibreMesh17.06 is 3
years old now).
Chef backend and frontend is currently being rewritten by aparcar and
coworkers in a completely different shape [2,3] and anyway does not make
sense to have a Chef for something that is not a release.
So, currently the suggested compilation method is the one described on
the website on "Compiling LibreMesh from source code" [4].
The pending issues for making a release based on OpenWrt18.06 or on
OpenWrt19.07 does not differ much [5] but there is at least a
significant one regarding Batman-adv configuration.
I started selecting some high-priority issues which in my opinion would
be good to fix/implement before releasing [6]. Any contribution and
comment is welcome!
Hugs,
Ilario
[1]
https://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flibremesh…
[2]
https://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…
[3]
https://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…
[4]
https://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flibremesh…
[5]
https://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…
[6]
https://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…
--
Ilario
iochesonome(a)gmail.com
ilario(a)sindominio.net
25 Mar
25 Mar
6:10 p.m.
Thank you very much Ilario!
Hugs!
Ilario Gelmetti:
On 3/3/20 12:25 PM, amuza wrote:
I have been out for a long while, and now I would
like to resume my
libremeshing. I don't remember many things, and I see the website did
not change much.
Is 17.06 still the recommended version?
I remember when you wanted to precook binaries for your own network
there was this chef thing you could use. Is that thing still available?
I don't remember where it was.
I'd be happy if you could give me some updates on versions,
methodologies and URLs.
Hi!
As there was no answer on this topic in 20 days, I'll copy and paste
here spiccinini's answer that was posted on the Riot/Matrix chat [1] and
I'll add some more observations:
spiccinini wrote:
some of us are mainly working in master, trying
to maintain it as stable as possible. Many communities in south america have been using
this "rolling un-release" libremesh firmwares.
In my opinion we should performa a release based on 18.06 with what we have now, stating
the current issues. But I know that not everyone has the same opinion (at least ilario and
daniel).
We currently don't have a way to colectively take decisions (for example to release
or not, etc) other than the github pull requests. I would be very happy (and I beleave it
will impact positively in the project) if we find a way to build a decision mechanism.
In my opinion it would be better to have an OpenWrt19.07-based release
but to have a OpenWrt18.06-based release is much much better than no
release at all (which is the current situation: LibreMesh17.06 is 3
years old now).
Chef backend and frontend is currently being rewritten by aparcar and
coworkers in a completely different shape [2,3] and anyway does not make
sense to have a Chef for something that is not a release.
So, currently the suggested compilation method is the one described on
the website on "Compiling LibreMesh from source code" [4].
The pending issues for making a release based on OpenWrt18.06 or on
OpenWrt19.07 does not differ much [5] but there is at least a
significant one regarding Batman-adv configuration.
I started selecting some high-priority issues which in my opinion would
be good to fix/implement before releasing [6]. Any contribution and
comment is welcome!
Hugs,
Ilario
[1] https://libremesh.org/communication.html
[2] https://github.com/aparcar/asu/issues/211
[3] https://github.com/aparcar/asu
[4] https://libremesh.org/development.html
[5] https://github.com/libremesh/lime-packages/labels/OpenWrt%2019.07
[6] https://github.com/orgs/libremesh/projects/2
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
23 Aug
23 Aug
5:05 p.m.
Ilario Gelmetti:
On 3/3/20 12:25 PM, amuza wrote:
According to the website, this method ("Compiling LibreMesh from source
code") uses OpenWRT 18.04, is it ok to use 19.07 instead?
If that's not problematic, is there anything else I should do or know
besides changing the version in the git clone command?
I have been out for a long while, and now I would
like to resume my
libremeshing. I don't remember many things, and I see the website did
not change much.
Is 17.06 still the recommended version?
I remember when you wanted to precook binaries for your own network
there was this chef thing you could use. Is that thing still available?
I don't remember where it was.
I'd be happy if you could give me some updates on versions,
methodologies and URLs.
Hi!
As there was no answer on this topic in 20 days, I'll copy and paste
here spiccinini's answer that was posted on the Riot/Matrix chat [1] and
I'll add some more observations:
spiccinini wrote:
some of us are mainly working in master, trying
to maintain it as stable as possible. Many communities in south america have been using
this "rolling un-release" libremesh firmwares.
In my opinion we should performa a release based on 18.06 with what we have now, stating
the current issues. But I know that not everyone has the same opinion (at least ilario and
daniel).
We currently don't have a way to colectively take decisions (for example to release
or not, etc) other than the github pull requests. I would be very happy (and I beleave it
will impact positively in the project) if we find a way to build a decision mechanism.
In my opinion it would be better to have an OpenWrt19.07-based release
but to have a OpenWrt18.06-based release is much much better than no
release at all (which is the current situation: LibreMesh17.06 is 3
years old now).
Chef backend and frontend is currently being rewritten by aparcar and
coworkers in a completely different shape [2,3] and anyway does not make
sense to have a Chef for something that is not a release.
So, currently the suggested compilation method is the one described on
the website on "Compiling LibreMesh from source code" [4].
The pending issues for making a release based on
OpenWrt18.06 or on
OpenWrt19.07 does not differ much [5] but there is at least a
significant one regarding Batman-adv configuration.
I started selecting some high-priority issues which in my opinion would
be good to fix/implement before releasing [6]. Any contribution and
comment is welcome!
Hugs,
Ilario
[1] https://libremesh.org/communication.html
[2] https://github.com/aparcar/asu/issues/211
[3] https://github.com/aparcar/asu
[4] https://libremesh.org/development.html
[5] https://github.com/libremesh/lime-packages/labels/OpenWrt%2019.07
[6] https://github.com/orgs/libremesh/projects/2
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
6:36 p.m.
Hi!
On August 23, 2020 2:05:00 PM GMT-03:00, amuza <amuza(a)riseup.net> wrote:
Ilario Gelmetti:
and
Yes, at least it has been reported to work fine with 19.07.
On 3/3/20 12:25 PM, amuza wrote:
> I have been out for a long while, and now I would like to resume my
> libremeshing. I don't remember many things, and I see the website
did
> not change much.
>
> Is 17.06 still the recommended version?
>
> I remember when you wanted to precook binaries for your own network
> there was this chef thing you could use. Is that thing still
available?
I
don't remember where it was.
I'd be happy if you could give me some updates on versions,
methodologies and URLs.
Hi!
As there was no answer on this topic in 20 days, I'll copy and paste
here spiccinini's answer that was posted on the Riot/Matrix chat [1] I'll add some more observations:
spiccinini wrote:
> some of us are mainly working in master, trying to maintain it as
stable as
possible. Many communities in south america have been using
this "rolling un-release" libremesh firmwares.
>
> In my opinion we should performa a release based on 18.06 with what
we have
now, stating the current issues. But I know that not everyone
has the same opinion (at least ilario and daniel).
>
> We currently don't have a way to colectively take decisions (for
example
to release or not, etc) other than the github pull requests. I
would be very happy (and I beleave it will impact positively in the
project) if we find a way to build a decision mechanism.
In my opinion it would be better to have an OpenWrt19.07-based
release
but to have a OpenWrt18.06-based release is much
much better than no
release at all (which is the current situation: LibreMesh17.06 is 3
years old now).
Chef backend and frontend is currently being rewritten by aparcar and
coworkers in a completely different shape [2,3] and anyway does not
make
sense to have a Chef for something that is not a
release.
So, currently the suggested compilation method is the one described
on
the website on "Compiling LibreMesh from
source code" [4].
According to the website, this method ("Compiling LibreMesh from source
code") uses OpenWRT 18.04, is it ok to use 19.07 instead?
If that's not problematic, is there anything else I should do or know
besides changing the version in the git clone command?
We have this issues labeled 19.07:
https://github.com/libremesh/lime-packages/issues?q=is%3Aopen+is%3Aissue+la…
Please if you find some problem report it ;)
Best!
SAn
The pending issues for making a release based on
OpenWrt18.06 or on
OpenWrt19.07 does not differ much [5] but there is at least a
significant one regarding Batman-adv configuration.
I started selecting some high-priority issues which in my opinion
would
> be good to fix/implement before releasing [6]. Any contribution and
> comment is welcome!
>
> Hugs,
> Ilario
>
> [1] https://libremesh.org/communication.html
> [2] https://github.com/aparcar/asu/issues/211
> [3] https://github.com/aparcar/asu
> [4] https://libremesh.org/development.html
> [5] https://github.com/libremesh/lime-packages/labels/OpenWrt%2019.07
> [6] https://github.com/orgs/libremesh/projects/2
>
>
>
> _______________________________________________
> lime-users mailing list
> lime-users(a)lists.libremesh.org
> https://lists.libremesh.org/mailman/listinfo/lime-users
>
7:34 p.m.
According to the website, this method ("Compiling LibreMesh from source
code") uses OpenWRT 18.04, is it ok to use 19.07 instead?
Yes, at least it has been reported to work fine with 19.07.
If that's not problematic, is there anything else I should do or know
besides changing the version in the git clone command?
We have this issues labeled 19.07:
https://github.com/libremesh/lime-packages/issues?q=is%3Aopen+is%3Aissue+la…
Please if you find some problem report it ;)
Best!
SAn
27 Aug
27 Aug
7:56 a.m.
amuza:
Thank you SAn!
I think I will try with 18.04, I'm not an expert and I don't understand
some of those 19.07 issues, so I guess things will be easier for me if I
try with 18.04.
Cheers
What are the effects of those open issues in 19.07?
As I don't understand them, I don't know if they would affect me.
Thanks!
According to the website, this method ("Compiling LibreMesh from source
code") uses OpenWRT 18.04, is it ok to use 19.07 instead?
Yes, at least it has been reported to work fine with 19.07.
If that's not problematic, is there anything else I should do or know
besides changing the version in the git clone command?
We have this issues labeled 19.07:
https://github.com/libremesh/lime-packages/issues?q=is%3Aopen+is%3Aissue+la…
Please if you find some problem report it ;)
Best!
SAn
1335
days inactive
1512
days old
lime-users@lists.libremesh.org
7 comments
4 participants
participants (4)
-
amuza -
Ilario Gelmetti -
Nick Dark -
SAn