lime-dev January 2015

lime-dev@lists.libremesh.org

5 participants
10 discussions

by David

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 [1] (for that specific domain, wildcards and extended verification certs are not for free of course, but we there is no need for them). [1] https://www.startssl.com/

9 years, 7 months

LUCI2 and LiMe

by Pau

Yesterday I tested the current implementation of the web interface LUCI2 [1] (which will replace LUCI in the future). The basic administration menu (Network, WiFi, System, Status, etc.) is already implemented and works fine. LUCI2 is a 100% rewritten web interface and it does not use lua anymore. It is just a small uhttpd plug-in which communicates Javascript with 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 have some JavaScript expert into the team :) Cheers. [1] http://wiki.openwrt.org/doc/techref/luci2 -- ./p4u

9 years, 10 months

Re: [lime-dev] [lime-packages] luci.ip.Hex() does not exist anymore (#7)

by Pau

It is not trunk neither stable, it is just "LUCI", the repository "http://git.openwrt.org/project/luci.git". We are using it in all LiMe Branches. On 29/01/15 14:32, Gioacchino wrote: > 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: >> https://github.com/libre-mesh/lime-packages/issues/7#event-226805821 > > 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 > > --- > Reply to this email directly or view it on GitHub: > https://github.com/libre-mesh/lime-packages/issues/7#issuecomment-72023720 > -- ./p4u

9 years, 10 months

Re: [lime-dev] [lime-packages] luci.ip.Hex() does not exist anymore (#7)

by Gioacchino Mazzurco

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: > https://github.com/libre-mesh/lime-packages/issues/7#event-226805821 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

9 years, 10 months

bird-openwrt

by Gioacchino Mazzurco

Hi! 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 ? Thanks! 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 ;)

9 years, 10 months

bmx6 auto-gw module for watchping

by Pau

I wrote and commited a couple of packets in the new branch feature/bmx6-auto-gw-mode 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 openwrt trunk Comments or complains? https://github.com/libre-mesh/lime-packages/tree/feature/bmx6-auto-gw-mode -- ./p4u

9 years, 10 months

Librenet6 subnet request

by Gioacchino Mazzurco

Hi! I have recently added a new topo server here in Aurea Social, the configuration should be clean now, can you reserve the subnets 2a00:1508:1:f017::/64 2a00:1508:1:f000::aea/128 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 Thanks!

9 years, 11 months

Re: [lime-dev] [lime-packages] BMX6 do not configure properly ethernet devices (#6)

by Gioacchino Mazzurco

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 network.protoVlanSeparator="_" I am still trying to reproduce the bug can you send me a tarball of /etc/config what router model are you using ?

9 years, 11 months

Firewall issue fixed in feature/new-firewall branch

by Pau

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. https://github.com/libre-mesh/lime-packages/commit/e76bc740dfa20dc581a905a4… 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. Cheers. -- ./p4u

9 years, 11 months

Ground routing branch

by Gioacchino Mazzurco

Hi all! 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 after lime-config 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

9 years, 11 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

lime-dev January 2015