I noticed that the subdomain dev.libre-mesh.org runs with a self-signed
certificate, which is annoying because casual people browsing (and
security paranoid) won't accept to add an exception in order to read
more and will leave...
A free browser-accepted certificate can be obtained from StartSSL 
(for that specific domain, wildcards and extended verification certs are
not for free of course, but we there is no need for them).
Yesterday I tested the current implementation of the web interface LUCI2
 (which will replace LUCI in the future). The basic administration
menu (Network, WiFi, System, Status, etc.) is already implemented and
LUCI2 is a 100% rewritten web interface and it does not use lua anymore.
ubus via standard JSON. So it is quite more flexible and less resources
aggressive for the router (since the JS is executed in the client side).
I would recommend to start thinking in LUCI2 instead of LUCI, so we
should base the future LiMe web interface in LUCI2. Would be nice to
On Thursday, January 29, 2015 05:13:40 AM Pau wrote:
> Assigned #7 to @G10h4ck.
> Reply to this email directly or view it on GitHub:
Is this bug present in last stable or just in trunk?
If it is just in trunk i would wait that trunk stabilize a little before
changing stuff in libre-mesh to fix stuff like this
P.S. please keep dev(a)lists.libre-mesh.org in CC
I was looking at the bird integration developed during GSoC 2014, I would like
to integrate bird inside lime-proto-bgp.
Is there is some kind of mechanism that avoid routing loop if in the same bmx6
cloud there is more then one bmx-bird router ?
P.S. GSoC2014 tag should be added to the final post in the freifunk blog
acutally it have "GSoC 2014" as tag that make search a little difficult ;)
I wrote and commited a couple of packets in the new branch
bmx6-auto-gw-mode: watchping module for bmx6, it automatically announces
an Internet access in the network if detected. I added it as dependency
packet for lime-full
lime-eb-ip-tables: a meta-packet which includes the ebtables/iptables
required modules. If not enabled there is no NAT nor Masquerade in last
Comments or complains?
I have recently added a new topo server here in Aurea Social, the configuration
should be clean now, can you reserve the subnets
to it ?
At moment peering with other librenet6 islands work fine but i don't get
reponse if i try to ping6 googlez for example
On Friday, January 16, 2015 01:00:55 AM Pau wrote:
> While the name of the VLAN devices is now eth0-13 in the network
It shouldn't be like that
> configuration, bmx6 still uses the old format eth0_13. It seems to affect
> only ethernet interfaces.
This is the correct format as
I am still trying to reproduce the bug can you send me a tarball of /etc/config
what router model are you using ?
Here it is my proposal for fixing the firewall problem.
If firewall is installed, it does nothing new. But if it is not, it
creates a script to execute the /etc/firewall.user script on each boot.
It is very simple and works, so we don't need to depend on the whole
firewall shit, I mean thing.
If you like I will merge it to develop.
I have just pushed the feature/ground-routing branch to our git repo, the good
news is that it is already usable and working, the bad news is that it seems
that openwrt doesn't offer a way to know who switch%d is so it could arbitrary
be eth0 or eth1 depending on the model and seems there is no way to determine
it from software side -_-
what I have done now is assume in the code that swtich$i will be mapped to
eth$i and although it is not true it works on all device i have and on device
we use the most like tl-wdr3x00
what openwrt do is ship a spefic confing for each different device, this config is
manually written by the person who write the support for that device so plain
old boring manual human work...
what we can do is
1) leave stuff as is, so users with "unusual" devices have do do some adjust
2) Introduce some kind of very very hardware specific module like the unpopular
lime-hwd-tl-wdr3600 we had this summer for each device with a "switch map"
readeable by a program
3) Push openwrt developers to implement some kind of mechanism to make switch
map readeable from software side