Hello! Working with Librenet6 configuration I found a scenario where the
documentation go to an error that at the beginning is hard to understand
why.
In Unix systems "hostname" could be an alphanumeric and accept the
hyphen ('-')[1], but Tinc "Name" accept alphanumeric and the underscore
('_')[2], not the hyphen. So, there is a scenario not much uncommon
where we could have a hostname with hyphens like "virtual-server-1" or
"LiMe-0C9B".
So, those parts in documentation could became in a bug:
In Debian based:
Name = host_$(hostname)
In OpenWrt based:
HOSTNAME=$(uci get system.(a)system[0].hostname)
[0]
I have permissions for change the documentation and fix that issue, but
I want to talk with you about it because my fix proposal change the way
of naming hosts (beginning with an "host_" or "topo_") and it could
affect some of others of your scripts:
As is written in Tinc manual I think that they have knowledge about this
possible collision between to ways of naming hosts. So the manual says:
"If Name starts with a $, then the contents of the environment variable
that follows will be used. In that case, invalid characters will be
converted to underscores. If Name is $HOST, but no such environment
variable exist, the hostname will be read using the gethostname() system
call."[2]
About tinc environment variables[3].
So my proposal is changing from
Name = host_$(hostname) # bash variable
or
Name = topo_$HOSTNAME # bash variable
to
Name = $HOST # tinc environment variable
(And in the file names)
result:
"host_myniceserver" to "myniceserver".
"host_virtual-server-1" (that will fail) to "virtual_server_1"
"topo_LiMe-0C9B" (that will fail) to "LiMe_0C9B"
But in this case we lost info about if the host came from Debian/Ubuntu
manual (host_) or came from OpenWrt manual (topo_).
What do you think?
Also we made an script for my machines that we can share, off course is
in case of an script that this standardization process has sense.
Regards.
[0] http://docs.altermundi.net/LibreNet6/Setup
[1] As wrote in RFC 952 and RFC 1123
[2]
http://www.tinc-vpn.org/documentation-1.1/Main-configuration-variables.html
Name = <name> [required]
This is a symbolic name for this connection. The name must consist
only of alfanumeric and underscore characters (a-z, A-Z, 0-9 and _), and
is case sensitive.
[3]
http://www.tinc-vpn.org/documentation/Scripts.html#index-environment-variab…
($HOST environment variable (and maybe others) are not documented)
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
