24 Aug
2020
24 Aug
'20
12:19 p.m.
Hi,
As far as I understand the installation now should be done by following
the "Compiling LibreMesh from source code" guide at
https://libremesh.org/development.html
I think that provides firmware without a customized network profile
configuration. Chef did that, but I think there's no chef now. Is there
now any way to avoid manually configuring every router?
Thanks
24 Aug
24 Aug
1:21 p.m.
Hi!
On August 24, 2020 9:19:00 AM GMT-03:00, amuza <amuza(a)riseup.net> wrote:
Hi,
As far as I understand the installation now should be done by following
the "Compiling LibreMesh from source code" guide at
https://libremesh.org/development.html
Yes !
I think that provides firmware without a customized
network profile
configuration. Chef did that, but I think there's no chef now. Is there
now any way to avoid manually configuring every router?
Yes. The buildroot has a files directory, anything you put there will override the default
files. So you should place the "network-profile" files there.
I am working to update the configuration documentation as there was a lot of improvement
in that area in the last year (specifically the lime-node/lime-community/lime-defaults
hierarchy and the generic configs and lime-assets that was merged last week). I have an
early work in progress document half English half Spanish that may help you
https://hackmd.io/CWm5MbwrToevK1-mLh4Y-Q?view
Everyone can edit so if you can improve it please do it :)
Best!
SAn
2:06 p.m.
I think that provides firmware without a
customized network profile
configuration. Chef did that, but I think there's no chef now. Is there
now any way to avoid manually configuring every router?
Yes. The buildroot has a files directory, anything you put there will override the
default files. So you should place the "network-profile" files there. 
2:06 p.m.
On 8/24/20 2:19 PM, amuza wrote:
Hi,
Hi Amuza!!
As far as I understand the installation now should be
done by following
the "Compiling LibreMesh from source code" guide at
https://libremesh.org/development.html
Yep, that's correct :)
Those are the official instructions, on top of that modifications can be
done, at your own risk... For example compiling on top of OpenWrt 19.07
is not officially suggested but should work already.
I think that provides firmware without a customized
network profile
configuration.
Yep, you're right.
The awesome Aparcar is working on that as you can see here:
https://github.com/libremesh/network-profiles/blob/master/.github/workflows…
but currently the upload to Aparcar server is failing due to some
missing settings.
Is there any LibreMesh organization server that can be used for this?
Hopefully this will be available at some point...
If you really really really want to use the network-profiles now and
using the
https://github.com/libremesh/network-profiles
repository, the process can be done locally and manually (it's complex,
I don't suggest this) generating a source repository using
https://github.com/libremesh/network-profiles-builder
and including the resulting directory as a local feed in feeds.conf file
of the buildroot. This way you can either include the files in the
compiled images or produce a package that can be installed using OPKG.
The solution proposed by SAn (to put the wanted files in the files/
directory in the main build directory) is much more convenient:
https://openwrt.org/docs/guide-developer/build-system/use-buildsystem#custo…
Chef did that, but I think there's no chef now.
Also this is right.
Aparcar did a lot of improvements on Chef (so many that I'm not even
sure it's still called Chef...) and I suspect that it's not trivial to
have LibreMesh in there? I actually don't know.
Anyway until when there's no actual release, I think that people should
use the old fashioned method (compiling everything).
Is there
now any way to avoid manually configuring every router?
Yes, the solution proposed by SAn is the most convenient but various
alternatives are available :)
Thanks
Ciao!!
Ilario
3:01 p.m.
Thank you Ilario and SAn!
The solution proposed by SAn (to put the wanted files
in the files/
directory in the main build directory) is much more convenient:
https://openwrt.org/docs/guide-developer/build-system/use-buildsystem#custo…
Why can't I find that "files" directory. Shouldn't it be into the
openwrt directory?
I have already compiled the generic firmware, I don't know if that makes
any difference...
3:07 p.m.
On 8/24/20 12:01 PM, amuza wrote:
Thank you Ilario and SAn!
You have to create the directory in the base directory of the repository.
See here https://gitlab.com/librerouter/librerouteros/-/tree/librerouter-1.3 for an
example.
The solution proposed by SAn (to put the wanted
files in the files/
directory in the main build directory) is much more convenient:
https://openwrt.org/docs/guide-developer/build-system/use-buildsystem#custo…
Why can't I find that "files" directory. Shouldn't it be into the
openwrt directory?
I have already compiled the generic firmware, I don't know if that makes
any difference...
3:18 p.m.
Why can't
I find that "files" directory. Shouldn't it be into the
openwrt directory?
You have to create the directory in the base directory of the repository.
See here https://gitlab.com/librerouter/librerouteros/-/tree/librerouter-1.3 for an
example.
>
3:22 p.m.
On 8/24/20 12:18 PM, amuza wrote:
What is "the base directory of the repository"?
I guess in my case it is ~/git/openwrt, is that correct?
Is that the same thing as "buildroot"?
Ok, so this "files" directory is something that must be manually
created, right?
Yes to all the questions!
Why can't I find that "files"
directory. Shouldn't it be into the
openwrt directory?
You have to create the directory in the base directory of the repository.
See here https://gitlab.com/librerouter/librerouteros/-/tree/librerouter-1.3 for an
example.
>
3:37 p.m.
On 8/24/20 5:18 PM, amuza wrote:
What is "the base directory of the repository"?
I guess in my case it is ~/git/openwrt, is that correct?
Is that the same thing as "buildroot"?
Ok, so this "files" directory is something that must be manually
created, right?
I think that this is quite a common confusion source, so I specified it
in the compilation guide as a note. Check it out here:
https://libremesh.org/development.html#compiling_libremesh_from_source_code
Ciao,
Ilario
PS please remember that modifications on the website are more than
welcome! Try the "Edit this page" button on the top right of each page!
--
Ilario
iochesonome(a)gmail.com
ilario(a)sindominio.net
Why can't I find that "files"
directory. Shouldn't it be into the
openwrt directory?
You have to create the directory in the base directory of the repository.
See here https://gitlab.com/librerouter/librerouteros/-/tree/librerouter-1.3 for an
example.
>
10:08 p.m.
Ilario Gelmetti:
On 8/24/20 5:18 PM, amuza wrote:
What is "the base directory of the repository"?
I guess in my case it is ~/git/openwrt, is that correct?
Is that the same thing as "buildroot"?
Ok, so this "files" directory is something that must be manually
created, right?
I think that this is quite a common confusion source, so I specified it
in the compilation guide as a note. Check it out here:
https://libremesh.org/development.html#compiling_libremesh_from_source_code
Ciao,
Ilario
PS please remember that modifications on the website are more than
welcome! Try the "Edit this page" button on the top right of each page!
Thank you again Ilario and SAn!
Why can't I find that "files"
directory. Shouldn't it be into the
openwrt directory?
You have to create the directory in the base directory of the repository.
See here https://gitlab.com/librerouter/librerouteros/-/tree/librerouter-1.3 for an
example.
>
2001
days inactive
2001
days old
lime-users@lists.libremesh.org
9 comments
3 participants
participants (3)
-
amuza -
Ilario Gelmetti -
SAn