- lime-dev - listas.altermundi.net

Fwd: [guifi-euskalherria] [guifi-users] Próximas actividades de Guifi.net

by al

Hello. After libre-mesh speech in Hackmeeting 2013 - Sestao, a local person from Euskal Herria send to Libre-mesh crew congratulations and ask about to start to use it in his zone (see below). I'm gonna answer asking about if is rural area or city (for interferences in 2,4GHz, but I think he lives in rural area) and explain him possibility to have roaming. I think we can help him with a pre-tested binary for his zone, explain that we are in pre-beta release, but qMp project and Altermesh project are in production in several communities. He has tech knowledge. ----- Mensaje reenviado ----- 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 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!

11 years, 6 months

1
0
0 0

HackMeeting Iberico

by Gioacchino Mazzurco

When do you arrive? We leave from madrid at 9 am tomorrow so i think we will be there more or less at eating time see you soon!

11 years, 6 months

2
1
0 0

CONFINE Open Call

by Nicolás Echániz

Hi all, I know some of you are skeptic about presenting projects to CONFINE, but I believe, from what I've been able to talk to different people involved that we have a chance with libre-mesh. I have already agreed with the head of the Networking department at the Universidad Nacional de Córdoba (a reowned University in Argentina) to present the proposal from their institution. I've also checked that Argentina is one of the eligible countries, according to: http://cordis.europa.eu/fp7/ict/programme/home_en.html I've also confirmed that the closing date will (most likely) be extended. So... I've started writing a proposal in this pad: http://etherpad.guifi.net/libremesh-proposal (only the abstract is written so far, the rest is just the template) I'm working on this with Daniel Britos, from the UNC, but I've been thinking that others on the list might have some time to help, specially Isaac :) I want to have a good head-start during the next few days and I plan to finish it during the first days of our return to Argentina (although I need to confirm the CONFINE closing date). Ok... so that's the plan, anyone who wants to help is welcome. Cheers, Nico

11 years, 6 months

2
2
0 0

Google Summer of Code 2014

by Gioacchino Mazzurco

Hi! I have participied with ninux to google summer of code for two years as mentor, this year i have the feeling ( not confirmed ) that ninux is not mooving on for GSoC for some internal iussue. With GSoC we can take ~5k$ for each students ( for example me and p4u ) participating and 500$ for each mentor participating ( for example nico end gui ), the only draw back is that we need to prepare some burocratic stuff What do you think, is guifi participating this year? I think 10k$ would be a good sprint for libremesh project ( without google noticing we can handle that money as we prefere... )

11 years, 6 months

3
3
0 0

mesh distributed system using bmx6 sms

by Pau

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Quick example of how the BMX6 sms plugin can be used to implement a very small distributed DNS system. http://bmx6.net/projects/bmx6/wiki/Mdns Maybe we could reuse it for libre-mesh in some moment. - -- ./p4u -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (GNU/Linux) iQEcBAEBAgAGBQJSaQboAAoJEAX7rWpc+YnNYIYH/2LrjOWnVsGxIjUR5mG2ccON vH3qcRUsMEdFVR1uryIyU8zWDZRapuYtFPxyLsBBht3xxXTXxBEIvLU4Hn1DuHF2 PWEotwvUFDyA+r5AO56WF3a2E6OLspovuSIlXVUc8m06jcpsUTPtU3Lkkmycs75B BgMWyeY4CMt+xDmCA8j7Zc7UyhZY5tqGbDFDq0TL6lb9q2JaYHkwXsXohdE8ndRO T2TQ5G0dLSKb+KvAhapZh81gDBXecGDDbo6YKZ4QnPcT2KM/FUYChqP74gRwJAQE f+LrJc4RXWEh37t2obr+c/oFM0UkGOKGXHCV56kq+1aYlldPS+FU8rDta6Xv9lw= =OkFJ -----END PGP SIGNATURE-----

11 years, 6 months

2
1
0 0

Paper about a qMp deployment in Barcelona

by Pau

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Find here a scientific paper about a qMp network deployed here in Barcelona. The title is: Experimental Evaluation of Wireless Mesh Networks: A Case Study and Comparison http://edss.isima.fr/workshop/wp-content/uploads/paper_22.pdf PS: sorry for crossposting - -- ./p4u -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (GNU/Linux) iQEcBAEBAgAGBQJSaB0CAAoJEAX7rWpc+YnNcoIH/jyF81DpEoDAHkpY5wbuI+nG oha9DcQHUEFdVHZMe10b42qaWArMuAiRHcfJGumHKJitFfM5Tn0NjLPdXxJrwt3/ V32JQXHbPnvfjHwnmKbuXO9wGtVFBvBwbBTyHirdQiiNBw3+h9xxBkQSUatdubzN HcM6pes139LdFT2bIyuiAcqKvNz6ggPhqo3vMDo/XvU9hpFJALbT4PT8M/NXcYXJ 0aQYd4dMqvUYr0SdaltCMikR+aUVhXVxbPNBFfyE9FxNtqrN7SffG8nqySQwe0cp vkMdhNQcuDo15LGBfREv+4BteOPv1K62dYEBt3fksr8ZjjWbpKtExv9esD3pHcg= =L+Ez -----END PGP SIGNATURE-----

11 years, 6 months

1
0
0 0

New network in rural areas in Brasil

by al

Hello from Guifi.net - Catalonia. People from a rural hacklab in Itatiaia (Brasil)[1] are going to suporpt a intensive project for start to develop a free, open and neutral network in rural areas in Brasil. 1st part of project start September 5th until 20th. We're going to research social, economical and technological reality in rural areas in Brasil, to make some links in this area and to develop free software for their needs. Of course I was thinking to do it with Libre-Mesh in cheap routers and I hope some of you find this project interesting to come to work on it together. They pay travels, food and host for a little team (3-4 people). I can not to decide who (they do it), but they tell me that if I know about people that have the profile that I contact them and say them that tomorrow 13th or 14th they are going to open the call to collaborators. So, you are the people with perfect profile :) They are going to choose first people that propose him or herself to the project. At same time they are 3 or 4 other several projects about rural and tech's. After this meeting we want to continue development of free networks in Brasil and we're going to work in to get more supporters in contact with "forumdainternet.cgi.br", "Tropixel" and "Saravea.net". Thank you! PD: Some of you can give me permissions to edit Libre-Mesh wiki? My username is "al". Thank you. [1] http://nuvem.tk/

11 years, 7 months

5
13
0 0

Definition in english of Libre-mesh in home page, please correct expressions

by al

Hello, this is a call for native English-speakers ;) We made a definition of project. We made it in Spanish and then we translated it to English, so the concept is good but maybe the expressions used on it are not much. So maybe you Isaac (or other native English-speakers) can take a look. http://www.libre-mesh.org/ Spanish original is here: http://es.wiki.guifi.net/wiki/Libre-mesh Thanks.

11 years, 7 months

3
4
0 0

dhcpdiscover

by Pau

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi. What do you think about this? https://github.com/p4u/dhcpdiscover Could be useful for us? It can be executed to know if there are DHCP servers (different to you) in a network interface. root@qMp76:/tmp# dhcpdiscover -i br-lan DHCP ok: Received 1 DHCPOFFER(s), max lease time = 3600 sec. root@qMp76:/tmp# dhcpdiscover -i br-lan -b 172.30.22.1 DHCP offer comming from the banned addr 172.30.22.1, ignoring it DHCP problem: No DHCPOFFERs were received. Could be used for knowing if a network device is plugged to a WAN modem or not. Cheers - -- ./p4u -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQEcBAEBAgAGBQJR3FUmAAoJEAX7rWpc+YnNtxAH/3YeM1OdlvPP1A3dXQOQC4Wl bVC0i6F8JRU1sIWaFpLbEIFXteCgPn8EhGD0Li+77ZDkbKJT2vPuBLpgmumdGABb 38P04bTFj0Mag1mlUmF7RdyXpNOAofNBq0Ok4gWOp1AISwDOATFueOtuOZihkJVJ HV8m7KvR9BLR9q1ssod5Hm/t7ca7n+pgCV39plmRMHOahwnR32PkuLZsbiniV3v2 qujV92/ymtCJR5Wv44iwGK0m8jl7GU9YJwUCvPXdVkXm+aY6cxyYU+t5m9l50yoA gfTyQN57nK0Q/8GT0TrL4UUQpumdfqLRO3OynCDJkofAtCUIAlWDkpGWLD9oNTk= =lGut -----END PGP SIGNATURE-----

11 years, 7 months

3
3
0 0

quick comments about bmx6

by Gui Iribarren

just to note down what we talked yesterday: 1) on the wiki, http://bmx6.net/projects/bmx6/wiki/Wiki#Blocked-Nodes there's no mention at all that the module "ip6_tunnel" is needed, probably useful to note on compile/install section? 2) there's also no documentation whatsoever about globalPrefix only thing i could find is on the help: --globalPrefix <NETWORK>/<PREFIX-LENGTH> specify global prefix for interfaces but from what i tried, if a globalPrefix is set for an interface (or globally) and the interface doesn't have any ip on that prefix, then it does not get an autoconfigured fd66:66:66 either, and the interface stays disabled. I don't know if that's on purpose, i expected that if the interface had no address in that prefix, it would get activated anyway with the usual fd66:66:66. in any case maybe doc should be more verbose about how it works? finally, 3) you asked for some links about tunnels: tinc-vpn is the mesh vpn, that works perfectly and is a great idea, but being userspace it kills cpu with high traffic http://tinc-vpn.org/ tunneldigger was made by slovenian people, is a simple userspace daemon that sets up L2TP tunnels (kernelspace) to a set of tunnel "servers" https://wlan-si.net/en/blog/2012/10/29/tunneldigger-the-new-vpn-solution/ high traffic is not an issue, but it works in a hub-and-spoke model, there's no mesh concept whatsoever cheers! gui

11 years, 7 months

3
4
0 0

bmx6 slides

by Pau

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Find here the slides of the Axel Neumann's talk in the IS4CWN about bmx6, explaining the basics of the protocol, showing the results of some tests (comparing with OLSR) and explaining future developments. http://bmx6.net/news/15 Cheers - -- ./p4u -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (GNU/Linux) iQEcBAEBAgAGBQJSUAoWAAoJEAX7rWpc+YnN9c4H/jGBpu/TzoJg2/fM+c78mcRk wfCotUEeAzS7/KOgLzuRUPewyrTd6JnTf+pAFeSHdxAuunBuUKN2rsYIu8nv9J/c TGCCyIQbxtYVeVk1Xj1Y0JtLh9Pp18FBo20cpjrFOBqxArnM6K3lqo+8DFjRNErs QnWr/PKJF1KO+hxkYyOpbTJjNFB61kxTBEkDAZpeGt8iyQXz9tsX1LRcUtWkXxbB ZVw5ozQ8VI7dpXiQCd6AwBbSf5dfAuKrGgiIuhtwUylC0B3ne/eMyFCZuSQU0Kku gtKLWHmCyDT07JtX3EiOhRasyz/6Pt92yd2nEA9LeBZyAdQ1pL4nfwRwCDnonXU= =pNfS -----END PGP SIGNATURE-----

11 years, 7 months

1
0
0 0

Network architecture in the wiki

by Pau

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Please, take a look to this wiki page. I would like to use it for the Libre-Mesh presentation of this afternoon in the IS4WCN. http://dev.libre-mesh.org/projects/libre-mesh/wiki/NetworkArchitecture Please, feel free to modify it, improve it or add missin things. Cheers - -- ./p4u -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (GNU/Linux) iQEcBAEBAgAGBQJSTqqHAAoJEAX7rWpc+YnNuNUIAJNPEgPXn1mdxrMoH2KYslzO vGEq794baPqa76Ca943SGSaGUeYCILPBtqCiRcqy2xbBczYgHnCT4O+0P9I9C91p kZa0cj1KQJaqaNUiOBOVrgHTTLp+vds4Bluu/vtHaHPY2pPKw+JnS3gPyEEIG+I9 wK821xlVfj6EDOmiyCjUyKDMqL7M7yq5ytAtEhQQGzL56scGyRXStgYzbkWY/lfA kuxs2eG9uPy8uSKEHZgqNtC5iup3sQ+t9lTyfbotPoWqO3rQEIe70RxbSD7G3FjC QhqpRqUnf/hHx9dTLG3Q/HJ7GghBtqMsunuvkcUiBmo5pRnF/rrO3N6Jr2bhGWM= =37+O -----END PGP SIGNATURE-----

11 years, 7 months

2
1
0 0

PhD thesis about BMX6 routing protocol

by Pau

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Recently a PhD student from Belgium has published his thesis named "Analysis of the BMX6 routing protocol". It is a 109 pages document explaining all BMX6 details and comparing it to OLSR. I've not read it yet completelly, but it seems a very good document for those who want to know more about the routing protocol. Find it here: http://bmx6.net/news/14 Enjoy it! - -- ./p4u -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (GNU/Linux) iQEcBAEBAgAGBQJSSn89AAoJEAX7rWpc+YnNjSkH/jQyQefbhonYSxPdFKoT3Q06 gCq164hSEpT0jeb6h3fPCKw1eWI2xour7MjVdLBm4lstDkuMnY5iOjh3OljtfHQE /LXu+/L3C/3rgmTqzSfQZyLSwYFjTeYAKak0WG88boYZFT3ZbWMTVCzfXZgyK6CC itZzc5HwGos6no5+Ne05+ItC3Y/wn1lqocMqVAmS+A+hHPPIUJnLRfIwlaSEFyt2 DdZLDP5NCC9/sKYFm/5AC62KxVDYEKi0itW+EKJZsNogTtPgaJT3HzUxLva1oiGm yUDHQ2Ynu3iIpBCDb27r0nv/5EqP4Vy9pqtGsPGEcOeytm7qV7FoSC/fub0UWsY= =v3Jb -----END PGP SIGNATURE-----

11 years, 7 months

1
0
0 0

#libre-mesh bridged on Retroshare

by Gioacchino Mazzurco

As i mentioned some time ago, the #libre-mesh channel on freenode is bridged to libre-mesh lobby on retroshare Someone asked for the code but at that time it wasn't released yet, today the autor informed me that he released the code under LGPL on github https://github.com/sehraf/RetroShareChatBot have fun ;)

11 years, 7 months

2
1
0 0

lime meeting before and after the summit

by Gui Iribarren

hello fine folks, so, here we are with nico planning dates, we are going to arrive to barcelona this friday 27 in the morning, p4u, do you think we can meet before you leave (on sunday)? i.e. this friday or saturday we'll be staying at Can Masdeu those days so you're welcome to come, or, we might go down to barcelona if needed so that we can review together the progress so far with isaac, i hope we'll be able to coincide after the summit, 5/oct in berlin really happy to see you soon!!

11 years, 7 months

6
9
0 0

Talk on libre mesh at Universidad Politecnica Madrid (UPM)

by Gioacchino Mazzurco

Hi all! Some people from ACM [1] have proposed to me to do a talk about something I do/like about networking at Computer Science Department of UPM, i was thinking on talking about libre-mesh so i can talk also about human aspect of netowrking and not only about tecnical stuff what do you think about that ? [1] http://www.acm.org/

11 years, 7 months

3
5
0 0

Libre-mesh.org down

by al

Hello from Brasil. I'm working on Libre-mesh network deployment here for two weeks. I need resources as map, code, firmware,... Now all is down. Please can you give up again? Maybe we can make a on-line backup server in order to have high availability and not to depend just for one server. We can have a redmine/nginx stable and the other one for testing. (I said that because we had two downs just last month, please, I'm a little bit worried).

11 years, 8 months

5
4
0 0

#libre-mesh on IRC bridged with libre-mesh on RetroShare

by Gioacchino Mazzurco

Hi! Thanks to help of people on retroshare we achieved to have #libre-mesh on freenode bridged with libre-mesh on RetroShare so now we can chat on bot networks with all, the only glitch is that people on one network will not see people on the other but just on the list, the messages will be relayed by the Bridge nick that will report real author as part of the message This is an important step, RetroShare is a P2P secure and encripted netwok, so there is no need for servers, it is just like mesh but on layer 7 and it is particular important because it will encourage local traffic instead of remote one, and decentralization that is all good for our fredom networks :D Also ipv6 for retroshare is in plan for 0.6 version ( we are at end of 0.5.x series ;) so we will have it soon ) And i am developing the GUI for androis so we will have scure messaging on phone too ( VoIP is in plan we already have some working plugin prototype so soon secure call too :D ) see you!

11 years, 8 months

3
4
0 0

web page down

by Pau

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi. The web page is down again: http://dev.libre-mesh.org Do you have problems with the server? I could find some server to allow it if needed. Cheers - -- ./p4u -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQEcBAEBAgAGBQJSE0BZAAoJEAX7rWpc+YnN+roIALii6E3yiHJM7YeUxTLaq9qi +I7Iz1Mui/eRhQ1Hiclul6akRnmFbXhOZ/kPepT889W9kUQVhg34CkF74S8mN+Tq MMgLAK9+uel3dr1hXrd7a9od7NbEgCnzKPpyVCVVQ9hYOIoO2YYug6hyNMrlq4jl HdEDSS1IpfUhIexWOgU6eLr/jJmyslfi+xIwtLbamwZ5MuZWAfLF3gZVsRM8LlwX nIUT/epu5tUENgJcC8nDhHxHCcR9BAMZxzOEdY6wdXLHRSl4tHjQAdB9GvSaghpn bUPf7siz8MEhpIuye7Xm3uBs7DyXdTsmAVdxYayIfudhn+iGofk38oYVuRyIC6E= =opzk -----END PGP SIGNATURE-----

11 years, 9 months

2
1
0 0

Re: [lime-dev] Opened form to ask for travels to Brasil! (it was: "New network in rural areas in Brasil")

by al

----- Mensaje original ----- > De: "al" <al(a)blogmail.cc> > Para: "libre-mesh developement" <dev(a)lists.libre-mesh.org> > > https://docs.google.com/forms/d/10bij_tMJSGkZrt2LYDhmI14Wo-xtM1O-oS0llG-481… > > Please developers, ask for your travel. > > They just opened call for collaborators. They're going to choose > first people. > > It only take 10 minutes. Organizators wrote "Guifi.net" in project. But it is a new free, open and neutral network based on Libre-Mesh.

11 years, 9 months

2
3
0 0

https://libre-mesh.org/ down !!??

by Axel Neumann

Hi, Currently, broswing to https://libre-mesh.org/ results in: 502 Bad Gateway and http://libre-mesh.org directs by to a map (NOT the unsecured libre-mesh project side). Anybody available and able to fix that problem? thanks /axel

11 years, 9 months

2
1
0 0

Re: [lime-dev] [Mesh] From libre-mesh

by Pau

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 CCed libre-mesh mailing list. On 29/07/13 12:29, Pau wrote: > Hi. > > First of all, running layer3 protocol over layer2 protocols would > be completely stupid, so just discard this idea. > > The Isaac explanation is right. But as said the scope of libre-mesh > is to be compatible with most of the possible scenarios, so what > Isaac said is just one of the models libre-mesh will be able to > support. > > Another scenario (the one I like more) is having small batman-adv > communities (let's say a building, a neighborhood or maybe a > district). These communities are connected with other communities > using layer3 protocol (such as BMX6). So at the end you can end-up > in a city with 20 bat-adv clous connected all of them with BMX6. > > The selection of the border-nodes have to be made automatically > (to scale better and to be as easy as possible for the normal > user). So there will be a mechanism to discover if a node is > border-node or not (if it is connecting with another node which is > using anode batmand-adv ID**). It can be achieved by a very simple > protocol based on ICMPv6. So, once a node see that he is a border > node, it starts BMX6 automatically to start sharing routes between > both batman-adv clouds. > > Following this approach libre-mesh will be able to cover both > scenarios depending on the user needs: > > - A big bat-adv cloud for all the city (if batman-adv ID is the > same for all nodes). > > - A lot of small bat-adv clouds connected with BMX6 (each small > community decides the batman-adv ID to isolate from other small > communities). > > At this point I believe you understand why using a mesh dymanic > routing protocol instead of BGP. > > Please, take a look again on the diagrams I included in my first > mail, they are trying to explain it. > > ** batman-adv ID is the VLAN tag used to isolate clouds > > Cheers > > On 29/07/13 05:09, Mitar wrote: >> Hi! > >>> but I don't think you're correct in your assesment of how the >>> system would work. > >> Probably. :-) I don't have a clear mental picture of it. > >>> If such a link is persistent, and of a sufficient quality then >>> those node (and only those nodes) would route between >>> communities using bmx. > >> And why not just BGP? So why using a routing protocol which was >> optimized for wireless links to run over something which is not a >> wireless network anymore (but an abstracted L2 Batman network, >> which might be somewhere deep in a wireless network, but none of >> this is seen to BMX)? > >> The only thing you need is "network is available"/"network is not >> available" announcements which knows how to read Batman >> community IDs, no? You don't really need packet loss measurements >> for wireless links? > >> Can Batman on one node participate in multiple communities at >> the same time? > >> Have you seen this? > >> http://www.open-mesh.org/projects/open-mesh/wiki/Connecting-Batman-adv-clou… > >> So I do understand that you need some kind of L3 routing >> protocol on borders between L2 routing domains. But I am not >> exactly sure how this would work as a generic auto-configuring >> firmware. For example, if we have two L2 mesh networks: > >> ------------ ------------ | >> [gateway1a]--link A--[gateway2a] | | mesh 1 | | mesh 2 >> | | [gateway1b]--link B--[gateway2b] | >> ------------ ------------ > >> I am not sure how could gateway1b and gateway2b be one device, >> one node? And with an auto-configuring firmware? > >> Both mesh 1 and mesh 2 are big L2 blobs. What I can understand >> is that gateway1a and gateway1b is part of mesh 1. And gateway2a >> and gateway2b part of mesh 2. They have between them each a >> special network link, respectively. So gateway1a/b have their own >> IPs inside mesh 1 and they also have IP inside the peering links. >> Same for gateway2a/b. > >> So I know how to configure this manually. But I am not sure how >> BMX6 running on gateway nodes can just discover this >> automatically? And even more, how it can know over which link to >> route traffic? Link A or link B? It does not have any special >> knowledge of how well gatewa1a or gateway1b is connected to the >> rest of mesh 1. But even if we ignore that (which is really a >> hard problem to solve), the reason why BMX6 would be useful is >> because link A and link B can be of different link qualities and >> you want to route over better one? > >> And how does BMX6 then propagate this information that link 1 is >> better than link 2 to clients in the mesh network? > >> And still, how you configure those links automatically? > >>> I agree strongly that the way to encourage adoption is to >>> build, use, and demonstrate. At the same time, we will make >>> much more progress if we can find ways to collaborate. I tend >>> to agree with the comments regarding in-person collaboration. >>> Perhaps it would be possible for you to come and talk things >>> over when Pau and Roger are in the states? > >> I agree that discussion in person can help. But sooner or later >> we have to write something down. If you already have clear image >> what you want to build, then just write this down. Discussions >> are important if we need to create a solution. But in this case >> you are saying that you already have a solution. Can you just >> write this down? > > >> Mitar > > > > _______________________________________________ mesh mailing list > mesh(a)lists.sudoroom.org http://lists.sudoroom.org/listinfo/mesh > - -- ./p4u -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQEcBAEBAgAGBQJR9oH9AAoJEAX7rWpc+YnN4cUH/2MXqLVEQjQMpkEDifKBeA7C Rpwd0FfYb3xTRqaykK2O0zfS8g5z6KQKjxqw+HEen0VELPNcedeMu2n5AVvsSdvQ YPwmBgHMeA5WxQUAM5TO+CsF03+veKTkE26ZynVsp2ZQojv/uCa22BustKYZXiZq hB2o03Rx03JnM6GFB0b4cLzmw3rHWSApuFGj7Fa7uwrdQRrPIW5k12R72zNDJzWT 0EijNQADhSctIhdB2LRpXeYkLbdaSLcseHuY0oAwTfIblbugsgDFnR96iwffXdF+ YeY2YdGQh2uzZsa2PVD4/1DE2iVQf4/J/UCRBWSZSRBLLLMrS5hRwMFLm/tXU78= =PcuD -----END PGP SIGNATURE-----

11 years, 9 months

3
4
0 0

Re: [lime-dev] [Mesh] From libre-mesh

by Pau

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, this kind of discussions is what I was trying to avoid... but it is my fault for starting it. On 28/07/13 01:30, Mitar wrote: > Hi! > >> The idea is to make a meta-firmware which can be used as basis >> to create specific community firmwares. The project is named >> libre-mesh [5]. > > To throw a ball back at you: why another meta-firmware? We already > have OpenWrt. Why libre-mesh cannot be just one package for > OpenWrt, which configures and depends on anything you believe > should be there? Then other communities can just fork that package > and adapt it. Or just add additional packages. It is exactly what we are doing. Please see our repositories you will find lime-packages which is an OpenWRT feed. > Because I don't see firwmare anything more than just a list of > packages + configuration + few small scripts. I don't see this as > such big additional split of work as you are describing. Or is > there more to firmware development? Well, I would not say "few small scripts", it is a bit more than that. I don't know about which firmware are you speaking about but in my experience if you want to end up in a stable, powerful and flexible system you need more than "few small scripts". >> Batman-adv is very nice, but you cannot have a single collision >> domain cloud for all the nodes because it does not scale. > > Have this been proven/shown anywhere? Aren't there Batman-adv mesh > nodes with 1000 nodes in existence (or in fact in Batman-adv you do > not care so much about the nodes, but about number of individual > MAC addresses in the mesh, including clients and anything bridged > to the mesh)? Ask yo AlterMesh guys who are starting having problems with scalability. Can you imagine which is the total amount of ARP packages in a 1000 nodes bat-adv cloud? (just to put an example) >> So, the network have to be splitted in several clouds. To >> federate them a layer3 routing protocol is needed, so here is >> where we use BMX6 [7]. > > Why would you need to use BMX6 to federate them? Isn't just Quaga > with Batman-adv on both sides enough on a gateway node between > clouds? Or are you saying that BMX6 should run on top of Batman > clouds on all nodes and not just on gateways? Quagga is a suit which includes several routing protocols. Quagga could be used to federate bat-adv and bmx6. But if you are speaking about use static routing, I would just say it is a big mistake (what happens when you have to paths to the same cloud?). >> Why? because BMX6 (100% rewritten fork of Batmand with native >> IPv6 support) is very powerful and produces a very low overhead >> (see [6]). > > But how does this overhead compare with speed of convergence > (adaption to the changes in the mesh). Because overhead is in > general inversely related to speed of convergence. More packets you > send around, higher the overhead is, faster you can inform > everybody that there was a change in topology. So this graph > without a related graph of speed of how fast the routing protocol > adapted nodes is not really useful. So I am interested in a > scenario where somebody is actively talking to a node which is > moving around. If my connection to the node stays working while in > all cases, but one routing protocol has lower overhead to achieve > this, then this is a better routing protocol. > I agree with your approach about compare overhead and routing changes. However I can say this test was made during the WCW-Berlin. The scenario was around 15-20 nodes (ask UFO to to know it better) in a mobile scenario (it means someone moving nodes). All protocols were running at same time in different VLAN (see battlemesh firmware in github) so all of them were in the same situation. Just to give you another detail, the tested protocol which showed more difference between moving and not moving environment was Babel. By the way, the conclusion of this tests was: BATMAN based protocols are better in the overhead-mobile test. > Mitar > Cheers, Mitar. Hope to see you in October. - -- ./p4u -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQEcBAEBAgAGBQJR9F2YAAoJEAX7rWpc+YnN2/UH/2Jo0bujrjXBwGwN2vP5oi+q 5O5w5jQZ6uQEaeruwEXrmtNeucY1p9yNkXLhxDnSFWYQup4Qt4KvAdJPOQ+/pjBf 7khnwvHgD9Pupce/F8dLbmgrdUTlmThZdrug1EQHPnHwekTHwPO6/DraDYgf6Pzf NPu0QGQDFi0zk1sBbWxXeizvcmxXhgbID9yptp6p+XIn4wvJkAVw1d3N2jHcUDRe fg/KBQeUsCqViwMnclylOwS6Q73UpJ6yW4wVAiphwS7KpZHYn+X/yYK0NbD8kQfL 3EtUufaUxoAUgfan1qQJcP8ItEV24ylrnkJTueV06/DP65NS3O2RykfOPwM6Tyo= =skVf -----END PGP SIGNATURE-----

11 years, 9 months

7
15
0 0

Re: [lime-dev] [Mesh] From libre-mesh

by Gui Iribarren

On 07/28/2013 06:53 AM, Mitar wrote: > Hi! > >> We had several long, insightful discussions with the bat-team in Aalborg >> last battlemesh, it's a pity you couldn't attend :( > > Are there any summaries/minutes of those discussions? Because it seems > you have more knowledge about this and it would be sad that it would > stay locked just into discussions. Even if we meet on mumble, I will > maybe understand, but ideas and conclusions you are presenting still > would not be available to others. I think the best would be to write > this things down. There are measurements, there are all the discussion > from all the mesh events and it seems there is a common idea of "best > practices" shared by routing protocols. Could this be written down > somewhere and then it will be easier to understand? Writing things down is important, but takes time, and emails take even more time :) At the battlemesh, I was left with the cristal clear conclusion that the bandwidth of information flow in a physical meeting is incomparable to any other kind of communication meeting >>>>> video >> voice >> chat/email/etc in a week i learnt much more than i could have read in a year, let alone write down The executive summary of what we envision for libre-mesh (guys just like you Mitar, which met for the first time in april, and in a couple of physical afternoons agreed on a common working ground, after months of mail-misunderstandings) is published on http://dev.libre-mesh.org/, and is soooo similar to https://sudoroom.org/wiki/Mesh/Firmware that i think if we meet, in an afternoon we'll be working together. until then, let's start writing down... code! so, let's show each other code, and i'm confident all doubts and questions will settle themselves out, or be discussed over real, concrete designs and experiences :) > >> i'm really looking forward to meet you Mitar! maybe we can at least have >> a mumble one of these days? > > Sure, we could! But I believe the best would be first to write things > down, for others in the network and in general for all community > wireless networks. > > > Mitar >

11 years, 9 months

1
0
0 0

From libre-mesh

by Pau

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi. My name is Pau from Barcelona. I have heard about your project in the battlemesh mailing list. First of all, congratulations for starting such kind of initiative, I hope you succeed. In my place I'm working in the development of a Mesh firmware named qMp [2] which is being used mainly in our community network Guifi.net [3]. The purpose of sending this mail comes from what I read in your Wiki [4] about create a new firmware. IMHO it is a mistake since there are several projects already created, probably too much because we are dividing our strength. Recently (thanks to the battlemesh and other events like that) we have started a new project to put all the development efforts together and make a firmware generic and useful for everybody. The idea is to make a meta-firmware which can be used as basis to create specific community firmwares. The project is named libre-mesh [5]. Until now three existing mesh communities have joined: Guifi.net (Catalonia), AlterMesh (Argentina), Eigennet (Italy). I would like to invite you to participate. We have a huge experience in the OpenWRT-based distributions for mesh networking, I hope you are able to take advantage of it. I don't pretend to start a large discussion about routing protocols, but I would like to summary our conclusions because they can be useful for us. Batman-adv is very nice, but you cannot have a single collision domain cloud for all the nodes because it does not scale. So, the network have to be splitted in several clouds. To federate them a layer3 routing protocol is needed, so here is where we use BMX6 [7]. Why? because BMX6 (100% rewritten fork of Batmand with native IPv6 support) is very powerful and produces a very low overhead (see [6]). Here [8][9] find a couple of small diagrams to understand a little better this model. Cheers. PS: do not use ARC Freestations, they use Ralink USB chips and driver is bullshit in ad-hoc mode. PS2: CCed Libre-Mesh mailing list [1] mesh(a)lists.sudoroom.org [2] http://qmp.cat [3] http://guifi.net [4] https://sudoroom.org/wiki/Mesh/Firmware [5] http://libre-mesh.org [6] https://libre-mesh.org/attachments/download/12/overhead_mobile.png [7] http://bmx6.net [8] https://libre-mesh.org/attachments/download/4/smartmesh2.png [9] https://libre-mesh.org/attachments/download/17/lime-modes1.jpg - -- ./p4u -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQEcBAEBAgAGBQJR9FHbAAoJEAX7rWpc+YnN1wsH/ROdF+IsNU8X9Ub0BslkEVw4 d0ixSUH2WQKwxd58iIf+4TbsH4SXHUQlm726KnCJMRx2hzZ9E/dyItrVvbrk9Vbw YUS59VeVwqBqo39Pu16pxDoA4hrQa3yNi+Cq3CBOQlBh/oKf1r1OFNOznhkrzdNj 7pp/L146NSyl+TJ1U3nPpikf7AAvPVfU/ege/cLGrmDeP6rGdtArLJzGRDM/8syw pQ/A75u11IyFs00EgJJufhG4ZSbKoZIaePOZAfONPKi+WxRJZsJw4IDxp7Gd3+wF Dk5GPj5afDjSZpM8zxK88bwDUz6jW5S8V+pQd0+TnwcaqIrlYOqDI5ublyC9Z4s= =Nr0g -----END PGP SIGNATURE-----

11 years, 9 months

2
1
0 0

sort of sprint...

by NicoEchániz

Hi guys, Guido and I will be working during the whole next week on libre-mesh stuff. Our work time will be starting at 12 UTC every day of the week. We would like to work on this topics: * properly debug and report outstanding batman bugs: OGM starving and ttvn drops. * test the configuration guido and gioaccino did in Berlin on a local testbed. * start working on auto-configurtation scripts, looking into the existing work done during the battlemesh and afterwords. * luci-based web interface for antenna alignment It would be nice to work together with the rest of you if you have some time available during the week, so we can get the ball rolling. Cheers, Nico

11 years, 10 months

4
3
0 0

meeting

by NicoEchániz

Hi txantxitos, I wanted to let you know that after some weeks of network instability here in Quintana while we tested a more recent revision of OpenWRT/AlterMesh I am now done with that so I can get back to other things. How about your time schedules? Could we agree on an IRC (#libre-mesh) meeting for this week to organize the work ahead? It could be Thursday at 4PM Barcelona, 11AM Buenos Aires for example. Are you guido on a plane at that time or is it oK? Cheers, Nico PS: I am seeing an error (502 Bad Gateway) in: https://dev.libre-mesh.org/ Guido could you have a look?

11 years, 11 months

6
17
0 0

Fwd: [Nodogsplash] LuCI page for configuring Nodogsplash

by NicoEchániz

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Maybe this can be of some use to us... it would also be an excuse to interact with the Commotion guys. cheers, Nico - -------- Original Message -------- Date: Wed, 29 May 2013 10:03:56 -0400 From: Dan Staples <danstaples(a)opentechinstitute.org> To: nodogsplash(a)ml.ninux.org Subject: [Nodogsplash] LuCI page for configuring Nodogsplash Hi all, As part of another project, I created an OpenWRT LuCI page for configuring Nodogsplash (similar to luci-app-splash). It lets the administrator set leasetime, which interfaces/zones to captive portal, whitelist and blacklist MACs, whitelist IP ranges, and set the splash page text. It's certainly not all the Nodogsplash options, but enough for a simple setup. The Nodogsplash default splash page I include also uses a simple javascript redirect to point to a LuCI-created splash page, which allows you to use your router's web interface theme and include LuCI headers/footers and whatnot on the splash page. Just wanted to throw it out there in case it would be of use to anyone. The source is here: https://github.com/opentechinstitute/commotion-splash I would love feedback on it if anyone has any. I also haven't tried it on vanilla Attitude Adjustment, I've only used it as part of the Commotion OpenWRT-based firmware. So the one caveat is that it depends on a small lua file being present in /usr/lib/lua/, which can be found here: https://github.com/opentechinstitute/luci-commotion/blob/master/luasrc/comm… cheers, Dan - -- Dan Staples Open Technology Institute https://commotionwireless.net _______________________________________________ Nodogsplash mailing list Nodogsplash(a)ml.ninux.org http://ml.ninux.org/mailman/listinfo/nodogsplash -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQEcBAEBAgAGBQJRpi7dAAoJEPHORz17N0TFOKYIANRQuLr74RU+H0rtXa26KInh cWOLlrYLi6sjB02NFL1kID7C2pVaWV+F/oYghTs//Z9PZM1EwmqP3OZwm4mB4Vni EWxN8Ol+Mlf2XVJkntAlSNEShzNFrt9VDt6dz1+eJ43Pwy21IYFdJ1wfXpKvkRQ5 /UkajGkAKk5Pl2jAy7r3WBwIUh74KlpyklEQvQlkbWdTZk1SezErci2HbTGo5VLz MI69cYtoHNLcDH8ChHQAooTCnTH3OgWEte2t6ZMZBcz03hFpV91PIb+HlKBBtLpS zrZWDctHal5hoKP37wv582nLPWClr9onc+AtAHs7UTESNI5798xf+5B/S3qjOR4= =qqdW -----END PGP SIGNATURE-----

11 years, 11 months

2
2
0 0

autconfig/autobuild

by Gioacchino Mazzurco

In eigennet firmware we really didn't have a build system, so have an autconfig script inside the device make a lot of sense, but in libre-mesh we have lime- build and chef, so were we put the limit between autobuild and autoconfig ? Autoconfig works well on simple devices like picostation or nanostation, but on more complex setup like the black tplink is not the good approach, so i was thinking about completely moving to a build + profile system without or with minimal autoconfig script on the device what do you think about that ?

11 years, 11 months

3
5
0 0

qmpfw y Chef

by NicoEchániz

Hi Pau and SAn, during the brainstorming sessions that gave birth to libre-mesh we talked about integrating qmpfw and the firmware Chef. Pau and SAn are the guys behind the development of these tools, maybe it would be interesting to start coordinating how this can be actually implemented? Cheers, Nico.

11 years, 12 months

3
3
0 0

magic icmp

by Gioacchino Mazzurco

I saw that it depends on libpcap, it is the only way to listen for icmp messages? In this case i think it is not the case to use icmp protocol and instad would be simpler and more performant just a simple udp multicast socket like bmx6 do

12 years

4
11
0 0

Listening to icmp

by Gioacchino Mazzurco

Now I am asking to my self, how ping command listen to icmp reponse without libpcap ?

12 years

3
5
0 0

Subscription Confirm

by Isaac Wilder

Can whoever has list duty approve the sub request for Charles? imw

12 years

3
2
0 0

Batman-adv bla II backbone

by Gioacchino Mazzurco

I have talked today with antonio (ordex) and really what they call backbon is not the common sense of backbone, so we should add a vlan on top of ethernet interfaces where client are accepted too if we want batman-adv to route traffic accross ethernet too

12 years

1
0
0 0

Fwd: News in libremesh

by Gioacchino Mazzurco

Is p4u receiving mail from the mailing list or there is some problem ? ---------- Forwarded Message ---------- Subject: News in libremesh Date: Wednesday 15 May 2013, 00:06:01 From: Pau <hakais(a)gmail.com> To: NicoEchániz <nicoechaniz(a)altermundi.net>, Gioacchino Mazzurco <gio(a)eigenlab.org>, Gui Iribarren <gui(a)altermundi.net> Hi. We are currently using the the repositories created in github. I see Gio added the package for cracking the ath9k regdomain. I added a dummy package named lime-system with some basic dependences. If you clone the repository lime-build and type "make T=tl-703n J=2", it should compile the system with the lime-system enabled and the dependences. For the moment only the targets tl-703n and tl-wdr4300 are supported, but it is just a mather of adding the config files in the configs/directory To create them execute - make T=NEW_TARGET menuconfig - find the resulting config file in build/configs/NEW_TARGET - diffconfig it with build/ar71xx/scripts/diffconfig (yes, it should be added to the Makefile to do it automatically, please volunteeers!!) - save it to configs/NEW_TARGET Following this approach we can have kind of useful diferent profiles for each target. So, some software can fit in devices such as wdr4300 and not in 703n. I also have been thinking about the network architecture modes (NAM). I think we should implement some of them and let the administrator choose (can be different for each community). - bmx6 + bat-adv in all nodes - bat-adv in all nodes and bmx6 in the borders (autoloaded) - bat-adv in all nodes and bmx6 only in the nodes designed by the administrator [1] https://github.com/libre-mesh PS: Do we have mailing list? -- ./p4u -----------------------------------------

12 years

1
0
0 0

Terra

by Isaac Wilder

Just came across terra: http://terralang.org/ Looks like it could be a really nice fit in certain places. imw

12 years

1
0
0 0

[Dev] we have a list

by NicoEchániz

Hi everyone, We just created the mailing list. The subscribers so far are: pau, gui, nico, gioacchino, axel and isaac. cheers, Nico

12 years

4
4
0 0

[Dev] roadmap / issues

by NicoEchániz

Amici, I converted Pau's Roadmap wiki entry into individual issues, so we can have more complete information on each task: what is expected, who will be in charge, etc. I marked all issues with lime-alpha as target version just to have them grouped. It's here: http://dev.libre-mesh.org/projects/libre-mesh/issues And I updated the link in the wiki to point there. If we are all ok, we can delete the Roadmap wiki page and keep using the issue system for future tasks. Cheers! Nico

12 years

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

lime-dev