We try to incroporate Lime into network which is CC only (for techn.reasons)
So thank you very much for your efford.
Will test ist ASAP with new test-builds on BR15L and gathering some more
dokumentation.
Keep up the good work !
3zl / Reinhard
Hi!
DISCLAIMER: This mail contain sarcasm! Please don't take it as a personal
insult but as an occasion to make fun of our own code and learn ;)
This morning I was reviewing the branch that claimed to fix incompatibilities
with Chaos Calmer, I even re-based it on top of current develop and gave it a
name that fits more in our branch naming convention...
After some testing and reading I decided to not merge it and to rewrite it
from scratch instead.
Some shitty part of our code that was network.generate_host instead of using
the IP API was messing a lot with CIDR private internals, as Lua is so
indulgent it didn't refused to run but our code was a real mess!
In the new version of the library that part has been rewritten in C and to Lua
it exposed just the API so our shitty code can't mess with the private stuff
anymore, in this situation our reaction instead of fixing our shitty code has
been to copy the old luci code before putting it inside our core and then
(more reasonably) as a separate package...
This morning I have decided to do what we should have done since the
beginning:
rewrite the shit code so we don't need the old library anymore, in this
process I even discovered a Luci bug that Jow has already fixed (a missing
dependency)
I was tempted to delete the wrong branch but i decided that is a good idea to
keep it some week more so we all have time to review and understand what we
have done wrong
https://github.com/libre-mesh/lime-packages/tree/sandbox/ip_legacy_module
And here it goes the branch with the proper solution
https://github.com/libre-mesh/lime-packages/tree/sandbox/hotfix/luci-lib-ip
I have already tested it if no one oppose this I'll merge it in the following
days.
Cheers!
Hi!
I was reviewing our repo and found out lot of personal branch out of the
naming scheme we consensuated got inside our main repo.
I believe this happened by accidental error because all members of our github
organization has admin right on all repositories, i am changing this so there
is no possibility of pushing accidentally unwanted stuff and a pull request
have to be done
Cheers!
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
