Today has started the midterm evaluation, the deadline Is next Monday, so I have to show the work I have done ‘till now. It can be resumed in the following parts:
1) Refactoring of graph-parser and C Bindings
During the community bonding period I started working on the code of Quynh Nguyen’s M.Sc. Thesis. She wrote a C++ program capable of calculating the BC of every node of a topology . I re-factored the code, and now it is a C/C++ shared Library . I’ve also applied some OOP principles (Single responsibility and inheritance) and unit tests to make it more maintainable.
The interface of the library Is well defined and it can be re-used to implement another library to perform the same tasks (parsing the json and calculating the BC).
2)Prince Basic functionalities
After I completed the library a started working on the main part of the project. the daemon. We decided to call it Prince in memory of the Popstar.
This daemon connect to the routing protocol using the specific plugin (see below), calculate the BC using graph-parser, computes the timers and then it push them back using again the specific plugin. With this architecture it can be used with any routing protocol.I wrote the specific plugin for OONF and OLSRd. At the moment it has been tested with both, but I need to write a plugin for OLSRd to change the timers at runtime. For OONF I used the RemoteControl Plugin.
With these feature Prince is capable of pulling the topology, calculate the BC and Timers and push them back to the routing protocol daemon.
3) Additional Features: Configuration file, Dynamic plugins,
I wrote a very simple reader for a configuration file. Using the configuration file the user can specify: routing protocol host and port, routing protocol (olsr/oonf), heuristic, (un)weighted graphs.
As you can see from this Issue , I’m going to use INI instead of this home-made format.
As I said before I moved to a specific plugin all the protocol specific methods (pulling the topology and pushing the timers), to keep the daemon light I decided to load this plugin dynamically at runtime. So if you specify “olsr” in the configuration file just the OLSRd specific plugin will be loaded.
At the moment I consider this an “alpha” version of Prince. In the next 2 months I’ll be working on it to make it stable and well tested. The next steps will be:
I am Gabriele from the Ninux community. I am participating in GSoC 2016 for the first time and I am very glad I have been accepted as a Student for Freifunk. I am from Florence, Italy. Here I’m studying Computer Science, soon I will graduate and I hope to use the results of this project to write my bachelor thesis.
Four years ago, with others community networks’ enthusiasts we have funded Ninux Firenze, the fist Wireless Community Network in Florence where I had the chance to learn how these networks work and to meet many others people interested in this field. The network is constantly growing, and now it counts almost 20 nodes. In May ’14 I have been for the first time to Wireless Battle of the Mesh in Leipzig where I met the Freifunk community. For this GSoC I will work on a project called PopRouting:
OONF (OLSRv2) is a link state routing protocol. It works sending periodical messages to his neighbors with the aim of transmitting information about topology changes. With these information each node of the network is able to calculate the paths to reach any other destination. These messages are periodically generated, based on the configuration parameter that regulates the sending interval. A short period will make the network react rapidly but it will also cause a large overhead due to control messages. Pop Routing is a recent technique that takes advantage of the knowledge of the network topology to find the optimal value for the OONF’s timers. Using Pop Routing every node computes the “betweenness centrality” of every other node and uses it to calculate the optimal trade-off between convergence and overhead for its timers. The algorithm has been developed at the UniTN and the algorithm to compute the BC in C++ is available as free software. My goal is to code a daemon (in C) that is able to calculate autonomously the BC of the network and push it to OONF using the telnet plugin.
In this month of community bonding I have been to Wireless Battle of the Mesh v9 in Oporto(PT). There I met the OONF developers and we discussed how to implement this inside OONF. I also gave a presentation on the project. After the Battlemesh I started working on the algorithm developed by UniTN and I made a C/C++ library out of it .
Today I will start coding for the GSoC, stay tuned and I will give you more updates soon.
Freifunk attendees had the chance to discuss Community Networks with Linus Torvalds and Dirk Hohndel from Intel at the Google Mentor Summit. Linus said, it was impressive to see the growth of community networks around the world and it is exciting to see so many people working on Linux for embedded devices.
Hi everyone, I'm Alessandro Bucciarelli and I am participating for the first time to Google Summer of Code.
I chose to apply to work on Netengine, a project by Freifunk/Ninux. Netengine is a Python abstraction layer thought to retrieve informations about network configurations, and not only, from multiple couples of network protocols/device firmware.
Actually the main network protocols we are working on are: SNMP, SSH; with HTTP which is an idea for the immediate future.
By the firmware side there are AirOS and OpenWRT which are the most used firmwares among network devices (antennas and other) deployed inside the Ninux network.
Many of the readers, if experienced in the network field, will agree with me in saying that the retrieval of network informations (e.g IP addresses of the interface/s, MAC addresses, routing configurations) is vital.
This aspect is more than vital when you are interacting with remote devices, geographically widespread and sometimes accessible by only unskilled persons, to have a timely diagnostics of the deployed hardware.
The module we are developing tries to solve, and I am sure it will be so, the problem of having informations from the devices REMOTELY, without any kind of further configurations and without any kind of physical interaction with the device.
Wie lebensrettend offene Infrastrukturen sein können, zeigt sich vor allem in Katastrophenszenarien, wie zum Beispiel momentan im Erdbebengebiet in Norditalien. Jetzt berichtet auch Spiegel Online über einen Aufruf der Behörden an die Bürger ihren WLAN-Zugang zum Internet zu öffnen, um die Kommunikation von Rettungskräften zu erleichtern.
Italiens Norden wird von Erdbeben erschüttert, die Rettungskräfte arbeiten pausenlos. Die Kommunikation ist schwierig, weil Telefon- und Handynetze teilweise zusammengebrochen sind. Nun rufen Städte und Gemeinden der betroffenen Region die Bürger auf, ihre heimischen W-Lan-Anschlüsse in freie Hotspots zu verwandeln und dafür den Passwortschutz kurzfristig aufzuheben. (http://www.spiegel.de/netzwelt/web/....)
Auf Republicca können die Italiener nun nachlesen, wie der Zugang geöffnet wird:
PER CONSENTIRE a tutti coloro che non riescono a comunicare via cellulare di collegarsi ad internet, molti comuni invitano i cittadini dei paesi colpiti dal terremoto di oggi ad aprire la propria rete wi-fi domestica. (http://www.repubblica.it/cronaca/2012/05/29/news/i...)
Der Kommentar von Reto Mantz dazu:
Der Fall wirft ein deutliches Schlaglicht auf die Relevanz des Zugangs zum Internet und allgemein des Zugangs zu Kommunikationssystemen. Und letztlich ist dieser Punkt auch in rechtlicher Hinsicht beachtlich: Wenn eine Kommunikationsstruktur zur Begehung von Rechtsverletzungen genutzt wird, greift potentiell das deutsche Konstrukt der Störerhaftung: Der Anschlussinhaber soll als Mitwirkender an der Rechtsverletzung des (möglicherweise unbekannten) Dritten wenigstens auf zukünftige Unterlassung haften. Nun zeigt das Beispiel der italienischen Städte und Gemeinden, dass ein offenes WLAN nicht Gefahrenquelle ist ..., sondern eine wichtige gesellschaftliche Funktion erfüllt. ... Auch wenn der Aufruf der italienischen Städte nur der vorübergehenden Öffnung von WLANs dienen soll, zeigt er doch, wie wichtig heutzutage der freie Zugang zu Kommunikationsstruktur ist, nicht nur zur Überbrückung des sog. Digital Divide. (http://www.retosphere.de/offenenetze/2012/06/02/funktion-und-bedeutung-des-wlan-acess...)
Zu hoffen bleibt, dass die Erkenntnis, wie wichtig und lebensrettend offene Netze sein können sich auch längerfristig in Italien durchsetzt. Bei vielen Bürgern ist dies bereits vor Langem angekommen. Die Bürgernetze von Ninux.org in Italien wachsen beständig. Wann wird sich diese Erkenntniss auch in der Politik in Deutschland durchsetzen und wann werden die gesetzlichen Beschränkungen und Abmahnfallen für Betreiber freier Netze endlich abgebaut?
Freifunk.net and Ninux.org have been accepted as mentor organizations for the Google Summer of Code 2012. It is fantastic news that the growing international free networks community is now represented by two organizations in the study program.
If you are looking for more information on how to participate get in touch with your local wireless community or introduce your ideas on the wiki or Wlanware mailing list. People on the list will direct you to specific subprojects and contact points if needed.
Freifunk.net is an umbrella organization for wlan networks and community projects around the world and welcomes student applications for software tools to build and enhance free networks including:
* projects for routing protocols like OLSR, B.A.T.M.A.N. or other freely licensed protocols
* firmwares for routers and software for network devices
* software for network specific content creation like network CMS'
* any other network related software project
If you are a student there are important links to follow:
* Idea Page: http://wiki.freifunk.net/Ideas
* Student Check List: http://wiki.freifunk.net/Student_Check_List
* Mailing List http://freifunk.net/mailman/listinfo/wlanware
* Freifunk GSoC Page http://www.google-melange.com/gsoc/org/show/google/gsoc2012/freifunk
* Google Open Source Programs: http://socghop.appspot.com
There is an info day on March 15 in Rome. You can also meet many contributors to the community at the battle of the mesh in Athens from March 26-April 1: http://battlemesh.org/BattleMeshV5
The next 'Wireless Battle of the Mesh' will take place from Wed 2nd till Sun 6th of June in Bracciano (near Rome), Italy. The event aims to bring together people from across Europe to test the performance of different routing protocols for ad-hoc networks, like Babel, B.A.T.M.A.N., and OLSR. This third WBM will be improving the testbed conditions for mesh protocols with standardized testing procedures that will be reported after the event for the wireless communities.
On the development side, a flashing tool will be presented to simplify the deployment of such wireless networks based on OpenWrt stable release and packages for each protocol.
If you are a mesh networking enthusiast, community networking activist, or have an interest in mesh networks you have to check this out!
The Wireless Battle of the Mesh is an event that aims at bringing together people from across Europe to test the performance of different routing protocols for ad-hoc networks, like Babel, B.A.T.M.A.N., OLSR, 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).