Hi devs!
Some times ago I reported an issue on Github asking to "Separate
settings for netmask and IP range auto assignment" [#18].
Then I implemented a simple solution [#22] adding an _optional_ field to
the main_ipv4_address option.
G10 suggests to slightly modify my implementation, no problem.
But could we discuss if there's a better solution or if mine is ok?
Thanks,
Ilario
[#18]: https://github.com/libre-mesh/lime-packages/issues/18
[#22]: https://github.com/libre-mesh/lime-packages/pull/22
--
Ilario Gelmetti
iochesonome(a)gmail.com
igelmetti(a)iciq.es
ilario.gelmetti(a)estudiants.urv.cat
This service is critical enough for enough community networks to start
thinking deeply on strategies on how to improve it's uptime in an even more
decentralized manner.
Cheers!
hey geniuses!
i've been fixing a few loose ends that were left from the 15.04 release:
* luci-app-lime-location was not included (we consider it a serious
regression versus the AlterMesh we have been using until now)
including it was really simple; at some point it would probably be nice
to integrate it better (make it understand lime-defaults, etc)
* luci-lib-librmap-bmx6 plugin was made by nico the other night, which
greatly enhances the libremap experience by reporting bmx6 links :D.
include that as well.
https://github.com/libre-mesh/lime-packages/commit/1bba47922611722f265a5dff…
########
* lime-webui was mostly left half-baked, so i gave it a bit of love and
fixes. Now it also blends better with the recently introduced
luci-app-lime-location.
https://github.com/libre-mesh/lime-packages/commit/6f26719a4bf47897ca7a8b62…
########
* most importantly, i gave one more round of love to the
dnsmasq-lease-share stuff; now it works in all scenarios AFAICT,
correctly resolving dhcp leases and also reserving leases gave by other
nodes
* while doing that, i also implemented a new package:
dnsmasq-distributed-hosts , which shares the data found in /etc/hosts of
each node. So now there's a trivial way to distribute static addresses
through the whole cloud :)
https://github.com/libre-mesh/lime-packages/commit/f4e2eb07d4c83571fecc3814…
########
in summary:
https://github.com/libre-mesh/lime-packages/compare/15.04...sandbox/release…
########
last but not least, some tweaks to libremap-agent, which are already
prepared as a pull request for andre
https://github.com/libremap/libremap-agent-openwrt/pull/17https://github.com/libre-mesh/libremap-agent/compare/15.04...libre-mesh:san…
########
i know this is diverging more and more from develop, really sorry for
that :$ i promise to merge all this properly as soon as we finish
deploying the stable release in our networks :D
quintanalibre is already halfway through
and boqueronlibre (a recently born network) has all its 10 routers with
15.04 running fine :)
cheers!
---------- Forwarded Message ----------
Subject: [GSoC Mentors Announce] Google Summer of Code 2016
Date: Tuesday, October 13, 2015, 04:52:29 PM
From: 'Carol Smith' via Google Summer of Code Mentors Announce List <gsoc-
mentors-announce(a)googlegroups.com>
To: GSoC Mentors Announce <gsoc-mentors-announce(a)googlegroups.com>
Hi GSoC mentors and org admins,
We've announced
<http://google-opensource.blogspot.com/2015/10/dozen-of-one-half-dozen-of-ot…>
that we're holding Google Summer of Code 2016 <http://g.co/gsoc>.
The GSoC calendar
<https://www.google.com/calendar/embed?src=gsummerofcode@gmail.com&ctz=Ameri…>,
FAQ <https://developers.google.com/open-source/gsoc/faq>, and events
timeline <https://developers.google.com/open-source/gsoc/timeline> have all
been updated with next year's important dates, so please refer to those for
the milestones for the program.
Please consider applying to participate as an organization again next year
or maybe joining as a mentor for your favorite organization if they are
selected to participate.
We rely on you for your help for the success of this program, so thank you
in advance for all the work you do!
Cheers,
Carol
--
You received this message because you are subscribed to the Google Groups
"Google Summer of Code Mentors Announce List" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to gsoc-mentors-announce+unsubscribe(a)googlegroups.com.
Visit this group at http://groups.google.com/group/gsoc-mentors-announce.
For more options, visit https://groups.google.com/d/optout.
-----------------------------------------
Hi!
I noticed that some emails didn't get delivered, I don't have them
neither in spam folder but they are in the archive.
For example: of the last four mail of september sent by
trizonelabs(a)gmail.com I have just one in my inbox.
http://lists.libre-mesh.org/pipermail/dev/2015-September/date.html
It's just me or we have a faulty spam filter or some sending problems?
Bye!
Ilario
--
Ilario Gelmetti
iochesonome(a)gmail.com
igelmetti(a)iciq.es
ilario.gelmetti(a)estudiants.urv.cat
If you didn't read those emails from trizonelabs (see my last email
about emails not being delivered), here you are the really useful
document that was linked there:
http://simon.bugs3.com/lime-3zl/dokuwiki/doku.php
and its backup http://i4free-gr.eu5.org/info/lime-3zl/dokuwiki/doku.php
I vote for moving the two pages about libre-mesh on the official wiki.
Ilario
--
Ilario Gelmetti
iochesonome(a)gmail.com
igelmetti(a)iciq.es
ilario.gelmetti(a)estudiants.urv.cat
Hello people,
i'm taking dev.libre-mesh.org (and chef.altermundi.net) down for a brief
maintenance right now,
it should be back in less than an hour,
sorry for the inconvenience!
cheers
gui
Hello @all
i am very sorry that the link to
http://simon.bugs3.com/lime-3zl/dokuwiki/doku.php?id=libremesh:start seems
not to be working any more for reasons unknown.
I will try to save / move the content and let you know.
Cheers
3zl(Reinhard)
2015-02-05 14:00 GMT+02:00 <dev-request(a)lists.libre-mesh.org>:
> Send Dev mailing list submissions to
> dev(a)lists.libre-mesh.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.libre-mesh.org/mailman/listinfo/dev
> or, via email, send a message with subject or body 'help' to
> dev-request(a)lists.libre-mesh.org
>
> You can reach the person managing the list at
> dev-owner(a)lists.libre-mesh.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Dev digest..."
>
>
> Asuntos del día:
>
> 1. libremesh documenttion effort : start (3zl Trizonelabs)
> 2. Re: libremesh documenttion effort : start (Pau)
> 3. Re: Please put the subject next time (Pau)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 4 Feb 2015 21:17:26 +0300
> From: 3zl Trizonelabs <trizonelabs(a)gmail.com>
> To: dev(a)lists.libre-mesh.org
> Subject: [lime-dev] libremesh documenttion effort : start
> Message-ID:
> <
> CAJuY50wn0Zgce6FJraa4nWzoQuLyYh20kH-caX6nB1e1c0_r9g(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> As to sort raw intormation about the lime systems, we did start a dokuwiki
> at http://goo.gl/l23aks
>
> If things go well this might be transfered to any official libremesh docu
> site.
>
> We would appreciate any form of ideas,help or cooperation.
>
> Thank you
>
> 3zl(Reinhard)
> ------------ próxima parte ------------
> Se ha borrado un adjunto en formato HTML...
> URL: <
> http://lists.libre-mesh.org/pipermail/dev/attachments/20150204/693814bf/att…
> >
>
> ------------------------------
>
> Message: 2
> Date: Thu, 05 Feb 2015 09:35:15 +0100
> From: Pau <pau(a)dabax.net>
> To: dev(a)lists.libre-mesh.org
> Subject: Re: [lime-dev] libremesh documenttion effort : start
> Message-ID: <54D32B43.1040704(a)dabax.net>
> Content-Type: text/plain; charset="windows-1252"
>
> Hi.
> Documentation is something missing in libre-mesh, so it is a good idea
> to dedicate some efforts, thank you. However you might register into
> libre-mesh.org and create there the wiki page (following the redmine
> wiki syntax) instead of using a dokuwiki which is sightly different.
>
> Cheers.
>
> On 04/02/15 19:17, 3zl Trizonelabs wrote:
> > As to sort raw intormation about the lime systems, we did start a
> dokuwiki
> > at http://goo.gl/l23aks
> >
> > If things go well this might be transfered to any official libremesh docu
> > site.
> >
> > We would appreciate any form of ideas,help or cooperation.
> >
> > Thank you
> >
> > 3zl(Reinhard)
> >
> >
> >
> > _______________________________________________
> > Dev mailing list
> > Dev(a)lists.libre-mesh.org
> > https://lists.libre-mesh.org/mailman/listinfo/dev
> >
>
> --
> ./p4u
>
> ------------ próxima parte ------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 473 bytes
> Desc: OpenPGP digital signature
> URL: <
> http://lists.libre-mesh.org/pipermail/dev/attachments/20150205/6365b777/att…
> >
>
> ------------------------------
>
> Message: 3
> Date: Thu, 05 Feb 2015 09:39:26 +0100
> From: Pau <pau(a)dabax.net>
> To: dev(a)lists.libre-mesh.org
> Subject: Re: [lime-dev] Please put the subject next time
> Message-ID: <54D32C3E.8000406(a)dabax.net>
> Content-Type: text/plain; charset="windows-1252"
>
> By the way, this wiki page explains the network architecture of libre-mesh:
>
> http://libre-mesh.org/projects/libre-mesh/wiki/Network_Architecture
>
> It might be useful to understand the internals of the basic system.
>
> On 03/02/15 16:51, Gioacchino Mazzurco wrote:
> > On Tuesday, February 03, 2015 06:37:24 PM 3zl Trizonelabs wrote:
> >> 1.is there any "override" mechanism to stop lime-config touching
> >> original config files or params within ?
> >
> > Do you meana specific confg file ora you wanna prevent that lime-config
> edit
> > config files in general ?
> >
> >
> >> 2. overall view of the design "/usr/bin/lime-config" ( lua script
> >> with no "lua" extension ?)
> >
> > It just call all lime modules clean() and then configure() method
> >
> >
> >> 3. list of keywords used in "/usr/bin/lime-config" and respective
> >> scripts / files
> >
> > What you mean by keywords ?
> >
> >
> >> 4. there is some "mingle" between lime and lime-defaults - whats the
> >> meaning of "missing" compared to what.
> >>
> >> Next halt : Parsing of lime / lime-defauls and the respective list of
> >> keywords with their actions have to be carved out of the source
> >
> > For example the option lime.network.protocols is a necessary option so
> if the
> > user do not specify it in /etc/config/lime then the one from
> /etc/config/lime-
> > defaults (that the user must not touch) is taken
> >
> >
> >> btw : we have been really surprised by the numbers of interfaces been
> >> generated and digging deep to find out to which extent they are
> >> necessary and to what use
> >
> > Abstraction always come with a price, lime is a metafirmware so you can
> change
> > it's behavior dramatically just editing a couple of options, to have
> such a
> > level of abstraction we opted to use tagged vlans, mac vlan and some
> other
> > technique that have the "virtual draw back" of creating a lot of
> interfaces
> >
> >
> >> No organised site to store the documentation to ?
> >
> > http://libre-mesh.org/
> > We are mostly volunteers we document libre-mesh in our spare time, if
> you have
> > some resource to dedicate to us we will be happy to spend some more works
> > hours on developing/documenting lime, we also accept patches or if you
> wanna
> > write some docs you are welcome too
> >
> >
> > _______________________________________________
> > Dev mailing list
> > Dev(a)lists.libre-mesh.org
> > https://lists.libre-mesh.org/mailman/listinfo/dev
> >
>
> --
> ./p4u
>
> ------------ próxima parte ------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 473 bytes
> Desc: OpenPGP digital signature
> URL: <
> http://lists.libre-mesh.org/pipermail/dev/attachments/20150205/a3eee027/att…
> >
>
> ------------------------------
>
> _______________________________________________
> Dev mailing list
> Dev(a)lists.libre-mesh.org
> https://lists.libre-mesh.org/mailman/listinfo/dev
>
>
> Fin de Resumen de Dev, Vol 22, Envío 4
> **************************************
>
i build CC with luci 0.12 still containing Hex function
seems to be ok
FYI: i noticed https://github.com/libre-mesh/lime-packages/issues/7
as we are bound to openWRT CC on CPE210 maybe someone find a durable
solution so we could use luic for 15.x
cheers
3zl(Reinhard)
2015-09-15 15:00 GMT+03:00 <dev-request(a)lists.libre-mesh.org>:
> Send Dev mailing list submissions to
> dev(a)lists.libre-mesh.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.libre-mesh.org/mailman/listinfo/dev
> or, via email, send a message with subject or body 'help' to
> dev-request(a)lists.libre-mesh.org
>
> You can reach the person managing the list at
> dev-owner(a)lists.libre-mesh.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Dev digest..."
>
>
> Asuntos del día:
>
> 1. Re: lime-config error Hex (Ilario Gelmetti)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 14 Sep 2015 17:01:12 +0200
> From: Ilario Gelmetti <iochesonome(a)gmail.com>
> To: libre-mesh developement <dev(a)lists.libre-mesh.org>
> Subject: Re: [lime-dev] lime-config error Hex
> Message-ID: <55F6E138.50603(a)gmail.com>
> Content-Type: text/plain; charset="windows-1252"
>
> On 08/14/2015 09:33 PM, 3zl Trizonelabs wrote:
> > running lime-config get follung error and faulst in config files (%M %N
> > parameters not set)
> >
> > Chaos-calmer 15.05
> > LiMe 15.04 BigBang (15.04 rev.a1b8263 20150814_2143)
> >
> > lime-config
> >
> > /usr/lib/lua/lime/network.lua:35: attempt to call field 'Hex' (a nil
> value)
>
> Hi!
> This problem has been addressed by Pau, I suggest you to look into the
> discussion with subject "15.09 coming..." in the September archives of
> this list [0]. You can try the ip_legacy_module branch that should solve
> the issue [1].
> Let us know ;)
> Ilario
>
> [0] http://lists.libre-mesh.org/pipermail/dev/2015-September/thread.html
> [1] https://github.com/libre-mesh/lime-packages/tree/ip_legacy_module
>
> --
> Ilario Gelmetti
> iochesonome(a)gmail.com
> igelmetti(a)iciq.es
> ilario.gelmetti(a)estudiants.urv.cat
>
> ------------ próxima parte ------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 181 bytes
> Desc: OpenPGP digital signature
> URL: <
> http://lists.libre-mesh.org/pipermail/dev/attachments/20150914/1fd9850a/att…
> >
>
> ------------------------------
>
> _______________________________________________
> Dev mailing list
> Dev(a)lists.libre-mesh.org
> https://lists.libre-mesh.org/mailman/listinfo/dev
>
>
> Fin de Resumen de Dev, Vol 28, Envío 6
> **************************************
>
I am completing graduation in Computer Science, as subject of my final work I
have choosed to implement interoperability between Guifi.net classic networks
and Libre-Mesh based networks, the paper describe this work plus most parts of
Libre-Mesh meta-firmware.
The paper is public and released under creative common. If you spot some error
feel free to give feedback.
https://bitly.com/1KU6sRp
