lime

lime-users@lists.libremesh.org

493 discussions

Re: [lime-users] How to get self-configured IPV6 on LiMe

by Ilario

Hi :) Actually I have no idea of how to join LibreNet6 and LibreMesh, I'm not an active LibreNet6 user... For sure you have to plug a working IPv6 gateway in the WAN port of a LiMe router, if this doesn't automagically work _I suppose_ you will have to issue some bmx6 command equivalent to this one (which is for IPv4): https://github.com/libremesh/lime-packages/blob/develop/packages/bmx6-auto-… Anyone with experience on this? 2016-10-26 16:53 GMT+02:00 Leonardo Taborda <leonardotaborda(a)networkbogota.org>: > Hello Ilario! > > > We want to deploy IPV6 in our nodes. We have got already an IPV6 range from > Librenet6: 2a00:1508:1:f024::/64 --> NetworkBogota.org > > Anyways, when i noticed the feature on LiMe I though it was like just pick a > range and you are on the way, but it is not working. Routers and clients > receive a global routable ipv6 address but it is not reaching internet since > you can't ping6 google or pass an ipv6 test. > > I appreciate some help on this, since we want access to isolated nodes and > their services.

8 years, 9 months

[lime-users] propagating settings

by Marvin Arnold

We have multiple lime nodes connected to each other. How can we have hostnames we set on one router propagate to the entire network? A related issue is that I am trying to install Sandstorm on a small computer in the network. As far as I can tell from the instruction <https://docs.sandstorm.io/en/latest/administering/faq/#can-i-run-sandstorm-…>, this should be possible if I setup a dnsmasq <https://davejamesmiller.wordpress.com/2013/03/14/installing-dnsmasq-wildcar…>. Is it clear to anyone whether this needs to be done on the sandstorm server, or on the lime router, or across the entire lime network?

8 years, 9 months

Re: [lime-users] atualizando fumaça para chaos calmer

by Gui Iribarren

On 30/10/16 13:19, bruno vianna wrote: > oi gui > > como vamos reinstalar várias coisas lá na rede, estou fazendo uma versão > do firmware atualizada para chaos calmer. aí tem duas coisas que reparei: > > - o vale.sh não está no repositório de pacotes do chaos calmer, tem como > adicionar? hm. boa pergunta. na real tenho pendente dar uma ajeitada naquele pacote, fazer interface web, e tal. Ta no roadmap para meados de 2017 :( por enquanto, ja q vc eh uma das 2 o 3 pessoas no mundo q entende como funciona :P pode fazer um "opkg install http://chef.altermundi.net/downloads/r44952/ar71xx/packages/lime_packages/v…" logo apos flashejar > > - a gambiarra que tinha no /etc/uci-defaults/93_dns-alias-for-anygw para > dar o escopo de endereços de 10.7. para fumaça, e reservar alguns ips > fixos, não tá funcionando. a rede continua gerando ips no escopo 10.87. > > o arquivo tava assim: > ### copied from fumacaonline profile 1509 > ### Workaround dhcp-range con espacio para ips estaticas > sed -i '\|^dhcp-range=tag:anygw,10.7.|s/10.7.0.2/10.7.4.0/ > <http://10.7.0.2/10.7.4.0/>' /etc/dnsmasq.d/lime-proto-anygw-10-ipv4.conf ah, acho q ja temos um jeito "oficial" de fazer uma coisa parecida a traves do /etc/config/lime-defaults eh uma coisa do tipo option main_ipv4_address '10.7.0.0/16/17' ou seja, network /16, mas com autoassignacao restrita a "primeira metade" (/17), isto eh, vc pode ficar tranquilo q os pontos terao ips entre 10.7.0.1 e 10.7.127.254 (= 10.7.0.0/17) e usar a 2da metade para ips estaticas confundido? pergunta pro Ilario que foi o ideador ;) Gracias ilario!! Una "gambiarra" (chapuceria) menos en brasil > > ### Workaround dns domain > uci set dhcp.(a)dnsmasq[0].local=/rede.fumacaonline.org.br/ > <http://rede.fumacaonline.org.br/> > uci set dhcp.(a)dnsmasq[0].domain=rede.fumacaonline.org.br > <http://rede.fumacaonline.org.br> tambem implementamos oficialmente esto en /etc/config/lime-defaults en tu caso seria: config lime system option domain 'rede.fumacaonline.org.br' :)

8 years, 9 months

[lime-users] Ubiquiti UAP AC PRO

by Juergen Kimmel

Any experiences or suggestions related to Ubiquiti UAP AC PRO?

8 years, 10 months

[lime-users] Fwd: Testing Libremesh develop on UBNT bullet M

by Gui Iribarren

Hey Pau, here's a report from someone testing develop. @Juergen, unless you're specifically interested in debugging bleeding edge develop, i'd suggest you to try with the latest stable release "Community Chaos", you'll find it at the same builds.libremesh.org for a better first time experience :) -------- Ursprüngliche Nachricht -------- Von: Juergen Kimmel <juergenkimmel(a)gmail.com> Gesendet: 31. Oktober 2016 11:55:22 MEZ An: Gui Iribarren <gui(a)altermundi.net> Betreff: Re: [libre-9344] Testing Libremesh Hi, yes I'm a subscriber. I tried factory and sysupgrade and both with "-n" with http://builds.libremesh.org/develop/ar71xx-generic- develop/lede-ar71xx-generic-ubnt-bullet-m-squashfs-sysupgrade.bin During flashingthe following message showed up: "/usr/lib/lua/luci/dispatcher.lua:433: Failed to execute function dispatcher target for entry '/'. The called action terminated with an exception: /usr/lib/lua/luci/dispatcher.lua:433: Failed to execute firstchild dispatcher target for entry '/status'. The called action terminated with an exception: /usr/lib/lua/luci/dispatcher.lua:433: Failed to execute template dispatcher target for entry '/status/index'. The called action terminated with an exception: /usr/lib/lua/luci/template.lua:97: Failed to execute template 'status/index'. A runtime error occured: /usr/lib/lua/luci/util.lua:587: Unable to establish ubus connection stack traceback: [C]: in function 'assert' /usr/lib/lua/luci/dispatcher.lua:433: in function 'dispatch' /usr/lib/lua/luci/dispatcher.lua:168: in function </usr/lib/lua/luci/dispatcher.lua:167>" FYI the following message I encountered at http://10.13.0.1/cgi-bin/luci/admin/status/routes > /usr/lib/lua/luci/dispatcher.lua:460: Failed to execute template dispatcher target for entry '/admin/status/routes'. > The called action terminated with an exception: > /usr/lib/lua/luci/template.lua:97: Failed to execute template 'admin_status/routes'. > A runtime error occured: /usr/lib/lua/luci/tools/webadmin.lua:99: attempt to call method 'sub' (a nil value) > stack traceback: > [C]: in function 'assert' > /usr/lib/lua/luci/dispatcher.lua:460: in function 'dispatch' > /usr/lib/lua/luci/dispatcher.lua:141: in function Regards Gui Iribarren <gui(a)altermundi.net> schrieb am Sa., 29. Okt. 2016 um 04:22 Uhr: On 18/09/16 20:31, Juergen Kimmel wrote: > Two Picostations > Two TP-Link WR841ND V 8.0 > > LEDE Reboot r1278 / LuCI Master (git-16.251.61906-44bf3f0) > > Besides many other issues I start with this one: > > /usr/lib/lua/luci/dispatcher.lua:460: Failed to execute template dispatcher target for entry '/admin/status/routes'. > The called action terminated with an exception: > /usr/lib/lua/luci/template.lua:97: Failed to execute template 'admin_status/routes'. > A runtime error occured: /usr/lib/lua/luci/tools/webadmin.lua:99: attempt to call method 'sub' (a nil value) > stack traceback: > [C]: in function 'assert' > /usr/lib/lua/luci/dispatcher.lua:460: in function 'dispatch' > /usr/lib/lua/luci/dispatcher.lua:141: in function > > No idea what this is about, you will enlighten me I think. > > Nobody else on this mailing list? I will see whether it is alive or not. hey juergen! did you manage to subscribe to...? https://lists.libremesh.org/mailman/listinfo/lime-users anyway, regarding the errors you mention, a couple of questions: 1) where did you get the libremesh binary you're testing? (URL) 2) how did you flash it? using "sysupgrade"? in that case, did you preserve your configuration or instead discarded it using "sysupgrade -n" ? (you should discard it) 3) what happens if you run "firstboot" and reboot? cheers! > > > _______________________________________________ > libre-9344 mailing list > libre-9344(a)lists.libre-mesh.org > https://lists.libre-mesh.org/mailman/listinfo/libre-9344 >

8 years, 10 months

[lime-users] Picostation M2 configure Wan

by Juergen Kimmel

I upgraded my Picostation M2 with http://builds.libre-mesh.org/community_chaos/16.07/ar71xx/generic/openwrt-1… I don't find where to configure WAN for ETH0. It seems to me the interface is missing and I don't know how to create.

8 years, 10 months

[lime-users] Release 16.07 "Community Chaos" officially out

by Gui Iribarren

Thanks to everyone involved, finally we have an official release! * generic binaries, meant for testing or setting up temporary networks (i.e. when having the default AP SSID = LibreMesh.org is fine) http://downloads.libremesh.org/community_chaos/16.07/ * customized binaries with chef, meant for stable community networks (basically, you can preset a specific AP SSID and other settings common to the whole network, and then flash many routers in a row) can be generated at: http://chef.libremesh.org/ Changelog since "BiggestBang" 15.09: • Now based on OpenWrt Chaos Calmer 15.05.1 • Removed "firewall" package (which is included by default in vanilla OpenWrt/LEDE), since it's not really being used in LibreMesh setup. It can always be installed on a case-by-case basis using opkg. ∘ there's a new minimal system that runs /etc/firewall.lime on boot (if "firewall" is not installed) • Removed "odhcpd" since we're not using it at the moment (we use dnsmasq) • Removed "odhcp6c" since we're not using it at the moment (we still haven't solved how to deal with native IPv6 coming over WAN, i.e. propagate a delegated prefix over the mesh in a reasonable way) • New default packages: "lime-hwd-openwrt-wan" and "lime-proto-wan". This checks if there's a WAN port, and automatically configures as "wan" proto (lime-proto-wan). The "wan" proto let's you assign in /etc/config/lime, for example, 802.1ad VLANs over the WAN port. • New default package: "lime-hwd-ground-routing". Allows you to configure 802.1q VLANs on embedded switches, so that you can separate specific ports and put • New default package: "bmx6-auto-gw-mode", so that when a node detects (with watchping) it can ping 8.8.8.8 over WAN port, a bmx6 tunIn is created on-the-fly, and Internet is shared to the rest of the clouds. • Workaround for an spurious log message caused by BATMAN-Adv ("br-lan: received packet on bat0 with own address as source address"): a "dummy0" interface is created and added to bat0, with a slightly different MAC address ∘ https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2014-March/011839.html • New available packages: "lime-proto-bgp", allows to do BGP with bird daemon; and "lime-proto-olsr", "-olsr2" and "-olsr6", which add support for all versions of OLSR. • Some new settings possible in /etc/config/lime-defaults ∘ wireless.htmode lets you preset the htmode for any wireless radio (or htmode_2ghz and htmode_5ghz for specific bands) ∘ wireless.distance is the equivalent, for setting distance (and distance_2ghz / _5ghz) ∘ system.domain for setting a cloud-wide domain name • New "named AP" interface by default: in addition to the shared SSID (where clients roam between nodes), there's a new AP with a different, unique SSID (it includes the node hostname). This lets people easily check with any stock smartphone (not only Android with a special app) which nodes are online, nearby, and their respective signal strength. Most importantly, it lets them connect to a specific AP and prevent roaming, when they need it. Roaming is a nuisance if you're in the middle of two nodes, with similar RSSI, but different performance (bandwidth to Internet). Finally, it gives users a very easy way to reliably access a specific (nearby) node webinterface, simply associating to a specific AP and browsing to http://thisnode.info/ • Fixed all alfred facters (bat-hosts, dnsmasq-distributed-hosts, dnsmasq-lease-share), so that they retry the "alfred -r" when it fails (i.e. in slave mode) • LiMe web interface received love: ∘ luci-app-lime-location (Simple Config -> Location) now works ∘ Simple Config -> Advanced

8 years, 11 months

[lime-users] Renamed Libre-Mesh to LibreMesh

by Gui Iribarren

Hello people, back in sep/2014, Ilario suggested to register libremesh.org: http://lists.libre-mesh.org/pipermail/dev/2014-September/000458.html we did, and after a looong transition, we're finally finishing all the renamings, right on time before the new release (so we're taking the opportunity to launch 16.07 with the new name) back in march, we took the decision to migrate everything, then at the last meeting consensus was *against* migration (among concerns, was breaking github urls, and such); but recently found out about github retrocompatibility features, and finally reached consensus approving the migration. Affected: * IRC: channel #libre-mesh is deprecated, join #libremesh from now on * GitHub repos: all the legacy urls continue to work (but deprecated) example: git clone https://github.com/libre-mesh/lime-packages.git still works, but you should clone from now on: git clone https://github.com/libremesh/lime-packages.git so all the existing lime-builds out there will continue to work, pointing to the legacy URLs, pulling changes without problem but if you're reading this, and have already existing repos in your computers, please change remote's URLs, like so: https://help.github.com/articles/changing-a-remote-s-url/ The only thing that will not work anymore is the old's organization "homepage" in github, i.e. the list of repos https://github.com/libre-mesh/ doesn't work anymore. use https://github.com/libremesh/ instead. This caveat is mentioned in https://help.github.com/articles/renaming-an-organization/ * Repo contents: everything was renamed in 1 commit to each repo branch: https://github.com/libremesh/lime-build/commit/071a90b85 https://github.com/libremesh/lime-build/commit/dde93693a https://github.com/libremesh/lime-packages/commit/4c0bd49e70 https://github.com/libremesh/lime-packages/commit/7f18ad3597 https://github.com/libremesh/lime-web/commit/b78a0d57c * Chef: All the mentions about Libre-Mesh were replaced to LibreMesh back in march/april already. * Mailing lists: they'll be transparently renamed to lime-*(a)lists.libremesh.org (pipermail archives, subscribers, etc) and the @lists.libre-mesh.org will be deprecated (mail sent to the deprecated address will be held, and senders notified the new addr) this will also involve moving to a better maintained mailman server This last step (mailing lists) is not done yet, to allow people to get this notice first, and update their email filters / etc. Please do so, since this email is the last one you'll get from *(a)lists.libre-mesh.org. You'll soon get a "Welcome" message from lime-*(a)lists.libremesh.org cheers! and see you on the other side of the mirror, with a freshly cooked release.

8 years, 12 months

[lime-users] alterchef migrated to Django 1.9

by Pablo Castellano

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey all. I just wanted to share with you that some weeks ago I migrated alterchef source code from Django 1.4 to Django 1.9. Requirements are almost the same but: - - South is not a requirement anymore since Django ships its own migration mechanism for a while now. - - Django-jsonfield now replaces the implementation of JSONField These changes are available in my django1.9 branch in GitHub. Since I don't know about the current VCS you are using (Mercurial) I preferred to migrate first to Git and then work. Feel free to merge them (but please respect authorship). I also encourage you to change VCS ;) Main repo: https://colectivo.altermundi.net/projects/chef My repo (django-1.9 branch): https://github.com/PabloCastellano/alterchef/tree/django-1.9 Commit log: https://github.com/PabloCastellano/alterchef/commits/django-1.9 I also started migrating the code to Python 3 while keeping compatibility with Python 2 but it turned out to be more tedious than expected and I stopped it. I think the best is just migrating to Python 3 without keeping compatibility. Regards, Pablo. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJXm6upAAoJEHj0TzpGP5GcuewP/0MXaV79TtiiGBNDxetf3Fwu vM2WFDPhcP3T1PLTWsn/2HCPZc4Xu942DotxCqgYdXgCBogBuiLBF+1SSCBBjHvj oRn136ozA2eY5UpSbX4BA0RxO66uo5suDBfvtzPBdaEwkYW4DFH4jnxR6z2sozan wr8DHRdIGbKlgYQ9vNnc8sKWWD7edR8zalBhVIWhRPpoEpRPIFYMrI6dwzCVcBhN bF18srldEcDD4nZIB3yDtd5gNcIryB+dnGs+MhJxLpK77O+0KWEMnz+rAFYfObn5 UFJ5ClfIyAmrRuIGSl+3dMlZS9Ub8M/N2bW6mimJmMBv4VZYbgVR4SYdeI8WUDRR HOm6gqYwff5gcHFKnUNu3U/lHNTA+vQ/UA9lGqR9aD3i5FK6gt27XPROSq1KG7j5 ECDx+FzxdqIx7NMZ1pbwNEFSyVmbM7Y4OPDOeLyb9WSS1OPtZFDqH1AKSRaa2TPj wwAlibhMIlQw6flIeq0SE2XF4Yh8ypIMhf4nouzYlL2jbtScwlQeYll5tzRmBTaU Nl36wEwBJ6snhE9cCIwJfmOVm1N+Ki91/kcZdCsVrlNkygoS3k76H0cl9t/G86Sg Rq1q99LDT1PmfMwcqFQDu7ZRdjtJYR5S8tib0zzxu/qSD3NOtmCDPFiZGCdBKV+b DAIGwJl6uQIN0zODFusT =ksaf -----END PGP SIGNATURE-----

9 years

[lime-users] Fwd: [lime-dev] 16.07 in the wild

by Ilario

Finally we have a new release! Welcome 16.07 or CommunityChaos :D The release is not yet included in Chef, it will be in a short time, until then you can build locally the firmware using lime-build :) If you find a bug please report it! ---------- Forwarded message ---------- From: Gio <gio(a)diveni.re> Date: 2016-08-08 13:53 GMT+02:00 Subject: [lime-dev] 16.07 in the wild To: dev(a)lists.libre-mesh.org Hi! I saw Gui merged las fixes in 16.07 toniight, so i consider 16.07 is the latest LiMe release I have just switched the default branch of lime build from testin/16.07 to 16.07 so now it will build by default latest stable release :) Congrats! _______________________________________________ Dev mailing list Dev(a)lists.libre-mesh.org https://lists.libre-mesh.org/mailman/listinfo/dev

9 years

← Newer
1
...
41
42
43
44
45
46
47
...
50
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

lime