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)
>Did you already read this ?
>https://github.com/libre-mesh/lime-packages/blob/develop/packages/lime-syst…>>/etc/config/lime
yes, we took this as a start for the analysis
>btw lime-default options are readed in case of something missing from lime
Questions :
1.is there any "override" mechanism to stop lime-config touching
original config files or params within ?
2. overall view of the design "/usr/bin/lime-config" ( lua script
with no "lua" extension ?)
3. list of keywords used in "/usr/bin/lime-config" and respective
scripts / files
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
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
No organised site to store the documentation to ?
regards
3zl(Reinhard)
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
/usr/bin/lime-config resp. /usr/lib/lua/lime:
as far we do understand these programs affect uci-config files in
/etc/config/ related to data in /etc/config/lime AND/OR
/etc/config/lime-defaults
list of keywords and their lime-configuration-action ( complete list ?? )
config lime <lime config class>
system
option
hostname
network
option
primary_interface <phys-interface>
list
protocols
lan ->
anygw ->
batman-adv
bmx
resolvers
<DNS ip ipv4>
<DNS-ip ipv6>
wifi
option
channel_2ghz
channel_5ghz
ap_ssid
adhoc_bssid
adhoc_mcast_rate
mesh_mesh_fwding
mesh_mesh_id
list
modes
ap
adhoc
override / prevail preset config-values
manual ?????
autogenerable ???
it would be very helpful for us and the project if anyone can shed a
profound light on this.
To trace the sourcecode for informations is too time-consuming, so we
wonder if there are any more documentation hidden somewhere.
We do believe, that a project like lime cannot survive without proper
system and user dokumentations and we are willing to start this.
Any kind of help is welcome
regards
3zl(Reinhard)
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
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
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 ;)
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
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!
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 ?