- lime-dev - listas.altermundi.net

Firewall issue fixed in feature/new-firewall branch

by Pau

Here it is my proposal for fixing the firewall problem. If firewall is installed, it does nothing new. But if it is not, it creates a script to execute the /etc/firewall.user script on each boot. https://github.com/libre-mesh/lime-packages/commit/e76bc740dfa20dc581a905a4… It is very simple and works, so we don't need to depend on the whole firewall shit, I mean thing. If you like I will merge it to develop. Cheers. -- ./p4u

10 years, 4 months

1
0
0 0

Ground routing branch

by Gioacchino Mazzurco

Hi all! I have just pushed the feature/ground-routing branch to our git repo, the good news is that it is already usable and working, the bad news is that it seems that openwrt doesn't offer a way to know who switch%d is so it could arbitrary be eth0 or eth1 depending on the model and seems there is no way to determine it from software side -_- what I have done now is assume in the code that swtich$i will be mapped to eth$i and although it is not true it works on all device i have and on device we use the most like tl-wdr3x00 what openwrt do is ship a spefic confing for each different device, this config is manually written by the person who write the support for that device so plain old boring manual human work... what we can do is 1) leave stuff as is, so users with "unusual" devices have do do some adjust after lime-config 2) Introduce some kind of very very hardware specific module like the unpopular lime-hwd-tl-wdr3600 we had this summer for each device with a "switch map" readeable by a program 3) Push openwrt developers to implement some kind of mechanism to make switch map readeable from software side

10 years, 4 months

2
2
0 0

Libre Mesh feature/ground_routing merged in develop

by Gioacchino Mazzurco

Hi all! I have been working on adding support for ground routing in libre-mesh in this days around winter solstice, today i have done various tests and as they satisfied me i have merged the work on develop branch, although it is stable and usable, some buggy switch chip of some router like tl-wdr3500 need some little (remove Ground routing port from other vlans) configuration tweaking after lime autoconfiguration, while for example the tl-wdr3600 works out of the box Moreover ground routing works also with CPE that doesn't have an integrated switch like e ubnt-bullet :) Debugging/Patches/Feedback are all welcome https://github.com/libre-mesh/lime-packages/commit/03202c811e3d3a208a28b35b…

10 years, 4 months

1
0
0 0

Testing LiMe in last trunk

by Pau

Today I have compiled and installed the last libre-mesh develop branch with the last openwrt-trunk. Congratulations to everyone! It worked fine almost out-of-the-box. The next points are my thoughts/questions regarding the current state of lime: 1) The firewall problem is not yet fixed, so raw images which does not include the firewall packet are not properly working. 2) Last OpenWRT/trunk does not have the iptables nat module (CONFIG_PACKAGE_kmod-ipt-nat) by default enabled (WTF?), so it should be added as dependency for lime-system. May be also related with the default strip kernel/libraries options (which comes enabled). 3) Would be nice to write the current options (even if they are the default ones) to /etc/config/lime once the lime-config script is executed. So it should 1) use the options specified in the file 2) fill the non-specified options. Then in the config file you got a picture of the current whole system configuration, when you upgrade the node these options are preserved and the node is configured in the same exact way it was before. 4) Is there any way to specify: "do no configure (or ignore) this radio device" to lime-config? 5) In my tests, when I try to set some parameters for a specific radio device (i.e only radio1), lime-config crashes. My first thought is that if there is a specific configuration for radioX, lime-config expect to find all the needed parameters there. I think it should try to find first the parameters in the specific configuration and afterwards (if the parameter does not exist) look in the generic/default wifi configuration section. -- ./p4u

10 years, 4 months

3
4
0 0

Parametric ssid implemented

by Gioacchino Mazzurco

Hi all! now adhoc_ssid is parameterizable with %H that will be substituted by hostname and with %Mn that will be substituted by the n'th byte of the device primary mac address, if you have personal clones and wanna test the feature just rebase on top of develop branch

10 years, 5 months

1
0
0 0

Interface-dependent IPv6 prefix

by Marc Juul

We're having the problem that bmx6 nodes sometime come up on different subnets. The interfaces are getting fd66:0066:0066:00XX::/64 IPs, where XX is the interface index. This means that some nodes are on different subnets, since they don't all have the same wifi interface index. Is this intentional, and if so, why? It means that just running "bmx6 dev=wlan0" on each node will not result in a working mesh where every node can reach every other node on their bmx6-assigned addresses. It seems that either the mask should be changed to /56 or the interface index should be used as the eigth or higher byte instead of the seventh? Perhaps it would be better to replace the ff:fe inserted into the middle of the MAC address with the interface index? Here's the responsible code from https://github.com/axn/bmx6/blob/master/ip.c: if (!global_prefix_cfg.mask && !dev->global_prefix_conf_.mask && autoconf_prefix_cfg.mask) { autoIP6 = bmx6AutoEUI64Ip6(dev->if_link->addr, &autoconf_prefix_cfg); autoIP6.mask = DEF_AUTO_IP6_DEVMASK; autoIP6.ip.s6_addr[6] = DEF_AUTO_IP6_BYTE6; autoIP6.ip.s6_addr[7] = (uint8_t)dev->if_link->index; //different ULAs for equal MAC addresses!! } -- marc/juul

10 years, 5 months

2
1
0 0

default values in config/lime

by David

The file /etc/config/lime seems to follow the same reasoning behind many other projects' default config, that is some commented lines that show how the conf should look like in the most frequent scenarios. In lime (branch:release/14.08) the comments are very self-explanatory but the example is for configuring radio1 and radio2 while 99% of the devices have radio0 and at most radio1... I think that should be changed because for a noob user like me it is misleading to show examples for radio1 and 2, while the radios are numbered from 0. What do you think about it?

10 years, 6 months

2
3
0 0

generate_host(...) and manual address

by Gioacchino Mazzurco

Hi! It seems to me that the actual generate_host(...) function doesn't permit to de user to specify completely it's address on /etc/config/lime, what i see is that if the user specify as example 10.10.10.10/24 as his ip address the last nibble get overridden by generate_host(...) function, is this the expected behavior? If so i would change that giving the user the possibility to specify completely it's ip address Cheers!

10 years, 6 months

2
3
0 0

Libre-Mesh IPv6 subnet

by Gioacchino Mazzurco

Hi all! I remember that guifi.net assigned to libre-mesh an IPv6 subnet bigger then the one we have for librenet6 so we can do the mapping of assigend ipv4 -> ipv6 i remember also a wikipage explaining the mechanism, someone remember more details ?

10 years, 6 months

2
1
0 0

bmx6 hung on boot

by Gioacchino Mazzurco

I had to reopen bug #28 because it is happening in Barrier Breaker http://www.libre-mesh.org/issues/28

10 years, 6 months

2
3
0 0

Firewall and ebtables

by Pau

I noticed about strange behaviors in the last binaries compiled for 14.08 branch. The packets to Internet were duplicated and things were weird in general. I found the problem, since the ebtables rules for preventing the anycast IP propagation were put to the user.firewall directory, if the firewall is not installed they are not executed. So, we have two solutions to this problem: 1. Add the firewall as dependency for LiMe 2. Execute these rules (and others which may be needed) separately by some lime process. What do you think? -- ./p4u

10 years, 6 months

2
1
0 0

map.libre-mesh.org - to do it something official?

by al

Hi! Pre 1: As a regular guifi.net speaker I know about how much important is the map for empower the idea of community networks. In a speech people understand community networks and the power they have in moment when they see guifi.net maps like: http://guifi.net/en/node/2413/view/map or, nicer for normal people: http://guifi.net/en/guifi/menu/stats/growthmap ("Init" | "Play") Pre 2: If you take a look to "site:libre-mesh.org" in a search engine (that is something a lot of people do in order to understand a website) we can see there http://map.libre-mesh.org/ which is working with a lot of nodes. We know more or less that we are not using that map, so it is not fully updated. Content: Let's do some official in http://map.libre-mesh.org/ or, at least, let's plan it. Salut!

10 years, 6 months

2
1
0 0

Commotion Call

by Pau

The OTI is funding projects for mesh network deployment, here is the call: https://commotionwireless.net/blog/2014/10/08/call-for-proposals-small-gran… It looks like they expect the people who apply to use Commotion, but maybe I'm wrong. If someone here has more information it would be appreciated. Cheers. -- ./p4u

10 years, 6 months

4
3
0 0

Logical name not supported in device section

by Gioacchino Mazzurco

Hi! This commit b7cf9e84106ee1aadd028aa526ac12ea82ba3a7e [0] break vlan creation ( vlan are not created anymore ) because @logical_name is not supported in device sections, moreover in most cases like @lm_eth0 logical name refer to a nonexistent logical interface, if netifd suffer race conditions on boot then the problem is inside netifd and cannot be worked around this way, in fact we don't get the race condition anymore but because the device is just not created anymore, we should fix netifd submitting patch to openwrt-devel/Felix if we wanna race conditions solved not break our meta-firmware ;) [0] https://github.com/libre-mesh/lime-packages/commit/b7cf9e84106ee1aadd028aa5…

10 years, 7 months

1
2
0 0

GSoC 2015 announced

by Gioacchino Mazzurco

http://www.google-melange.com/gsoc/homepage/google/gsoc2015

10 years, 7 months

1
0
0 0

OpenWRT tool to align your antenna

by Pau

It is in Catalan but easy to understand for anybody. http://guifi.net/ca/node/72965 We may probably use it as-is for LiMe, what do you think? -- ./p4u

10 years, 7 months

2
1
0 0

Fwd: [OpenWrt-Devel] Barrier Breaker 14.07 Final

by Gioacchino Mazzurco

---------- Forwarded Message ---------- Subject: [OpenWrt-Devel] Barrier Breaker 14.07 Final Date: Thursday 02 October 2014, 14:59:08 From: Steven Barth <cyrus(a)openwrt.org> To: openwrt-devel(a)lists.openwrt.org The OpenWrt developers are proud to announce the final release of OpenWrt Barrier Breaker. _______ ________ __ | |.-----.-----.-----.| | | |.----.| |_ | - || _ | -__| || | | || _|| _| |_______|| __|_____|__|__||________||__| |____| |__| W I R E L E S S F R E E D O M ----------------------------------------------------- BARRIER BREAKER (14.07) ----------------------------------------------------- * 1/2 oz Galliano Pour all ingredients into * 4 oz cold Coffee an irish coffee mug filled * 1 1/2 oz Dark Rum with crushed ice. Stir. * 2 tsp. Creme de Cacao ----------------------------------------------------- http://downloads.openwrt.org/barrier_breaker/14.07/ Important changes since RC3 * various ath9k related fixes * a few board related fixes * fixes for packages depdending on curl * per feed download folders Important changes since RC2 * NAT & firewall throughput improvements * Security updates for OpenSSL & PolarSSL * Minor fixes in DHCP & DHCPv6 handling * Configuration support for GRE tunnels * Various other fixes Important changes since RC1 * fix a long standing ath9k deadlock bug * all feeds are now built * image builder now works and RC2 contains all board specific images * various board/stability fixes ** Highlights since Attitude Adjustment ** Default configuration and images * Linux kernel updated to version 3.10 * Procd: new preinit, init, hotplug and event system written in C * Native IPv6-support - RA & DHCPv6+PD client and server - Local prefix allocation & source-restricted routes (multihoming) * Filesystem improvements - Added support for sysupgrade on NAND-flash - Added support for filesystem snapshot and rollback - Rewritten mounting system in C for rootfs and block devices * UCI configuration improvements - Support for testing configuration and rollback to working last working state - Unified change trigger system to restart services on-demand - Added a data validation layer * Networking improvements - Netifd now handles setup and configuration reload of wireless interfaces - Added reworked event support to allow obsoleting network hotplug-scripts - Added support for dynamic firewall rules and zones - Added support for transparent multicast to unicast translation for bridges - Various other fixes and improvements Additional highlights selectable in the package feeds or SDK * Extended IPv6-support - Added DS-Lite support and improved 6to4, 6in4 and 6rd-support - Experimental support for Lightweight 4over6, MAP-E and MAP-T - Draft-support for self-managing home networks (HNCP) * rpcd: new JSONRPC over HTTP-frontend for remote access to ubus * mdns: new lightweight mdns daemon (work in progress) * Initial support for the musl C standard library * Support for QMI-based 3g/4g modems * Support for DNSSEC validation * Added architecture for package signing and SHA256 hashing * ... and many more cool things Package feed reorganization For quite a while already we are not very satisfied with the quality of the packages-feed. To address this, we decided to do a fresh start on GitHub. The new feed https://github.com/openwrt/packages should be used from now on and package maintainers are asked to move their packages there. For the final release we will still build the old packages feed but it will be necessary to enable it manually in the opkg package list to be usable. Additionally we would like to give a big thank you to all of our package maintainers working on our various feeds. New build servers We would like to express our gratitude to Imagination Technology for funding the 2 build servers that we used for the release. Whats next ? We aim at releasing Chaos Calmer (CC) before the end of the year. The CC release will use 3.14 or a newer LTS kernel as baseline. Have fun! The OpenWrt developer team _______________________________________________ openwrt-devel mailing list openwrt-devel(a)lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -----------------------------------------

10 years, 7 months

1
0
0 0

dhcp static leases

by Luca Postregna

Hi, is there a way to configure dhcp static leases in libre-mesh firmware? Which is the right dnsmasq setup? Thanks LP -- luca.postregna.name twitter.com/lucapost

10 years, 7 months

3
3
0 0

Using 11s as link layer instead of adhoc

by Pau

Hi. As some of you already know, the last days I have been testing the possibility of use 802.11s as link layer instead of adhoc. By default 11s comes with a kind of layer2 routing (same as bat-adv does) by using HWMP (hybrid wireless mesh protocol) which in general is quite shitty compared to other well known solutions. However, if the option mesh_fwding is set to 0, this l2 routing layer is disabled and 11s can be used just as layer1 protocol in the same level of Ad-Hoc or AP/Infrastructure. From OpenWRt these are the needed options to enable 11s as link layer: uci set wireless.mesh0.mode=mesh uci set wireless.mesh0.mesh_id=wibed uci set wireless.mesh0.mesh_fwding=0 Using 11s instead of adhoc for deploying our mesh networks can bring some interesting features, among others: 1. Better support for 11n 2. Better compatibility with drivers (probably even ath_htc works fine) 3. You can bridge it to another interface if necessary. 4. It does NOT try to synchronize the TSF counter of your wifi card thus you can create up to 8 11s VAP mixed with adhoc, AP, client, etc... 5. I don't know deeply 11s but it probably has better design for deploying mesh networks I've been testing it in a 12 nodes mesh network mixing it with bmx6 and it worked as a charm. No more "strange" problems coming from the adhoc layer. Yesterday Gio the great added support for 11s in libre-mesh [1]. So now we only need to test it a bit more with our already crazy network architecture, so it may became even a bit more crazy for traditional mesh folks (bmx6+bat-adv+11s, never done something like that!). Opinion? Concerns? Ideas? [1] https://github.com/libre-mesh/lime-packages/tree/feature/80211s -- ./p4u

10 years, 7 months

5
8
0 0

OpenWRT tool to align your antenna

by Pau

It is in Catalan but easy to understand for anybody. http://guifi.net/ca/node/72965 We may probably use it as-is for LiMe, what do you think? -- ./p4u

10 years, 7 months

2
1
0 0

First Steps with libre-mesh

by gabriel giovaniello

Hi, congratulations for this new tool, and your great support. I’m doing first steps with libre-mesh firmware. I flashed a WR841nd with dev binary corresponding to that router. I can connect to router through switch ports and i receive IP but when i connect through wifi, my connection is kicked. Here I send Log details of syslog in lime node web interface: Sat Sep 13 12:18:30 2014 daemon.info hostapd: wlan0_ap: STA 00:1e:c2:b7:f6:42 IEEE 802.11: disassociated Sat Sep 13 12:18:31 2014 daemon.info hostapd: wlan0_ap: STA 00:1e:c2:b7:f6:42 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) Also i receive a list of: kern.warn kernel: [ 1479.000000] br-lan: received packet on bat0 with own address as source address I tried to keep pinging interface but i’m kicked, i tried from 2 different notebooks and my cellphone and no luck. My ip is assigned and seconds later wifi disconnects. I tried also reflashing firmware and same issue. How can i proceed? Regards. Gabriel -- *Gabriel H. Giovaniello* *+54 2216230146*

10 years, 7 months

5
15
0 0

Re: [lime-dev] (sin asunto)

by Pau

@Gui, 802.11s have many parameters which can be tunned, we will probably need to understand deeply how it works and make the proper configuration. I'll ask to open 11s mailing list about this thing, that could give us some good input. @David, thank you for the document, looks quite good. I think when you disable HWMP this frame is not used thus ignored. Batman-adv adds another ethernet encapsulation which IMO should be able to coexist with 11s. On 15/09/14 07:05, Nicolás Echániz wrote: > On 09/14/2014 09:09 PM, Gui Iribarren wrote: > > On 14/09/14 20:06, Pau wrote: > >> I don't know any con yet :) But we should see about the performance of both and compare. > > > > > > veeery very promising, > > I would very much like to test/compare network performance in both modes > on a live network. It sounds promising indeed. > In particular we have had lots of trouble with highly interconnected > meshes of >50 nodes; I believe this is more of a wi-fi layer problem, > but it would be interesting to see if 11s has a positive impact in those > scenarios. > > > abrazos, > Nico > > > _______________________________________________ > Dev mailing list > Dev(a)lists.libre-mesh.org > https://lists.libre-mesh.org/mailman/listinfo/dev > -- ./p4u

10 years, 8 months

1
0
0 0

lime-altermesh deployed in DeltaLibre

by Gui Iribarren

Today is a very happy day, even though i slept only two hours in the whole weekend :P after preparing the lime release candidate these past weeks, with all the *code written by Gio*, i compiled an imagebuilder from scratch using *p4u's lime-build* ath-ib uploaded it to *altermundi's chef*, https://chef.altermundi.net/downloads/ib/r42398/ar71xx/ then prepared an image for *DeltaLibre* with that https://chef.altermundi.net/fwprofile/deltalibreorgar-r42398/ and cooked the first *LiMe-based AlterMesh* complete release flashed that to a pair of lab devices at hand, and after confirming nothing would blow out badly, i sysupgraded 8 devices in DeltaLibre's gambado river (where it all started, 3 years ago, and which was still running one of the first altermesh versions) http://libremap.net/#bbox/-34.40620151141123,-58.57924103736878,-34.4006246… everything went out reasonably smooth (i'm still counting how many hours till i bump into some nasty, ugly ath9k hang :P) well, to be honest, i spotted already in my table-lab a new ath9k issue, where 802.11n speeds are not initially negotiated in IBSS VIF, and apparently starts to work after a wifi reset or something. Didn't care to debug it much, since i wanted to focus on having LiMe-AlterMesh deployed. These 8 sysupgraded nodes are not the first ones; the are 9 "LiMe-Full" nodes in a cloud that has been running since march in angostura river http://libremap.net/#bbox/-34.419973858189636,-58.56451034545898,-34.408821… giving a current total of 17 lime-based nodes, servicing real people everyday this is the WAN port traffic at the gateway in the 9 LiMe-Full cloud http://status.red.libre.social/graphs/type=port_bits/id=216/ so, to put it in perspective: even though i haven't touched legacy AlterMesh code for months, this marks the official abandonment of that codebase, since we now have an equivalent firmware built with LiMe, as we had originally planned back in Berlin's WCW 2013 - having achieved this milestone i want to share a hurray! with you all :D coding and developing takes some time, yet coordinating efforts between different communities is incomparably harder, so this determines the project progress, which then is basically a reflection of the members' social bonds strength :) code is just code; insignificant, even ugly code, in comparison to what happened behind the scenes that originated it it's no coincidince that during these last few months, Nico, Jesi and I had the opportunity to share time together, in person so that we could smell each other (as Isaac coined once :D), as well as Gio and Pau on their side too, which also helped hold mumble meetings, or that Al & Gri recently went to Mexico, to materialize the workshops that (unknowingly to Al) we had informally imagined with Peter Bloom at the start of the year; then crossing borders to visit SudoRoom, to weave one more strand in the free networks social fabric ;) speaking of which, a few days ago surian (from Brasil!) met pau and gio... and now jow is dropping in the party as well!? you sure are having fun, so cheers to all \o/ \o/ \o/ ps: (or back to topic?) while crashtesting the release, i took the time to report two "pseudoblocker" bugs, not particular to lime; they don't affect the (clients) end-user experience, but greatly annoy admins work on ssh sessions and debugging http://article.gmane.org/gmane.network.ssh.dropbear/1573 https://lists.openwrt.org/pipermail/openwrt-devel/2014-September/027815.html [0]: lime-altermesh is basically a subset of lime-full that runs only batman-adv, i.e. without lime-proto-bmx6 and lime-proto-anygw. Thanks to Gio's work, it was trivial to create the metapackage and have a fully working firmware equivalent to the old AlterMesh.

10 years, 8 months

5
6
0 0

Re: [lime-dev] Potencial funding

by Pau

I'm not attached to any University if it is what you mean for "academic". On 15/09/14 11:53, Gioacchino Mazzurco wrote: > On Monday 15 September 2014 11:51:05 Pau wrote: > > We should apply as Organization, the dead line is the 17th so we must hurry > > up. > > > > Any volunteer to send the organization subscription? I can do it but it must > > be done today. > > I believe it is better for non academic of us to be the admins, lets see if > someother read in time > -- ./p4u

10 years, 8 months

1
0
0 0

Potencial funding

by Gioacchino Mazzurco

Hi! I just discovered this other SoC style funding [0], didn't readed much yet but it seems interesting, are we interested? [0] http://vps.semesterofcode.com/

10 years, 8 months

2
2
0 0

A new mailing list for users?

by Ilario Gelmetti

Hi! I think that we need a mailing list for users, like the openwrt-users mailing list for openwrt. Is it possible to have something like users(a)lists.libre-mesh.org ? Thanks, Ilario -- Ilario Gelmetti iochesonome(a)gmail.com ilario.gelmetti(a)sns.it

10 years, 8 months

5
9
0 0

Dash in the name of the site

by Ilario Gelmetti

Why do we have a dash "-" in the name of Libre-Mesh and in the name of the site? I suggest to register also libremesh.org (without dash) before someone else does. Bye, Ilario -- Ilario Gelmetti iochesonome(a)gmail.com ilario.gelmetti(a)sns.it

10 years, 8 months

3
4
0 0

mac address e vlan

by Ilario Gelmetti

Is this normal? 5 of these interfaces have mac address dc:9f:db:30:c1:36 1 of these interfaces has mac address de:9f:db:30:c1:36 I'm using Libre-Mesh compiled with lime-build yesterday. Ciao, Ilario 10: wlan0_adhoc: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1536 qdisc mq state UP group default qlen 1000 link/ether dc:9f:db:30:c1:36 brd ff:ff:ff:ff:ff:ff inet6 fe80::de9f:dbff:fe30:c136/64 scope link valid_lft forever preferred_lft forever 11: wlan0_adhoc-11@wlan0_adhoc: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master bat0 state UP group default link/ether dc:9f:db:30:c1:36 brd ff:ff:ff:ff:ff:ff inet6 fe80::de9f:dbff:fe30:c136/64 scope link valid_lft forever preferred_lft forever 12: wlan0_adhoc-13@wlan0_adhoc: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1398 qdisc noqueue state UP group default link/ether dc:9f:db:30:c1:36 brd ff:ff:ff:ff:ff:ff inet6 fd66:66:66:c:de9f:dbff:fe30:c136/64 scope global valid_lft forever preferred_lft forever inet6 fe80::de9f:dbff:fe30:c136/64 scope link valid_lft forever preferred_lft forever 14: wlan0_ap: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-lan state UP group default qlen 1000 link/ether de:9f:db:30:c1:36 brd ff:ff:ff:ff:ff:ff inet6 fe80::dc9f:dbff:fe30:c136/64 scope link valid_lft forever preferred_lft forever 15: wlan0_ap-11@wlan0_ap: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master bat0 state UP group default link/ether dc:9f:db:30:c1:36 brd ff:ff:ff:ff:ff:ff inet6 fe80::de9f:dbff:fe30:c136/64 scope link valid_lft forever preferred_lft forever 16: wlan0_ap-13@wlan0_ap: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1398 qdisc noqueue state UP group default link/ether dc:9f:db:30:c1:36 brd ff:ff:ff:ff:ff:ff inet6 fd66:66:66:10:de9f:dbff:fe30:c136/64 scope global valid_lft forever preferred_lft forever inet6 fe80::de9f:dbff:fe30:c136/64 scope link valid_lft forever preferred_lft forever -- Ilario Gelmetti iochesonome(a)gmail.com ilario.gelmetti(a)sns.it

10 years, 8 months

1
0
0 0

progress towards release 14.08

by Gui Iribarren

I added some debug output, (logs output to /tmp/lime-config.log on firstboot run) and most importantly basic error handling to lime-config, so that the whole script does not die if a single module has a bug. Example result: root@LiMeNode-ee01b4:/# cat /tmp/lime-config.log Configuring LiMe for first boot... Clearing wireless config... Clearing network config... Disabling odhcpd Cleaning dnsmasq Disabling 6relayd... Adding macvlan interface to uci network... Clearing bmx6 config... /usr/lib/lua/lime/network.lua:17: 2 stack traceback: /usr/lib/lua/lime/network.lua:142: in function </usr/lib/lua/lime/network.lua:142> [C]: in function 'assert' /usr/lib/lua/lime/network.lua:17: in function 'get_mac' /usr/lib/lua/lime/proto/batadv.lua:29: in function 'setup_interface' /usr/lib/lua/lime/network.lua:141: in function </usr/lib/lua/lime/network.lua:141> [C]: in function 'xpcall' /usr/lib/lua/lime/network.lua:141: in function </usr/lib/lua/lime/network.lua:110> [C]: in function 'xpcall' /usr/bin/lime-config:17: in function 'main' /usr/bin/lime-config:21: in main chunk [C]: ? /usr/lib/lua/lime/network.lua:17: 2 stack traceback: /usr/lib/lua/lime/network.lua:142: in function </usr/lib/lua/lime/network.lua:142> [C]: in function 'assert' /usr/lib/lua/lime/network.lua:17: in function 'get_mac' /usr/lib/lua/lime/proto/batadv.lua:29: in function 'setup_interface' /usr/lib/lua/lime/network.lua:141: in function </usr/lib/lua/lime/network.lua:141> [C]: in function 'xpcall' /usr/lib/lua/lime/network.lua:141: in function </usr/lib/lua/lime/network.lua:110> [C]: in function 'xpcall' /usr/bin/lime-config:17: in function 'main' /usr/bin/lime-config:21: in main chunk [C]: ? Configuring system... Let uhttpd listen on IPv4/IPv6 ###### uci changes generated by lime-config run: ###### batman-adv.bat0=mesh batman-adv.bat0.bridge_loop_avoidance=1 batman-adv.bat0.multicast_mode=0 batman-adv.bat0.distributed_arp_table=0 bmx6.general=bmx6 [...] in this particular case, the errors are due to trying to get network.get_mac from a wlan0_ap interface which doesn't exist yet on firstboot. So, this new debug possibility is already proving veeery useful :) will push this branch in a bit, after rebasing and tidying things up

10 years, 8 months

3
5
0 0

Issues with the pre-compiled images

by Max Schmit

Hi, I installed the new image from download.libre-mesh.org, for the 703n issued on 5 August. The name of the image is sounding fine, however once installed, the router seems to run a regular openwrt binary, no LiMe flavour. Seems that some things are missing or did I?

10 years, 9 months

6
17
0 0

Italian documentation

by Ilario Gelmetti

Hi! I wrote some documentation in Italian for Libre-Mesh firmware :) http://wiki.ninux.org/Libre-Mesh Bye!! Ilario -- Ilario Gelmetti iochesonome(a)gmail.com ilario.gelmetti(a)sns.it

10 years, 9 months

1
0
0 0

git repos explanation

by Gui Iribarren

This is a braindump while i'm trying to understand the whole mess of repos and feeds, in addition to lime-build and such, looking forward to having a libre-mesh release codenamed "bigbang", and the steps we need in order to do that. the objective is to have a "snapshot" of everything, so that cloning lime-build release and running make, will produce the same binary, at any future time, no matter what happens with 3rd party repos. * https://github.com/libre-mesh/lime-build.git starting point, it contains the references to all other repos. --> Make a staging branch "release/14.08" * https://github.com/libre-mesh/lime-packages.git (referenced in lime-build/feeds.conf) libre-mesh packages. --> Make a staging branch "release/14.08" then, other repos we cloned and "snapshotted": * https://github.com/libre-mesh/openwrt.git (referenced in lime-build/config.mk) base openwrt buildroot. cloned from git://git.openwrt.org/openwrt.git --> Make an immortal branch "release/14.08" * https://github.com/libre-mesh/openwrt-packages.git (referenced in lime-build/feeds.conf) maintained packages feed. cloned from git://github.com/openwrt/packages.git original repo has a branch named "for-14.07" --> Make an immortal branch "release/14.08" tracking "for-14.07" * https://github.com/libre-mesh/openwrt-oldpackages.git (referenced in lime-build/feeds.conf) old packages feed. cloned from git://git.openwrt.org/packages.git --> Make an immortal branch "release/14.08" * https://github.com/libre-mesh/openwrt-routing-packages.git (referenced in lime-build/feeds.conf) cloned from git://github.com/openwrt-routing/packages.git original repo has a branch named "for-14.07" --> Make an immortal branch "release/14.08" tracking "for-14.07" * https://github.com/libre-mesh/openwrt-luci.git (referenced in lime-build/feeds.conf) cloned from git://git.openwrt.org/project/luci.git --> Make an immortal branch "release/14.08" * https://github.com/libre-mesh/libremap-agent.git (referenced in lime-build/feeds.conf) cloned from git://github.com/libremap/libremap-agent-openwrt.git --> Make an immortal branch "release/14.08" i know this means a loooot of repos that we have to "maintain" on our own (in a way), but: * it's the only method to have something that we control completely * normally they will be just mirrors of the original repo, and pulling changes from upstream should be as easy as "git pull upstream ; git push github-lime" not all of those repos were mirrored, and currently lime-build is pointing at the original (upstream) repos. I'll fix that in a minute. also, i changed the "default" branch of lime-packages to *develop*, to make development progress more visible. so now if you git clone lime-packages, you'll get bleeding edge code, unless you checkout "stable" branch (i.e. what was previously called master) or some particular release while this deviates just a little bit from nvie "gitflow" branching model, i think it is aligned with what people expect when looking at a github repo.

10 years, 9 months

3
2
0 0

OpenWrt packages in lime-build

by Pau

Hello. I've updated the git repository for the openwrt packages snapshot in lime-build. Merge was very problematic because OpenWRT developers are splitting the repositories, so I had to remove, create and mirror it again. Unfortunately, this new repository is not compatible with the old, so if you are using lime-build you should do: cd lime-build git pull rm -rf build/trunk-packages rm .checkout_owrt_pkg make update_all The packages feed was completely broken, so it is recommended to rebuild again. Cheers. -- ./p4u

10 years, 9 months

1
0
0 0

downloads.libre-mesh.org

by Pau

Hi. Yesterday I set up a server with generic pre-compiled images for LibreMesh. Find it here: http://downloads.libre-mesh.org/ ToDo: Set up the nightly compile, so we will have fresh compiled images every night if there is some change in the code -- ./p4u

10 years, 9 months

2
5
0 0

1043nd - no dhcp

by Max Schmit

Hi everyone, I’ve some problems to set up the 1043nd using the pre-compiled images of pau. For the two 703n, they are working out of the box. I’m not able to get a ip address over ethernet, also joining the lime SSID is buggy (shortly after obtaining an IP address, mac os is reporting that there are some issues, well could be also a strange osx behaviour…). I managed to get a access to web gui over wifi. The mesh is working. I tried to compare the different configs (703n and 1043nd). They are more or less the same. As Pau recalled me, often the switch section is difficult to get working. So: WAN got an ip address from my local network an Port 2 (connected to my computer) is for vlan id 1 : untagged / vlan 2 id 2 : off. I’ve no idea what’s wrong, my technical background for this is limited. Btw, currently I’m working on my bachelor thesis (UAV communications) and so libremesh fits perfect for my use. Thank you, max On Aug 1, 2014, at 2:00 PM, dev-request(a)lists.libre-mesh.org wrote: > 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. downloads.libre-mesh.org (Pau) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 01 Aug 2014 13:45:00 +0200 > From: Pau <pau(a)dabax.net> > To: libre-mesh <dev(a)lists.libre-mesh.org> > Subject: [lime-dev] downloads.libre-mesh.org > Message-ID: <53DB7DBC.2090102(a)dabax.net> > Content-Type: text/plain; charset="iso-8859-1" > > Hi. > Yesterday I set up a server with generic pre-compiled images for > LibreMesh. Find it here: http://downloads.libre-mesh.org/ > > ToDo: Set up the nightly compile, so we will have fresh compiled images > every night if there is some change in the code > -- > ./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/20140801/d36a0d3d/att…> > > ------------------------------ > > _______________________________________________ > Dev mailing list > Dev(a)lists.libre-mesh.org > https://lists.libre-mesh.org/mailman/listinfo/dev > > > Fin de Resumen de Dev, Vol 16, Envío 1 > **************************************

10 years, 9 months

2
2
0 0

tip4commit, we already have something in the basket!

by Pau

Hey, we got some BTC in our basket! Cool :) http://tip4commit.com/github/libre-mesh/lime-packages The current tip-for-commit is 0.00019800 (~0.12$), but for getting this amount you need to sign-in with your github account here http://tip4commit.com/users/sign_in and put your BTC address (you can go to http://blockchain.info to get one or use electrum as wallet). Thanks to the donor! -- ./p4u

10 years, 10 months

1
0
0 0

small news / updates on branch develop

by Gui Iribarren

so i finally spent a couple of days and resumed working on libre-mesh :D * first task was to make an "altermesh-system" that would include only batman-adv, but no bmx6 or anygw magic. This would not be retrocompatible with legacy altermesh, since batman versions are incompatible (2012.4.0 vs 2014.2.0) but the setup and functionality should be similar. Thanks to the impressive modularization work made by gioacchino all these past months, it was unexpectedly simple as compiling an image with lime-system, lime-proto-batadv, and that was it, mostly everything worked out of the box :D (i didn't even needed to create a metapackage to test) So, it is all very very promising! I estimate this week we can have with nico an "altermesh" cloud running live, but based completely on libre-mesh codebase. instead of going ahead and creating the altermesh-system metapackage, i went back and refactored a little bit of code to tidy things up, addressing some bad/unexpected details i have been seeing in lime-system these past months, but didn't have time to fix yet a quick summary: * /etc/resolv.conf was overwritten, which kinda break the normal resolution system (it should only contain 127.0.0.1, and dnsmasq reads /tmp/resolv.conf.auto to find out about upstream servers) now lime-defaults.network.resolvers are copied to dhcp.(a)dnsmasq[0].server and everything works as expected again * /etc/uci-defaults/95-lime-init-enable failed with 1 on boot the whole lime-init unique-in-its-kind hack was split into scripts placed at the "expected" places: /etc/firewall.user.d/* for iptables or ebtables stuff, /etc/rc.local.d/* for other hacky stuff. * iptables -t nat -A POSTROUTING -o $wan -j MASQUERADE needed to be manually added on gateways. Now the stock firewall system is back in place, we have the MASQUERADE rule for free. * dnsmasq-2.66-5 had a hardcoding bug on the dns lifetime announced in RAs, which triggered clients disconnect and reconnect every 20 mins (very annoying) openwrt-BB-rc1 ships with dnsmasq-2.71-3, a version where the bug is fixed (dns lifetime is now equal to router lifetime) * reworked dnsmasq-lease-share to use a different approach, instead of maintaining the leases database, and restarting every 5 minutes (yuck!) it writes a dhcp-hostsfile, which dnsmasq can re-read without a full restart. * found out another shortcoming of the anygw black magic and dnsmasq white magic: the ra-names feature doesn't work at all in lime-full, since the icmpv6 packet dnsmasq uses to SLAAC-CONFIRM hosts, goes out through anygw but comes back through br-lan, and dnsmasq misses it. So, there's no AAAA resolution at all in lime-full :( we encountered a similar issue with dhcpv4 but worked around it with dhcp-needs-broadcast. At some point, we should bump the thread at dnsmasq-discuss and look for a proper solution. * the dhcp-hostsfile approach vs leasefile-ro approach: dhcp-hostsfile has the benefit of not having to do a full restart, but on the other hand ra-names is not tried at all. Given the previous item / bug, (ra-names is not working anyway), it's better to stay with dhcp-hostsfile approach, and avoid dnsmasq restarts. will continue working tomorrow, but wanted to send huge kudos to gio for all the work done so far, a heads-up to the rest of the team, and that i'm back in business :D cheers!! gui

10 years, 10 months

1
0
0 0

tip4commit

by Pau

Hi. I've add libre-mesh packages repository to tip4commit. http://tip4commit.com/projects/804 Maybe we might put the link (or any other thing available in the project page) to the main web page. So people can make donations using BitCoin. -- ./p4u

10 years, 11 months

2
4
0 0

AirOS site survey can't see LiMe

by Ilario Gelmetti

Hi all! I was trying to use a Ubiquiti NanoStation M5 with firmware stock (AirOS) as a client for a Ubiquiti NSM5 running Libre-Mesh, but when I do a site survey on AirOS I notice strange things: if the country code is Italy no LiMe network is displayed [1]; if the country code is Uzbekistan I can see the LiMe network [2]. I put the LiMe network on a channel (40, 5.2GHz) allowed in Italy, so it should be visible (if you notice, in [1] you can see that 5.2GHz is in the list of frequencies scanned by AirOS). For reference I added another NSM5 running OpenWrt in ap mode. Do you have any idea of why this happens? Thanks, Ilario [1] https://imgur.com/S8etw0y,snjFc9w#0 [2] https://imgur.com/S8etw0y,snjFc9w#1 -- Ilario Gelmetti iochesonome(a)gmail.com ilario.gelmetti(a)sns.it

10 years, 11 months

2
3
0 0

802.1ad gsoc initial work merged in openwrt

by Gioacchino Mazzurco

nbd r41112 trunk/package/network/config/netifd/Makefile netifd: update to latest version, fixes reload issue (#16754) and adds 802.1ad support

10 years, 11 months

1
1
0 0

libre-mesh.org down

by Gioacchino Mazzurco

As in subject :( We should have a replicated server as soon as possible...

10 years, 11 months

3
2
0 0

Libre-mesh on events

by al

Hey people, some Libre-mesh presence on this events? I think if Libre-mesh wants to be "The Meta-Firmware for Community Mesh Networks" has the obligation to be there: * Wireless Battle of the Mesh v7 in Leipzig (Germany) - May 12-18 http://battlemesh.org/BattleMeshV7 * Salut, Amor i Xarxa (SAX) in Morella (Països Catalans) - June 7-8 https://sites.google.com/site/sax2014morella/home (yeah, incredible: in google sites!) * Backbone 409 in Calafou (Països Catalans) - June 14-15 http://backbone409.calafou.org/

10 years, 11 months

2
3
0 0

Lost password form on the site

by Ilario Gelmetti

Hi all! I'm Ilario from NinuxVerona (Italy), in NinuxVerona we use Libre-Mesh but up to now we have only one wireless link (UbiquitiPicoStationM2-wire-switch-wire-UbiquitiNanoStationM5-wireless-UbiquitiNanoStationM5). I registered on the libre-mesh site but the confirmation email never arrived, now the "lost password" page says "An email with instructions to choose a new password has been sent to you." but I can't see any email. Is it possible to become an editor of the libre-mesh site? Thanks, Ilario Gelmetti -- Ilario Gelmetti iochesonome(a)gmail.com ilario.gelmetti(a)sns.it

10 years, 11 months

2
2
0 0

Ipv4 editing

by Gioacchino Mazzurco

I have seen this commit from guii, does it permit editing ipv4 in /etc/config/lime or does it edit /etc/config/network ? https://github.com/libre-mesh/lime-packages/commit/9aa4fcceade64db4abafba31…

10 years, 11 months

3
2
0 0

I have installed the firmware. Now what? =)

by Ramiro Polla

Hi, I have compiled the firmware using lime-build for tl-mr3020, and then installed the firmware on two routers. The mesh works, they can see each other and I can connect to them as Access Points. Now I have two questions: 1. How do I connect a router to the Internet? 2. How do I share this connection with the mesh? For (1), I tried scanning for wifi networks but I got an error that libiwinfo-lua was missing. I connected to a network through ssh using wpa_supplicant and installed libiwinfo-lua, so now I can properly connect from the web interface. It seems libiwinfo-lua should be installed by default, shouldn't it? For (2), I'm not quite sure how to proceed. Ramiro

10 years, 12 months

5
15
0 0

Issue: asymmetric bmx6 tunnels break PMTUD

by Gui Iribarren

Hey axel! so, we've scratching our heads today, facing some MTU issues on our shiny new libre-mesh network, and after a few hours debugging, tcpdumping and discussing, we came to these conclusions: * the invented src-addr in the bmxOut tunnel makes it impossible for hops along the path to return "Packet Too Big" to the originating node. So, if a particular link has a smaller MTU than the first link (say, a VPN is involved), the packet will be silently dropped. A==1500==B---1400---C===1500===D A wants to send a packet to a network announced by D; so it creates a tunnel with D as destination, and a "D-derived" fake address as src, that matches the bmxIn "catchall" tunnel peer-addr in D Then sends a 1460 + 40 = 1500 bytes packet through that tunnel, B cannot push that packet to C, then tries to send back a ICMPv6 PTB... but the src-addr it finds in the encapsulation is not A, but instead the "D-derived" fake addr. Then, the ICMPv6 PTB is lost and A can never find out about the smaller MTU. This fundamentally breaks PMTUD which is a bad idea in IPv6 to avoid this there are 3 options: * set mtu=1280 on every bmxOut tunnel (yuck! :( ) * probe before establishing each tunnel, with the real src-addr so that PMTUD can happen correctly, until it reaches the desired endpoint node. Then, use discovered PMTU for new tunnel. (*downside*: this will only work as long as path doesn't change to pass through some thinner link. In that case, PMTU will not be rediscovered, and packets will be dropped again.) * use the current bmxIn "catchall" tunnels only for sending special bmx6 control packets, that ask for a symmetric tunnel. i.e. 1) A sends to D (2001:db8::D) a packet (encapsulated with a fake src-addr, to be catched by the catchall @ D) with content "I'm A and this is my real address 2001:db8::A; please make a dedicated tunnel for me" 2) D gets that packet and creates a tunnel with "peer 2001:db8::A", then sends back an ACK to A, again using "A-derived" fake-addr as src 3) A gets the ACK and creates the tunnel with "peer 2001:db8::D" *** now both ends have a symmetric tunnel between them, with real src and dest address *** 4) A finally sends the real payload through the symmetric tunnel, this payload (may be bigger than 1280, say... 1450) will be encapsulated with the real src-addr of A, so if any node in the path needs to send back a Packet-too-big, will be able to, and PMTUD will happen correctly. (at the cost of a full RTT latency before the first payload packet, but with a reasonable tunnel expire time as it has currently, that shouldn't be terrible) back in April, i remember we discussed the idea of symmetric tunnels, and you brought up this "control connection" idea which i'm simply redescribing here. But that discussion was in another context, more like a 'feature', and finally didn't really solve the idea we had originally, yet, this PMTUD issue was not taken into account AFAIR, so the "symmetric tunnel" idea now becomes more like a bugfix (i.e. don't create PMTUD blackholes) what do you think? Cheers!! gui

11 years

3
6
0 0

Re: [lime-dev] [freifunk-gsoc-students] Post for GSoC 2014 blog (Hardware Detection)

by Francisco Jiménez González

Hi, I have already published it on the blog: http://blog.freifunk.net/2014/hardware-detection-libremesh-gsoc-2014 I have selected Software as kategorien, Is it correct? let's me know if something is wrong so I will change it thank you!! ;) 2014-05-09 14:04 GMT+02:00 Mario Behling <mariobehling(a)gmail.com>: > Hi, > Please let us know when your posts are in the final version and if you > want to publish it yourself on the blog or we should do it. > Thanks > M. > On May 8, 2014 2:44 PM, "Andreas Bräu" <ab(a)andi95.de> wrote: > >> Hi Francisco, >> >> if you plan to publish your blog post at http://blog.freifunk.net I >> could create an account for you. >> >> Best, >> >> Andi >> >> Am Mittwoch, den 07.05.2014, 22:02 +0200 schrieb Francisco Jiménez >> González: >> > Hi everyone! >> > >> > >> > I have written the post for the Freifunk's blog here: >> > >> > http://pad.eigenlab.org/p/QPRE5WCuW0 >> > >> > >> > Feel free to contribute on it by changing, adding or removing things >> > >> > >> > Thank you and regards, >> > >> > Francisco >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "Freifunk GSoC Students" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an email to freifunk-gsoc+unsubscribe(a)googlegroups.com. >> > For more options, visit https://groups.google.com/d/optout. >> >>

11 years

1
0
0 0

Post for GSoC 2014 blog (Hardware Detection)

by Francisco Jiménez González

Hi everyone! I have written the post for the Freifunk's blog here: http://pad.eigenlab.org/p/QPRE5WCuW0 Feel free to contribute on it by changing, adding or removing things Thank you and regards, Francisco

11 years

4
3
0 0

Working on Libre-mesh HowTo for Guifi.net workers

by al

Hi from Garraf (Barcelona). Here we are with Gioacchino installing Libre-mesh nodes around and we are going to train a local group to lead Libre-mesh. People here use, understand and install guifi.net infraestructure nodes (RouterOS, AirOS, AP-WDS and BGP in both 5GHz and 2.4GHz), and they don't know more. So I just start to write a Libre-mesh HowTo oriented to this kind of base knowledge. I'm writing it in spanish and later I'm going to translate it to english and catalan. It's going to become a first approach to concepts like OpenWRT, ad-hoc, BMX6 and BATMAN-adv (without miths) for Guifi.net people. It is based on questions and answers, so, if you want to help, you can write some questions or try to write some answer. I'm doing it ehterpad here: http://pad.marsupi.org/manual-de-libre-mesh-para-guiferos

11 years

2
3
0 0

Post for the GSoC 2014 blog

by Gioacchino Mazzurco

I have written the post for the GSoC 2014 on a pad http://pad.eigenlab.org/p/gsoc2014_blog_post1 As politics often permeate what I say I ask yours reviews to see if something should be said in a more "politically correct" way before publication Moreover I am not a native english speaker so correction are welcome too :) If you choose to edit the pad please choose a color with good contrast in repect to the one i choosed so i can spot esly differences Thanks everyone :)

11 years

2
1
0 0

L2 netsplit

by Tim Niemeyer

Hi I heard an presentation last year in berlin about libre mesh. I was amazed about the idea to use clounds and a l3 routing protocol. I talked a bit later with Pau about a netsplit problem where one cloud is split up. Then alfred isn't synchonizing, so that the dhcp can't know wich ip is already in use. Is the problem resolved or further discussed? Tim (Freifunk Franken)

11 years, 1 month

7
15
0 0

libre-mesh.org uses vulnerable openSsl

by Axel Neumann

The Heartbleed bug allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users and the actual content. This allows attackers to eavesdrop on communications, steal data directly from the services and users and to impersonate services and users. http://filippo.io/Heartbleed/#libre-mesh.org /axel PS: lists.libre-mesh.org seems ok

11 years, 1 month

2
1
0 0

libre-mesh server uses vulnerable openssl

by Axel Neumann

http://filippo.io/Heartbleed/#libre-mesh.org The Heartbleed bug allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users and the actual content. This allows attackers to eavesdrop on communications, steal data directly from the services and users and to impersonate services and users. /axel PS: lists.libre-mesh.org seems ok

11 years, 1 month

1
0
0 0

LiMe in the BattleMesh

by Pau

Hi Lime Folks. Who is going to the BattleMesh? It would be nice to make a talk about libremesh, the basics and the current status. I would be part of the team presenting, but it would be nice to have someone else with me. Volunteers? -- ./p4u

11 years, 1 month

2
2
0 0

Lime-build doesn't build lime-packages

by Ilario GELMETTI

Hi all! Following the instructions [1] on your site I obtain a clean OpenWrt image, no LiMe packages inside, no bmx6, no batctl on the flashed antenna. I noticed the presence of a broken link: ls -l lime-build/ lrwxrwxrwx 1 ilario ilario 25 mar 15 15:00 files -> build/lime-packages/files maybe this is the cause? Running an old stile compilation worked [2]. [1] git clone https://github.com/libre-mesh/lime-build.git cd lime-build make T=ar71xx J=4 [2] cd lime-build/build/trunk ./scripts/feeds update -a ./scripts/feeds install -a make menuconfig (and select LiMe packages) make

11 years, 1 month

3
6
0 0

Server down

by Gioacchino Mazzurco

[21:03:30] <g10h4ck> guii nicoechaniz how are you ? [21:03:46] <g10h4ck> did you find the piece for server mounting ? [21:06:16] <guii> nope :( it's carnival/holidays until wednesday [21:06:31] <guii> ah, wait [21:06:39] <guii> i think you didn't get the news: [21:06:55] <guii> the server PSU / motherboard / CPU died

11 years, 1 month

6
7
0 0

Re: [lime-dev] libremap-agent pacchetto non c'�

by Gioacchino Mazzurco

You need to add this feed too to have libremap-agent src-git libremap https://github.com/libremap/libremap-agent-openwrt.git On Thursday 03 April 2014 13:14:33 you wrote: > ilario@ilario-fisso:~/software/lime-build-bis/build/trunk$ ./scripts/feeds > install -a Installing all packages from feed packages. > Installing all packages from feed lime_packages. > Installing package 'lime-map-agent' > WARNING: No feed for package 'libremap-agent' found, maybe it's already part > of the standard packages? WARNING: No feed for package > 'luci-lib-libremap-location' found, maybe it's already part of the standard > packages? WARNING: No feed for package 'luci-lib-libremap-system' found, > maybe it's already part of the standard packages? Installing all packages > from feed luci. > Installing all packages from feed routing.

11 years, 1 month

1
0
0 0

LibreMap status

by Gioacchino Mazzurco

Hi! I am thinking on moving libremesh firmware from altermap-agent to libremap- agent what is the current status? Can someone update http://www.libre-mesh.org/issues/6 ?

11 years, 1 month

1
0
0 0

Probable VLAN fix

by Gioacchino Mazzurco

Hi all! Talking with some german guys they were having fun on me, because i said tagged vlan are not working on wdrXXXX switch it seems we are just ignorant and we are missing some knowld on how switch works on openwrt they said to me that they tried on wdr3600 and it works fine and pointed to me to this page http://freifunk.in-kiel.de/wiki/Konfiguration/Eigenes_WLAN I do not have tp-link with me but i'll implement that as soon as possible and hope someone with tp-link in hand can help me testing

11 years, 1 month

2
2
0 0

Re: [lime-dev] br-lan: received packet on bat0 with own address as source address

by Gioacchino Mazzurco

Pushed workaround on dev branch more details at http://www.libre-mesh.org/issues/32

11 years, 1 month

1
0
0 0

br-lan: received packet on bat0 with own address as source address

by Ilario GELMETTI

Hi all, I have two devices (Ubiquiti PicoStation M2 and Ubiquiti NanoStation M5) in a very simple configuration: both attached to a Mikrotik RB250GS gigabit switch (latest 1.11 firmware) and both running the latest libre-mesh firmware. >From dmesg of the two devices I can see some error form batman loop avoidance: br-lan: received packet on bat0 with own address as source address Do you think that could be a libre-mesh related problem? This is from the PicoStation [...] [ 15.520000] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 15.520000] device eth0 entered promiscuous mode [ 15.540000] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready [ 15.640000] device br-lan entered promiscuous mode [ 15.640000] IPv6: ADDRCONF(NETDEV_UP): anygw: link is not ready [ 15.690000] IPv6: ADDRCONF(NETDEV_UP): eth0.11: link is not ready [ 15.840000] IPv6: ADDRCONF(NETDEV_UP): eth0.12: link is not ready [ 16.060000] batman_adv: bat0: Adding interface: eth0.11 [ 16.060000] batman_adv: bat0: The MTU of interface eth0.11 is too small (1496) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1532 would solve the problem. [ 16.090000] batman_adv: bat0: Interface activated: eth0.11 [ 16.100000] 8021q: adding VLAN 0 to HW filter on device bat0 [ 16.100000] device bat0 entered promiscuous mode [ 16.110000] br-lan: port 2(baINBOXt0) entered forwarding state [ 16.110000] br-lan: port 2(bat0) entered forwarding state [ 16.220000] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready [ 16.220000] IPv6: ADDRCONF(NETDEV_CHANGE): anygw: link becomes ready [ 16.240000] br-lan: received packet on bat0 with own address as source address [ 16.410000] eth0: link up (100Mbps/Full duplex) [ 16.410000] br-lan: port 1(eth0) entered forwarding state [ 16.420000] br-lan: port 1(eth0) entered forwarding state [ 16.420000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 16.440000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.11: link becomes ready [ 16.480000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.12: link becomes ready [ 17.340000] batman_adv: bat0: bridge_loop_avoidance: Changing from: disabled to: enabled [ 17.370000] batman_adv: bat0: distributed_arp_table: Changing from: enabled to: disabled [ 18.110000] br-lan: port 2(bat0) entered forwarding state [ 18.420000] br-lan: port 1(eth0) entered forwarding state [ 20.350000] IPv6: ADDRCONF(NETDEV_UP): wlan0_ap: link is not ready [ 20.370000] IPv6: ADDRCONF(NETDEV_UP): wlan0_ap.12: link is not ready [ 23.510000] device wlan0_ap entered promiscuous mode [ 23.530000] IPv6: ADDRCONF(NETDEV_UP): wlan0_ap.12: link is not ready [ 23.540000] IPv6: ADDRCONF(NETDEV_UP): wlan0_ap: link is not ready [ 23.560000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0_ap: link becomes ready [ 23.560000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0_ap.12: link becomes ready [ 23.580000] br-lan: port 3(wlan0_ap) entered forwarding state [ 23.580000] br-lan: port 3(wlan0_ap) entered forwarding state [ 25.580000] br-lan: port 3(wlan0_ap) entered forwarding state [ 26.040000] br-lan: received packet on bat0 with own address as source address [ 27.090000] IPv6: ADDRCONF(NETDEV_UP): wlan0_adhoc: link is not ready [ 27.110000] wlan0_adhoc: Created IBSS using preconfigured BSSID ca:fe:00:c0:ff:ee [ 27.110000] wlan0_adhoc: Creating new IBSS network, BSSID ca:fe:00:c0:ff:ee [ 27.120000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0_adhoc: link becomes ready [ 36.060000] br-lan: received packet on bat0 with own address as source address [ 46.080000] br-lan: received packet on bat0 with own address as source address [ 56.100000] br-lan: received packet on bat0 with own address as source address [ 66.120000] br-lan: received packet on bat0 with own address as source address [...] batctl s tx: 12 tx_bytes: 1264 tx_dropped: 43 rx: 20 rx_bytes: 948 forward: 0 forward_bytes: 0 mgmt_tx: 365 mgmt_tx_bytes: 23182 mgmt_rx: 362 mgmt_rx_bytes: 22912 frag_tx: 0 frag_tx_bytes: 0 frag_rx: 0 frag_rx_bytes: 0 frag_fwd: 0 frag_fwd_bytes: 0 tt_request_tx: 1 tt_request_rx: 2 tt_response_tx: 2 tt_response_rx: 1 tt_roam_adv_tx: 0 tt_roam_adv_rx: 0 dat_get_tx: 0 dat_get_rx: 0 dat_put_tx: 0 dat_put_rx: 0 dat_cached_reply_tx: 0 and this is from NanoStation: [...] [ 17.460000] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 17.460000] device eth0 entered promiscuous mode [ 17.480000] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready [ 17.520000] device br-lan entered promiscuous mode [ 17.520000] IPv6: ADDRCONF(NETDEV_UP): anygw: link is not ready [ 17.550000] eth0: link up (100Mbps/Full duplex) [ 17.550000] br-lan: port 1(eth0) entered forwarding state [ 17.560000] br-lan: port 1(eth0) entered forwarding state [ 17.560000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 18.610000] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [ 18.610000] device eth1 entered promiscuous mode [ 18.620000] br-lan: port 2(eth1) entered forwarding state [ 18.620000] br-lan: port 2(eth1) entered forwarding state [ 18.630000] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready [ 18.660000] br-lan: port 2(eth1) entered disabled state [ 18.740000] IPv6: ADDRCONF(NETDEV_UP): eth1.11: link is not ready [ 18.750000] IPv6: ADDRCONF(NETDEV_CHANGE): anygw: link becomes ready [ 18.800000] IPv6: ADDRCONF(NETDEV_UP): eth1.12: link is not ready [ 19.120000] batman_adv: bat0: Adding interface: eth0.11 [ 19.130000] batman_adv: bat0: The MTU of interface eth0.11 is too small (1496) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1532 would solve the problem. [ 19.150000] batman_adv: bat0: Interface activated: eth0.11 [ 19.160000] 8021q: adding VLAN 0 to HW filter on device bat0 [ 19.210000] device bat0 entered promiscuous mode [ 19.210000] br-lan: port 3(bat0) entered forwarding state [ 19.220000] br-lan: port 3(bat0) entered forwarding state [ 19.270000] batman_adv: bat0: Adding interface: eth1.11 [ 19.270000] batman_adv: bat0: The MTU of interface eth1.11 is too small (1496) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1532 would solve the problem. [ 19.300000] batman_adv: bat0: Interface activated: eth1.11 [ 19.560000] br-lan: port 1(eth0) entered forwarding state [ 20.810000] batman_adv: bat0: bridge_loop_avoidance: Changing from: disabled to: enabled [ 20.810000] batman_adv: bat0: distributed_arp_table: Changing from: enabled to: disabled [ 21.220000] br-lan: port 3(bat0) entered forwarding state [ 22.650000] IPv6: ADDRCONF(NETDEV_UP): wlan0_ap: link is not ready [ 22.680000] IPv6: ADDRCONF(NETDEV_UP): wlan0_ap.12: link is not ready [ 27.590000] device wlan0_ap entered promiscuous mode [ 27.620000] IPv6: ADDRCONF(NETDEV_UP): wlan0_ap.12: link is not ready [ 27.630000] IPv6: ADDRCONF(NETDEV_UP): wlan0_ap: link is not ready [ 27.650000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0_ap: link becomes ready [ 27.650000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0_ap.12: link becomes ready [ 27.670000] br-lan: port 4(wlan0_ap) entered forwarding state [ 27.670000] br-lan: port 4(wlan0_ap) entered forwarding state [ 29.140000] br-lan: received packet on bat0 with own address as source address [ 29.670000] br-lan: port 4(wlan0_ap) entered forwarding state [ 31.750000] IPv6: ADDRCONF(NETDEV_UP): wlan0_adhoc: link is not ready [ 31.770000] wlan0_adhoc: Created IBSS using preconfigured BSSID ca:fe:00:c0:ff:ee [ 31.780000] wlan0_adhoc: Creating new IBSS network, BSSID ca:fe:00:c0:ff:ee [ 31.790000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0_adhoc: link becomes ready [ 39.160000] br-lan: received packet on bat0 with own address as source address [ 49.180000] br-lan: received packet on bat0 with own address as source address [ 59.200000] br-lan: received packet on bat0 with own address as source address [ 69.220000] br-lan: received packet on bat0 with own address as source address [...] batctl s tx: 10 tx_bytes: 1096 tx_dropped: 41 rx: 18 rx_bytes: 756 forward: 0 forward_bytes: 0 mgmt_tx: 879 mgmt_tx_bytes: 51202 mgmt_rx: 352 mgmt_rx_bytes: 22292 frag_tx: 0 frag_tx_bytes: 0 frag_rx: 0 frag_rx_bytes: 0 frag_fwd: 0 frag_fwd_bytes: 0 tt_request_tx: 4 tt_request_rx: 1 tt_response_tx: 1 tt_response_rx: 2 tt_roam_adv_tx: 0 tt_roam_adv_rx: 0 dat_get_tx: 0 dat_get_rx: 0 dat_put_tx: 0 dat_put_rx: 0 dat_cached_reply_tx: 0 This problem isn't related to interaction between two devices, because also isolating a device via switch web interface, the other one after rebooting shows the same error again. Again, I don't know if this is a libre-mesh related problem or a problem of batman loop avoidance. Maybe the problem is related to this old closed bug? http://www.open-mesh.org/issues/170 Thanks, Ilario

11 years, 1 month

5
12
0 0

google SoC news

by Nicolás Echániz

Hi guys, I received an e-mail confirmation that I'm a mentor for this year's SoC. Have you received any e-mails? cheers, Nico

11 years, 1 month

3
5
0 0

subversion is a dependency for compilation?

by Ilario GELMETTI

Hi all, on the Libre-Mesh site I can read: You need to install dependencies: (i.e. in Debian 7.0 or higger) apt-get install git build-essential libncurses5-dev zlib1g-dev gawk after installing those packages and trying to compile I get Checking 'non-root'... ok. Build dependency: Please install the subversion client. Prerequisite check failed. Use FORCE=1 to override. make[1]: *** [tmp/.prereq-build] Error 1 make[1]: Leaving directory `/home/ilario/software/lime-build/build/trunk' make: *** [checkout] Error 2 So subversion also is needed? Bye, Ilario

11 years, 2 months

2
1
0 0

bmx6 debugging

by Gioacchino Mazzurco

Hi! On one node we are announcing a tunIn for internet and anotherone that have a corresponding tunOut is tring to reach internet, but there is some problem, packets never reach the other nodes and sniffing on interfaces never goes out from the originating node, and on dmesg i have found some of this messages [ 8829.860000] ip6_tunnel: bmxOut_9f4872: Path to destination invalid or inactive! That seems related ecause appears only on the node that is trying to go out, is it a well known problem or it is necessary a deeper debug ?

11 years, 2 months

3
8
0 0

Re: [lime-dev] Fwd: Re: [OpenWrt-Devel] is anybody working on supporting Linksys WRT1900ac ?

by al

Hi, people from Linksys answered me. As I sent a very informal mail they are interested to know more about (one of) our organization(s). I think they are interested concretely in which way we technically improve by software routers. I think is much better that someone of you that are working or was working in drivers code, dynamic routing daemons code or abstraction layers code (I think before Libre-mesh) send mail to them. Or write your experience and we can send it with a formal e-mail (maybe @libre-mesh.org or @qmp.cat or @bmx6.net or whatever). Here more or less quick idea of that: http://pad.marsupi.org/WRT1900ac Finally we can send e-mail to "Karen sohl" <Karen.sohl at belkin.com> ----- Mensaje original ----- > De: "al" <al(a)blogmail.cc> > Para: "libre-mesh developement" <dev(a)lists.libre-mesh.org> > Enviados: Martes, 18 de Febrero 2014 15:07:32 > Asunto: Re: [lime-dev] Fwd: Re: [OpenWrt-Devel] is anybody working on supporting Linksys WRT1900ac ? > > One month and no answer. > > I sent it again. But... maybe best forget it for now. > > I think Compex WPJ344 has more support: > http://wiki.openwrt.org/toh/compex/wpj344 > https://wikidevi.com/wiki/Compex_WPJ344_%28WPJ344LV%29 > > ----- Mensaje original ----- > > Enviados: Viernes, 17 de Enero 2014 13:06:36 > > Asunto: Re: [lime-dev] Fwd: Re: [OpenWrt-Devel] is anybody working > > on supporting Linksys WRT1900ac ? > > > > On Thursday 16 January 2014 00:42:00 al wrote: > > > I sent an email to contact in post. > > > > Great! > > >

11 years, 2 months

1
0
0 0

New Libre-Mesh Idea for GSoC 2014

by Gioacchino Mazzurco

http://wiki.freifunk.net/Ideas#Libre-Mesh:_modules_runtime_depends

11 years, 2 months

1
1
0 0

Improvement on Libre-Mesh at HackErasmus #2

by Gioacchino Mazzurco

The past week I was in Garraf at La Responsable together with Al to work on libre-mesh, here I'll do a little report of the work done: First of all my attention was dedicated to complete stabilize and merge into develop, wireless mode modularization (branch features/modes-modularization), wireless modes supported were implemented directly in wireless core file and didn't support adding of new wireless level configuration modules, so if someone would for example implement support for 802.11s ¹ in libre-mesh had to edit core wireless configuration files, while now he can just implement a mode module, writing very little number of line of code and without the risc of breaking the libre-mesh core. Then guided by testing and features requests emerged talking with Al about emerging communities needs, we decided moving on the following: First I had to change some default values that was giving trouble for example the channel 60 is DFS then radios had some difficult waking up we moved to channel 48 as default that doesn't give such troubles. Then because we had some cheap device around we tried to flash them with libre- mesh but the image was too big, so andother pass of modularization was needed, this time I have splitted protocols support in defferents packages, so for example cheap battery nodes can ship just batman-adv or just bmx6 according to user needs, also debug tools were removed form lime-system depends and splitted to lime-debug tools, so we can install them just when needed and when them fits. This new rounds of modularizations evidenced some bad abits in the code like using a global uci cursor and stuff like that, all things that were fixed before merge in develop ( more detalis on features/onadiet branch ) The new possibility of having a hybrid mesh of nodes having L2+L3 or L2 only support suggested the needs of having bmx6 take advantage also of L2 only piece of mesh so in the branch features/bmx6_over_batman the autoconfiguration module doing this was implemented and then merged into develop The rest of time was used to debug why bmx6 wasn't working as expected that resulted in the discovery that older bmx6 version are working as expected while newer manifest a bug already reported on this mailing list, plus enjoing life :) While waiting fore the dealyed aircraft i was thinking to some odd output of ps command missing dnsmasq then now i have tested and DHCPv4 is not working thanks to libre-mesh new modular nature debug of this part will be easier and hopefully done in following days! Thanks to La Responsable for ospitality and fun time together!! [¹] http://en.wikipedia.org/wiki/IEEE_802.11s

11 years, 2 months

2
1
0 0

New idea on freifunk GSoC wiki

by Gioacchino Mazzurco

http://wiki.freifunk.net/Ideas#OpenWrt_D-Link_DIR-632_support Axel do you wanna mentor some student implementing something for bmx6 ? At moment only babel have proposed ideas

11 years, 2 months

2
1
0 0

Fwd: Re: [Freifunk-Mentors] GSoC 2014 - Wanna do it?

by Gioacchino Mazzurco

---------- Forwarded Message ---------- Subject: Re: [Freifunk-Mentors] GSoC 2014 - Wanna do it? Date: Saturday 15 February 2014, 17:48:21 From: Mitar <mmitar(a)gmail.com> To: freifunk-mentors(a)googlegroups.com Hi! I added table to each of our ideas. Others, please do the same for your ideas. Mitar On Sat, Feb 15, 2014 at 5:17 PM, Mitar <mmitar(a)gmail.com> wrote: > Hi! > > So I think that TODO does not server anybody, but it just makes our > list of ideas looking less serious. > > > Mitar > > On Sat, Feb 15, 2014 at 5:14 PM, Mitar <mmitar(a)gmail.com> wrote: >> Hi! >> >> No, there is no way somebody could take shine away from nodewatcher. ;-) >> >> But last time they were checking ideas immediately after the deadline. >> So I do not see the reason to have TODO in there. They can always add >> it later, the whole section. >> >> >> Mitar >> >> On Sat, Feb 15, 2014 at 4:59 PM, Gioacchino Mazzurco >> <gmazzurco89(a)gmail.com> wrote: >>> On Saturday 15 February 2014 16:37:34 Mitar wrote: >>>> LibreMap is TODO. Can this be filled in or removed? >>> >>> Hopefully LibreMap guys will fill it soon, anyway don't think it's a problem if >>> it stay as TODO some day more, anyway i'll forward your email to remember to >>> the about the idea on the wiki ;) >>> >>> [ JOKE ] Mitar do you worry LibreMap taking some shine instead of Nodewatcher >>> ? :p [ / JOKE ] >>> >>> -- >>> You received this message because you are subscribed to the Google Groups "Freifunk Free Community Networks Mentors" group. >>> To unsubscribe from this group and stop receiving emails from it, send an email to freifunk-mentors+unsubscribe(a)googlegroups.com. >>> Visit this group at http://groups.google.com/group/freifunk-mentors. >>> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> -- >> http://mitar.tnode.com/ >> https://twitter.com/mitar_m > > > > -- > http://mitar.tnode.com/ > https://twitter.com/mitar_m -- http://mitar.tnode.com/ https://twitter.com/mitar_m -- You received this message because you are subscribed to the Google Groups "Freifunk Free Community Networks Mentors" group. To unsubscribe from this group and stop receiving emails from it, send an email to freifunk-mentors+unsubscribe(a)googlegroups.com. Visit this group at http://groups.google.com/group/freifunk-mentors. For more options, visit https://groups.google.com/groups/opt_out. -----------------------------------------

11 years, 2 months

1
0
0 0

libre-mesh.org down again

by al

root@eeprom:/home/al# ping libre-mesh.org PING libre-mesh.org (109.69.10.44) 56(84) bytes of data. ^C --- libre-mesh.org ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 4030ms root@eeprom:/home/al# ping6 libre-mesh.org PING libre-mesh.org(2a00:1508:1:f001::106) 56 data bytes >From 2a00:1508:1:f000::1 icmp_seq=1 Destination unreachable: No route >From 2a00:1508:1:f000::1 icmp_seq=2 Destination unreachable: No route

11 years, 2 months

2
3
0 0

reghack not working

by Gioacchino Mazzurco

Hi! After some tests here in Garraf we discovered that reghack is not properly working anymore... we are unable to use channel 14 in 2.4 band and we got a lot of trouble wen trying to use DFS channels on 5 band... If there is no rapid solution i belive it is the case to open a ticket ( when the server will be up again) Se you soon!

11 years, 2 months

1
0
0 0

About branching strategy

by Gioacchino Mazzurco

As we talked with Guido we are taking an article [0] as inspiration as branching strategy, here i would comment something about it [0] Says: > Feature branches typically exist in developer repos only, not in origin. I think this is not a good idea in our situation, we are a bunch of developer around the world and some time we don't know well on what the other are working, keeping those branch in origin and WELL UPDATED would help in understanding what is happening, to avoid work duplication and consequent hard to impossible to resolve merge conflict. [0] Says: > Finished features may be merged into the develop branch definitely add them > to the upcoming release: ... > $ git merge --no-ff myfeature ... > $ git branch -d myfeature > Deleted branch myfeature (was 05e9557). > $ git push origin develop > > The --no-ff flag causes the merge to always create a new commit object, even > if the merge could be performed with a fast-forward. This avoids losing > information about the historical existence of a feature branch and groups > together all commits that together added the feature. I think it is better do not delete the feature branch by default, and eventually delete just if necessary, so to keep better tracking of edit history and isolate easily eventual regressions, and i think the same about release and htofix branches, so generally i wouldn't delete branch if not necessary [0] http://nvie.com/posts/a-successful-git-branching-model/

11 years, 2 months

3
3
0 0

Fwd: Re: [Freifunk-Mentors] GSoC 2014 - Wanna do it?

by Gioacchino Mazzurco

---------- Forwarded Message ---------- Subject: Re: [Freifunk-Mentors] GSoC 2014 - Wanna do it? Date: Sunday 16 February 2014, 01:59:36 From: Gioacchino Mazzurco <gmazzurco89(a)gmail.com> To: freifunk-mentors(a)googlegroups.com On Saturday 15 February 2014 16:37:34 Mitar wrote: > LibreMap is TODO. Can this be filled in or removed? Hopefully LibreMap guys will fill it soon, anyway don't think it's a problem if it stay as TODO some day more, anyway i'll forward your email to remember to the about the idea on the wiki ;) [ JOKE ] Mitar do you worry LibreMap taking some shine instead of Nodewatcher ? :p [ / JOKE ] -----------------------------------------

11 years, 3 months

1
0
0 0

Fwd: Re: [Freifunk-Mentors] GSoC 2014 - Wanna do it?

by Gioacchino Mazzurco

---------- Forwarded Message ---------- Subject: Re: [Freifunk-Mentors] GSoC 2014 - Wanna do it? Date: Saturday 15 February 2014, 16:37:34 From: Mitar <mmitar(a)gmail.com> To: freifunk-mentors(a)googlegroups.com CC: Mario Behling <mb(a)mariobehling.de> Hi! LibreMap is TODO. Can this be filled in or removed? Mitar On Fri, Feb 14, 2014 at 8:16 AM, Juliusz Chroboczek <jch(a)pps.jussieu.fr> wrote: >> There is no actual official deadline for ideas. - The "deadline" is, >> when the Googlers look at it and think: "Wow, they really take care to >> get students into their projects. > > Ack. > > Matthieu has put up one proposal (search for Quagga), there should be > one or two others (from other people whom I've called) over the week-end. > > Thanks again, > > -- Juliusz > > -- > You received this message because you are subscribed to the Google Groups "Freifunk Free Community Networks Mentors" group. > To unsubscribe from this group and stop receiving emails from it, send an email to freifunk-mentors+unsubscribe(a)googlegroups.com. > Visit this group at http://groups.google.com/group/freifunk-mentors. > For more options, visit https://groups.google.com/groups/opt_out. -- http://mitar.tnode.com/ https://twitter.com/mitar_m -- You received this message because you are subscribed to the Google Groups "Freifunk Free Community Networks Mentors" group. To unsubscribe from this group and stop receiving emails from it, send an email to freifunk-mentors+unsubscribe(a)googlegroups.com. Visit this group at http://groups.google.com/group/freifunk-mentors. For more options, visit https://groups.google.com/groups/opt_out. -----------------------------------------

11 years, 3 months

1
0
0 0

moving server

by Nicolás Echániz

Services hosted in Buenos Aires will be offline for at least 24hs while the server literally moves from BsAs to Córdoba by train. The good news is that the new location is the National University of Córdoba datacenter so no more downtimes due to bad connectivity or power failures. cheers, Nico.

11 years, 3 months

2
1
0 0

branch develop cherry picked in lime-ng-config

by Gioacchino Mazzurco

Hi! I tryed to merge the two branch (also with rebase) but it was creating a lot of trouble, and dirty in the code so i have cherrypicked almost all commit of develop branch and various feature branches in lime-ng-config, i am testing it to the device hoping not encountering problems as the commits got picked inside another branch i would recomment to delete the develop branch and recreate it on top of master after merging of lime-ng- config in master Who have more than one device please help me with testing so we can merge and have a working firmware :)

11 years, 3 months

2
2
0 0

Re: [lime-dev] [lime-packages] Adapt luci-app-batman-adv for work with Alfred (#1)

by Gioacchino Mazzurco

Aren't we using libre-mesh.org for ticket/issue ? On Wednesday 12 February 2014 10:27:58 Pau wrote: > luci-app-batman-adv topology graph does not work with last batman-adv. The > "batcl vm" option has been removed from batman-adv and transfered to the > userspace application "Alfred". So the luci-app-batman-adv should have > alfred as dependency and the code Lua code should be adapted. > > --- > Reply to this email directly or view it on GitHub: > https://github.com/libre-mesh/lime-packages/issues/1

11 years, 3 months

1
0
0 0

GSOC 2014

by Pau

Hi. The GSOC (google summer of code) will start soon. The last years most of the Free Network Communities have been applying for funding under the umbrella of the Freifunk Community. Two years ago there were 12 accepted projects (of $5k each). The FreiFunk managers are looking for GSOC ideas before applying as an organization. So if there are good proposal they will go ahead again. I've added a Libre-Mesh proposal, but please, feel free to modify it or add more information. Also I've added a topic for Libre-Map because I think we should also try to apply in parallel for it. Please, help us to improve the ideas page: http://wiki.freifunk.net/Ideas Afterwards, we will see who is available for working on that in case the Google accepts our proposals. Cheers -- ./p4u

11 years, 3 months

2
2
0 0

Wireless Battle of the Mesh - call for talks

by Pau

Hello. This is the official call for talks and workshops of the Battlemesh v7. This event is getting more and more relevancy with the past of the years. Last WBM was partially sponsored by Intel and the University of Aalborg (Denmark). So I think it is a great opportunity to participate with any topic matching the requirements. [Battlemesh] BattleMesh v7 talk and workshop proposals now welcome! =================================================================== Do you have an idea or project related to mesh routing protocols? Are you involved in a community networking project that uses a mesh network? Are you aware of a related issue that you think should be discussed? Your workshop or presentation proposal is welcomed to BattleMeshV7 Leipzig! 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 ad-hoc networks, like Babel, B.A.T.M.A.N., BMX, OLSR,802.11s and Static Routing. 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 you might want to check this out ! The goal of the WirelessBattleMesh events 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 different WBM events, similar hardware and software configuration will be used based on the OpenWRT BoardSupportPackage and packages for each protocol implementation. The WBM events are also a great opportunity to develop testing tools for PHY/MAC radio layers (drivers,scripts and PHY analyzers). This years Battlemesh will take place from 12 - 18 May 2014 in Leipzig, Germany at the Sublab, Karl-Heine-Straße 93, 04229 Leipzig. http://battlemesh.org Format and topic of talks ------------------------- Workshops or talks relating directly to open source mesh routing protocols will be prioritised, but we welcome proposals of anything you think may be of interest to mesh routing and community networking enthusiasts. They may take any format, for example a presentation, talk, discussion, debate, practical workshop, or film showing. The suggested length for talks is one hour (40 minutes talk, 10 minutes questions and 10 minutes break/buffer). To get an idea of the kinds of talks and workshops at the previous events, see: http://battlemesh.org/BattleMeshV6/Agenda, http://battlemesh.org/BattleMeshV5/Agenda and http://battlemesh.org/BattleMeshV4/Agenda Lightening talks ---------------- Lightening talks are shorter talks which can be submitted later than the main workshops deadline, to allow everybody to have 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 before in PDF format to: submissions(a)battlemesh.org Submissions ----------- To allow an efficient handling of your proposal, please provide the following information and send them by email to the 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 length 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. Deadline -------- The deadline for proposals is the 1st of May. Contact ------- Email your proposals or specific questions to: submissions(a)battlemesh.org For general questions, please use the Battlemesh mailing list: http://ml.ninux.org/mailman/listinfo/battlemesh Please forward this message any groups or individuals who might be -- ./p4u

11 years, 3 months

1
0
0 0

Advances on modularization we discussed in Garraf

by Gioacchino Mazzurco

http://www.libre-mesh.org/issues/22#note-6

11 years, 3 months

1
0
0 0

Fwd: [GSoC Mentors Announce] Now Accepting Applications for Mentoring Organizations for GSoC 2014

by Gioacchino Mazzurco

I think we should move now if we want to participate ---------- Forwarded Message ---------- Subject: [GSoC Mentors Announce] Now Accepting Applications for Mentoring Organizations for GSoC 2014 Date: Monday 03 February 2014, 11:01:15 From: Carol Smith <carols(a)google.com> To: GSoC Mentors Announce <gsoc-mentors-announce(a)googlegroups.com> Hi all, We're pleased to announce that applications for mentoring organizations for Google Summer of Code 2014 are now being accepted [1]. If you'd like to apply to be a mentoring organization you can do so now via Melange [2]. If you have questions about how to use Melange, please see our User's Guide [3]. Please note that the application process has changed a bit from previous years: to apply you must now create your individual profile and then an organization profile before submitting your application. Please note that the application period [4] closes on 14 February at 19:00 UTC [5]. *We will not accept any late applications for any reason.* [1] - http://google-opensource.blogspot.com/2014/02/mentoring-organization-applic… [2] - http://www.google-melange.com [3] - http://en.flossmanuals.net/melange/ [4] - http://www.google-melange.com/gsoc/events/google/gsoc2014 [5] - http://goo.gl/bYYgV3 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/groups/opt_out. -----------------------------------------

11 years, 3 months

1
0
0 0

Telefonica reinventing the wheel ?

by Gioacchino Mazzurco

http://arstechnica.com/business/2014/01/bewifi-lets-you-steal-your-neighbor…

11 years, 3 months

2
1
0 0

How to update local git repo

by Ilario GELMETTI

Hi all! Some times ago I downloaded and compiled LiMe as suggested on your site: git clone https://github.com/libre-mesh/lime-build.git cd lime-build make T=ar71xx J=4 Now I would like to build an updated image, how should I update all the repositories (openwrt, libre-mesh, luci...)? Is there something like a "make update" ? Thanks 'n' bye, Ilario

11 years, 3 months

2
2
0 0

Some thoughts about libremap

by Pau

Hello. Some thoughts about my experience with libremap. 1. Routers -> Cluster should be disabled by default IMO 2. Same for filter links, since it is quite common to have "not perfect" links in a wifi community 3. Would be very useful to have more view levels. When there are some routers close you cannot see the specific position. In the other hand, Altermap allows to make quite more zoom, so this should be possible in OSM. 4. Would be nice to have a "LuCi" web plugin to manage the /etc/config/libremap agent. Is there something developed? If not I can do so. 5. I would like to create some specific plugins, for instance to send bmx6 information to the server. I see how the plugins work in the node, but I miss the web page part. Is there some "easy way" to add new plugins in the web page? Cheers! [1] http://libremap.net/#bbox/41.38757144743988,2.108720541000366,41.3898373021… -- ./p4u

11 years, 3 months

2
1
0 0

some lua libraries and useful code

by Gui Iribarren

some months ago in a sprint, we finally both sat down together with Nico to fight with lua, and at some point stumbled upon this https://github.com/rrthomas/lua-stdlib --[[ This is a collection of Lua libraries for Lua 5.1 and 5.2. You can load the standard set with require "std" ]]--- then i found out about luarocks, which is analog to ruby gems and python pips http://luarocks.org/repositories/rocks/ and from there, other interesting libraries * https://github.com/kikito/inspect.lua This function transform any Lua table into a human-readable representation of that table. The objective here is human understanding (i.e. for debugging), not serialization or compactness. (Dedicated to Nico, a python programmer horrified by lua being unable to print(table)) * https://code.google.com/p/luno/ O projeto Luno tem o objetivo de prover API's para uso com a linguagem de programação Lua que visem a facilitar a execução de tarefas corriqueiras mas que não estão diretamente implementadas pela biblioteca padrão do Lua. Luno conta com os módulos luno.string, luno.table e luno.io. Esses módulos provêem funções extras para manipular strings (trim, split, join, charAt, ...), io (getTextFromFile, ...), tabelas (imprimir tabelas, concatenar, ...). O módulo luno.util provê funções de uso geral como cópia (deep copy) e impressão (deep print) de variáveis. finally, i found the following blogpost enlightening, it's a thorough summary of differences and unexpected things, very helpful for me, dealing with lua for the first time http://notebook.kulchenko.com/programming/lua-good-different-bad-and-ugly-p… hope that helps someone,

11 years, 3 months

1
0
0 0

Copy an exact firmware from one router to other

by al

Hello, I remember first times with Freifunk firmware (OpenWrt White Russian): They put in main web page a link with a direct download of image that was working in same router. I suposse that it was generated from binaries when you click on. I think is a very good tool to make network bigger with same routers (you don't need to connect to any place to get firmware). Do you know about that? I think we can put it on libre-mesh (and also I need it now to make easy an exact copy from one of our libre-mesh routers here in Garraf).

11 years, 3 months

3
3
0 0

BattleMesh v7

by Pau

Hi. I've added a news entry in the libre-mesh page to endorse the WBMv7: http://libre-mesh.org/projects/libre-mesh/news Who is interested on going there? Do you have funding? Any idea about where can we find funding to bring some of you there? Cheers -- ./p4u

11 years, 3 months

2
1
0 0

libremap: wireless plugin?

by Pau

Hi. I've added the libre-map agent to Wibed [1] and now some nodes appear to the libremap.net web interface (in Barcelona). However the wireless plugin is not available, at least in the libremap-agent I'm using [2]. I wonder if this plugin exists and if not which are the plans to implement it. That would be a key point for wibed! So let me know if I can do something. Cheers. [1] http://wiki.confine-project/wibed:start [2] https://github.com/libremap/libremap-agent-openwrt -- ./p4u

11 years, 4 months

2
5
0 0

Fwd: Re: [OpenWrt-Devel] is anybody working on supporting Linksys WRT1900ac ?

by Gioacchino Mazzurco

Seems an interesting device, maybe we could receive someone if we ask as Libre-Mesh ? ---------- Forwarded Message ---------- Subject: Re: [OpenWrt-Devel] is anybody working on supporting Linksys WRT1900ac ? Date: Thursday 16 January 2014, 10:37:12 From: Peter Lawler <openwrt-devel(a)bleeter.id.au> To: openwrt-devel(a)lists.openwrt.org On 16/01/14 10:06, Peter Lawler wrote: > Oh, bad me for replying to myself... but from the press release page: > > http://www.linksys.com/en-us/press/releases/2014-01-06_Linksys_wrt_revoluti… > > Even worse, replying to my own reply Further down that page is commentary about OpenWRT, DDWRT etc. It also mentions they're planning to release devboards to developers. It also gives a name, email address and phone number for a contact about the product. I'm not in the same TZ as the contact, by ~15 hours. Maybe someone on this list who is a little closer could call up and ask what's what ;) Pete. _______________________________________________ openwrt-devel mailing list openwrt-devel(a)lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -----------------------------------------

11 years, 4 months

2
1
0 0

Flashing Ubiquiti Devices

by Ilario Gelmetti

Hi all! I compiled libre-mesh encountering only a small problem: subversion is needed but missing in the dependencies list. I was planning to flash libre-mesh on Ubiquiti PicoStation and Ubiquiti NanoStation. Can I safely flash using libre-mesh/images/bin/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-sysupgrade.bin and openwrt-ar71xx-generic-ubnt-nano-m-squashfs-sysupgrade.bin or some configuration is needed before compilation or after flashing? Thanks and bye, Ilario, Ninux Verona. -- Ilario Gelmetti iochesonome(a)gmail.com ilario.gelmetti(a)sns.it

11 years, 4 months

2
3
0 0

libre-mesh.org and 200.69.249.37 down

by al

Again. No SSH, no web, no ping. https://libre-mesh.org Let's do a copy for high availability. Isaac said to do it in his server. I also can do it in one of our servers. I'm sure that all of you have others servers. Now we can do a copy, but if you want to have it distributed servers we can make it available from several sharing same IP with BGP in internet. We can do a lot of things, but not let it down... is a bad image for the project.

11 years, 4 months

7
21
0 0

Nuntio Vobis Gaudium Magnum

by Gioacchino Mazzurco

Habemus Firmware! After a day of debugging with Al here in garraf and some our spent on fixing make files, and make address generation simpler and human understandable libre- mesh finally compile, you can find the images ready for testing on torvic in /home/openwrt/lime-g/bin/ See you soon P.S. We did realized after some work that there is some unmerged Guii work in the repo and also that there will be some conflict on merging, so please do the merge toghether so we can decide what to keep and what to not keep

11 years, 4 months

1
0
0 0

dnsmasq custom ipv6 mtu advertising

by Gioacchino Mazzurco

As we can read in this thread [0] dnsmasq doesn't permit to specify a custom mtu for ipv6, this is needed on out setup to avoid batman-adv level fragmentation, so the actual solution in dnsmasq doesn't work because it requires to put a lower mtu on specified interface and we cannot ( and don't want to do this ) Gui can you ask to dnsmasq developer to add this option so dnsmasq can work good also on our setup ? [0] http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2013q2/007160.html P.S. With al we have debuged some mtu iussue and committed fixes

11 years, 4 months

1
0
0 0

Problem with navigation over IPv6

by al

Hello. Navigation over IPv6 on Librenet6 doesn't work fine. Some pages on IPv6 spend a lot of time to load. Maybe problem come because computers on network get two global IPv6 from DHCP? We're temporally fix that deleting both and navigate only in IPv4 when it happens (hard to do it from a android phone, and it has some problems to connect). Our IPv6 range are not listed on Librenet6 documentation: http://docs.altermundi.net/LibreNet6/Setup Default dhcp ifconfig (my laptop): wlan0 Link encap:Ethernet HWaddr 00:1c:bf:24:f1:73 inet addr:192.168.11.16 Bcast:192.168.11.255 Mask:255.255.255.0 inet6 addr: 2a00:1508:1:f820:21c:bfff:fe24:f173/64 Scope:Global inet6 addr: fe80::21c:bfff:fe24:f173/64 Scope:Link inet6 addr: 2a00:1508:1:f820:c90f:9a43:3c24:ef8f/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:95714 errors:0 dropped:0 overruns:0 frame:0 TX packets:93125 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:36127128 (34.4 MiB) TX bytes:12318888 (11.7 MiB) Traceroute to google.com (habitually has some problems): Host Loss% Snt Last Avg Best Wrst StDev 1. 2a00:1508:1:f820::48:cf6b 0.0% 169 1.0 19.2 0.9 225.6 41.7 2. 2a00:1508:1:f000::1 0.6% 169 49.3 75.9 26.3 370.0 53.3 2a00:1508:1:f820::48:cf6b 3. 2a00:1508:1::1 1.8% 169 52.1 81.9 45.7 311.3 61.0 4. 2001:978:2:10::9 3.5% 169 70.6 100.0 46.8 414.1 74.1 5. ??? 6. 2001:978:2:46::43 0.0% 169 78.7 114.8 78.5 515.6 66.1 7. 2001:978::154:54:21:246 0.6% 169 79.2 114.0 78.9 457.2 61.9 8. 2001:978::109 1.2% 169 78.8 114.4 78.6 423.0 64.8 9. 2001:978::108 1.2% 169 77.6 117.7 77.6 420.9 67.0 10. 2001:978:4::2a 1.8% 169 83.3 119.0 78.2 510.3 74.3 11. 2001:978:2:7::1b:2 0.6% 169 78.3 117.6 77.7 500.8 73.0 12. 2001:4860::1:0:4ca3 2.4% 169 81.3 118.5 78.6 517.2 71.5 13. 2001:4860::8:0:5038 1.2% 169 80.2 122.0 78.4 482.2 65.0 14. 2001:4860::8:0:5e18 1.8% 169 91.2 120.9 84.4 457.1 62.4 15. 2001:4860::1:0:4a3a 0.6% 169 86.7 132.8 85.6 440.5 63.2 16. 2001:4860:0:1::66b 1.2% 169 88.0 125.4 85.0 401.6 65.9 17. par10s10-in-x09.1e100.net 0.6% 168 86.7 120.6 84.6 398.7 60.0 Traceroute to guifi.net (normally has not problems (is so near from here)): Host Loss% Snt Last Avg Best Wrst StDev 1. 2a00:1508:1:f820::48:cf6b 0.0% 22 112.9 23.1 0.9 112.9 38.1 2. 2a00:1508:1:f000::1 4.5% 22 54.2 93.2 45.8 362.6 93.9 3. 2a00:1508:1::1 0.0% 22 92.8 81.5 45.7 233.7 61.3 4. 2a00-1508--5.ip6.guifi.net 4.8% 21 53.5 76.7 49.2 303.0 66.9 Other problems are some periodical and small disconnects. Thanks!

11 years, 5 months

1
1
0 0

We need the firmware working in guifi Madrid

by Gioacchino Mazzurco

Hi! I don't remember well if finally we got to have libre-mesh enough stable for use/testing, or if we are still experiencing random strange problems, do we have some news after hackmeeting ? The other day I was in a talk about guifi in madrid, and also talked a little about libre-mesh, the result is that people of guifi madrid are very interested in using libre-mesh, because it seems it is more adapt to their network topology ( at moment they use point to multipoint and seems this is affecting negativley the growing rate of the netowork ) BTW from what i eared they have mostly ubiquity devices, with just one ethernet port that with libre-mesh will be needed both for mesh and client access, so stable working vlan is now a must ( disabling mesh or client access on eth0 to cope with tplink switch bugs is not acceptable anymore ) so let's see what we can do ;) Moreover we are trying to organize a little hackerasmus session during xmas vacation, hopefully we can advance with the firmware ;) bye!

11 years, 5 months

4
3
0 0

Talked with felix about 802.1ad vlan

by Gioacchino Mazzurco

The resume is he have no time to do it now, but if we send to him patches for netifd he will merge them. He suggest start working on latest netifd used by openwrt trunk <G10h4ck> Hi! <nbd> hi <G10h4ck> I am gioacchino from libre-mesh <G10h4ck> before anything <G10h4ck> many thanks for implementing mac-vlan in uci <G10h4ck> now we need something very similar for 802.1ad vlan <G10h4ck> this would help us and more people affected by tplink shitty bridges <G10h4ck> because we have tested and 802.1ad vlan packets are not dropped by the switch, while it drop 802.1q <G10h4ck> in this page also it is reported something http://wiki.openwrt.org/doc/networking/network.interfaces <nbd> right, this would need to be implemented in netifd <nbd> the code has to be changed to use netlink instead of ioctl to configure vlan devices <G10h4ck> i imagining something very similar to what you done with mac-vlan, am i wrong ? <nbd> it's a bit similar <nbd> but involves more rework of the existing code <G10h4ck> are you planning to do this soon ? <nbd> i don't have time to work on this at the moment <G10h4ck> ok <G10h4ck> how is going work with ath9k ? <G10h4ck> i remember at last WCW you talked to me about a feature that would increase speed, and cannot be easly implemented by proprietary driver because they work a lot at firware level <G10h4ck> while a good amount of memory was needed to implement that ( i remember the precondition but not the feature :P ) <nbd> it's mostly a latency improvement <nbd> still working on it, but much of the infrastructure for it is done <G10h4ck> many thanks :D <nbd> you're welcome <G10h4ck> nbd if we do a patch for netifd, there is to have the patch integrated soon ? <G10h4ck> because some time some patch need eons to be integrated :P <G10h4ck> and from what branch do you suggest to start working on this ? <nbd> if you send a patch against netifd, i will review it and merge it when it's okay <G10h4ck> ok <nbd> you should work on it with the latest git version of netifd <nbd> used in openwrt trunk <nbd> brb <G10h4ck> thanks, see you soon!

11 years, 5 months

3
6
0 0

BitCoin flowing accross librenet6

by Gioacchino Mazzurco

:D

11 years, 5 months

2
1
0 0

Libre-Mesh talk video (in spanish)

by Nicolás Echániz

I uploaded the video of the talk during the Hackmeeting in Txirbilenea: http://blog.altermundi.net/movieclip/libre-mesh-en-el-hackmetting-hackgarai… Do we have a video of the Libre-Mesh talk during the IS4CWN ? cheers, Nico

11 years, 5 months

3
2
0 0

bmx6: more useful ipAutoPrefix?

by Gui Iribarren

Hey Axel, here i am, haunting your dreams again with tricky questions... ;) [i'm trying to get all interfaces of a node have public ipv6 addresses, instead of the fd66:66:66:: autogenerated ones. but ipAutoPrefix is not flexible enough, and assigning addresses manually (outside of bmx6) and then using bmx6 globalPrefix would be a hassle. the ideal would be to leverage bmx6 ipAutoPrefix feature, but with a smaller prefix (/64)] ipAutoPrefix currently needs to be a /56, so that two bytes can be set to the interface index, and form a /64. Why does each interface *need* to have a /64? could it be simply a /128? (or something smaller than a /64, at least) (outside of ULA space, it's relatively uncommon to have a /56 available for each node; a /60 would be more realistic, and /64 would be ideal) currently scheme AFAIU: XXXX:XXXX:XXXX:00II:MMMM:MMff:feMM:MMMM/64 Xs = ipAutoPrefix nibbles II = interface index Ms = mac nibbles maybe this could work the same: XXXX:XXXX:XXXX:XXXX:00II:MMMM:MMMM:MMMM/80 this way, ipAutoPrefix can be a /64, interface id is still there and while the EUI-64 format is dropped, i don't think that's a problem? i understand each interface should have it's own distinct network, as it is now. so, to maintain that, the size is a /80 (yay!) but maybe it could turn directly into a /128, like i asked before? again, i'm not sure how these addresses are used / why they are needed, so feel free to say simply "no, that wouldn't work at all" or "that'd break backwards compatibility" have a nice weekend, as always! gui

11 years, 5 months

2
1
0 0

Re: [lime-dev] [guifi-euskalherria] [guifi-users] Próximas actividades de Guifi.net

by al

----- Mensaje original ----- > De: "Asier Garaialde - GipuzkoaShare" <agaraialde(a)gipuzkoashare.net> > Para: guifi-euskalherria(a)llistes.guifi.net > Enviados: Martes, 5 de Noviembre 2013 10:15:17 > Asunto: Re: [guifi-euskalherria] [guifi-users] Próximas actividades > de Guifi.net > Kaixo Al, > Me gustó mucho la charla que disteis sobre LibreMesh Muchas gracias, les he traspasado tu feedback a los charlistas :) > y quiero empezar > a hacer unas pruebas. El firm de LibreMesh esta ya suficientemente > 'maduro' como para hacer pruebas en semi-producción o todavía está > para utilizar únicamente en entornos de testeo? Me lanzo a probar > con LibreMesh o todavia es conveniente usar qMp? > Pues eso... > Me hubiese gustado quedarme para charlar con vostros mas > tranquilamente pero por rollos del curro, el sabado por la tarde > tuve que salir escopeteado... > Aio! Óbviamente el firm de Libre-mesh no está suficientemente maduro, pero las otras redes en las que ha venido trabajando el equipo de Libre-mesh sí que tiene el conocimiento necesario para ayudaros en crear una red en producción para una comunidad. Dinos qué necesitas (número de nodos, qué zona, si es entorno rural/ciudad, qué recursos teneis,...) y te podemos ayudar a buscar la mejor solución. Lo que salga de ahí en un futuro tendrá la posibilidad de hacer un upgrade a la primera versión recomendada para uso autónomo de Libre-mesh.

11 years, 6 months

2
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

lime-dev