11810
Comment: Added nodewatcher.
|
15593
added link to netjson slides
|
Deletions are marked like this. | Additions are marked like this. |
Line 11: | Line 11: |
|| 20:00 - 21:00 || WiBed, a testbed platform for WiFi experiments|| Wibed is a platform for facilitating the quick and cost-efficient acquisition, deployment, and management of testbeds based on commodity IEEE802.11 routers and enabling experimentation with wireless technology including the modification of low-level system components such as physical and link layer mechanisms, and network and transport layer protocols. WiBed was used, with partial (:-P) success in WBMv7 as the experiment firmware. || talk || Mano || || | || 20:00 - 21:00 || WiBed, a testbed platform for WiFi experiments|| Wibed is a platform for facilitating the quick and cost-efficient acquisition, deployment, and management of testbeds based on commodity IEEE802.11 routers and enabling experimentation with wireless technology including the modification of low-level system components such as physical and link layer mechanisms, and network and transport layer protocols. WiBed was used, with partial (:-P) success in WBMv7 as the experiment firmware. || talk || Manos, Igor || [[attachment:wibed.pdf]] || |
Line 16: | Line 16: |
|| 14:00 - 15:00 || babel does not care || Babel is a robust routing protocol that just doesn't care. While initially designed to be reasonably robust and efficient on both wireless mesh networks and classical wired networks, over the years Babel has been extended with delay-based routing for overlay networks, with radio-interference aware routing, and even with source-specific routing. Whatever you throw at it, Babel doesn't care, it just keeps pushing packets in the right direction.<<BR>>The talk will be elementary, and require little networking background. || talk || Juliusz || || | || 14:00 - 15:00 || babel does not care || Babel is a robust routing protocol that just doesn't care. While initially designed to be reasonably robust and efficient on both wireless mesh networks and classical wired networks, over the years Babel has been extended with delay-based routing for overlay networks, with radio-interference aware routing, and even with source-specific routing. Whatever you throw at it, Babel doesn't care, it just keeps pushing packets in the right direction.<<BR>>The talk will be elementary, and require little networking background. || talk || Juliusz || [[attachment:babel-20150804.pdf]] || |
Line 20: | Line 20: |
|| 18:00 - 19:00 || mesh in TV-whitespace || Presenting the TV-Whitespace experiment of Freifunk. The development of the equipment we use. Properties of the frequency band and ideas about the future use of the UHF. || talk || elektra || || || 19:00 - 20:00 || [[http://koruza.net|KORUZA ]]- wireless optical system (beta presentation) || || talk || Musti || || |
|| 18:00 - 19:00 || mesh in TV-whitespace || Presenting the TV-Whitespace experiment of Freifunk. The development of the equipment we use. Properties of the frequency band and ideas about the future use of the UHF. || talk || elektra || [[attachment:Freifunk-in-TV-Whitespace.odp]] || || 19:00 - 20:00 || [[http://koruza.net|KORUZA ]]- wireless optical system (beta presentation) || || talk || Musti || [[attachment:Battlemesh-2015-Koruza.pdf]] || |
Line 26: | Line 26: |
|| 13:00 - 14:00 || source specific routing in babel || multihoming is a difficult problem, and, unsurprisingly enough, there are many techniques for multihoming, none of which are applicable in all cases. The mesh networking community has standardised on using tunnels for multihoming (as with the "smart gateway" OLSR plugin). The home networking community has chosen a different solution, called "source-specific routing.".<<BR>>The first complete implementation of source-specific routing was done by Matthieu Boutier and Juliusz Chroboczek, and was implemented within the Babel routing protocol. In this talk, I will explain what are the difficulties with multihoming, explain how source-specific routing solves many of those difficulties, and give an outline of Babel's support for source-specific routing.<<BR>>References: http://arxiv.org/pdf/1403.0445 || talk || Matthieu Boutier || || | || 13:00 - 14:00 || source specific routing in babel || multihoming is a difficult problem, and, unsurprisingly enough, there are many techniques for multihoming, none of which are applicable in all cases. The mesh networking community has standardised on using tunnels for multihoming (as with the "smart gateway" OLSR plugin). The home networking community has chosen a different solution, called "source-specific routing.".<<BR>>The first complete implementation of source-specific routing was done by Matthieu Boutier and Juliusz Chroboczek, and was implemented within the Babel routing protocol. In this talk, I will explain what are the difficulties with multihoming, explain how source-specific routing solves many of those difficulties, and give an outline of Babel's support for source-specific routing.<<BR>>References: http://arxiv.org/pdf/1403.0445 || talk || Matthieu Boutier || [[attachment:2015-08-Battlemesh.pdf]] || |
Line 32: | Line 32: |
|| 20:00 - 24:00|| Party at [[https://tgas2014.wordpress.com/gt22/ | GT22]] || Tour of the GT22, bar with beer and entertainment by ''Dj Splinta 639'' and ''Vj Sajko'' || social || - || - || https://tgas2014.wordpress.com/gt22/ |
|| 20:00 - 24:00|| Party at [[https://tgas2014.wordpress.com/gt22/ | GT22]] || Tour of the GT22, bar with beer and entertainment by ''Dj Splinta 639'' and ''Vj Sajko'' || social || - || https://tgas2014.wordpress.com/gt22/ || |
Line 39: | Line 37: |
|| 14:00 - 14:30 || Cake || Comprehensive Queue Management Made Easy || talk || Jonathan || - || || 14:30 - 15:00 || addressing insecurity in internet of thing devices - a 5 year plan || || talk ||dave / jim || || || 15:00 - 16:00 || openWRT vs. FCC - forced firmware lockdown? || The new FCC rules are in effect in the United States from June 2nd 2015 [1] for WiFi devices such as Access Points. They require to have the firmware locked down so End-Users can't operate with non-compliant parameters (channels/frequencies, transmit power, DFS, ...). In response, WiFi access point vendors start to lock down firmwares to prevent custom firmwares (such as OpenWRT) to be installed, using code signing, etc. Since the same type of devices are often sold world wide, this change does not only affect routers in the US, but also Europe, and this will also effect wireless communities.<<BR>>We would like to discuss:<<BR>>* What are your experiences with recently certified WiFi Hardware<<BR>>* How can we still keep OpenWRT on these devices<<BR>>* What can we suggest to Hardware vendors so that they keep their firmware open for community projects while still compliant with the FCC?<<BR>>[1] https://apps.fcc.gov/oetcf/kdb/forms/FTSSearchResultPage.cfm?id=39498&switch=P || discussion || Simon Wunderlich || || |
|| 14:00 - 14:30 || Cake || Comprehensive Queue Management Made Easy - fq_codel is now widely deployed, and achieving vast reductions in network latency with load, primarily in QoS systems. Cake leverages the algorithms developed in fq_codel, is faster, uses less memory, and has fewer hash collisions. Work on cake is feeding back into the make-wifi-fast effort, as we also attempt to improve wifi behaviors under a wide range of conditions. || talk || Jonathan || [[attachment:cake-battlemesh-v8.pdf]] || || 14:30 - 15:00 || Why the Insecurities? || The state of security of all edge devices, and in particular, the tiny internet of things devices, is terrible. This short talk, goes into the cross layer issues at all 11 layers of the ISO network statck. || talk ||dave / jim || [[attachment:battlemesh-security.pdf]] || || 15:00 - 16:00 || openWRT vs. FCC - forced firmware lockdown? || The new FCC rules are in effect in the United States from June 2nd 2015 [1] for WiFi devices such as Access Points. They require to have the firmware locked down so End-Users can't operate with non-compliant parameters (channels/frequencies, transmit power, DFS, ...). In response, WiFi access point vendors start to lock down firmwares to prevent custom firmwares (such as OpenWRT) to be installed, using code signing, etc. Since the same type of devices are often sold world wide, this change does not only affect routers in the US, but also Europe, and this will also effect wireless communities.<<BR>>We would like to discuss:<<BR>>* What are your experiences with recently certified WiFi Hardware<<BR>>* How can we still keep OpenWRT on these devices<<BR>>* What can we suggest to Hardware vendors so that they keep their firmware open for community projects while still compliant with the FCC?<<BR>>[1] https://apps.fcc.gov/oetcf/kdb/forms/FTSSearchResultPage.cfm?id=39498&switch=P || discussion || Simon Wunderlich || [[attachment:2015-08-06_wbmv8_FCC.pdf]] ; Etherpad: http://tinyurl.com/WBMFCC || |
Line 43: | Line 41: |
|| 17:30 - 18:00 || Preliminary Experiments with MultiPath TCP VPNs || Multipath TCP "aims at allowing a Transmission Control Protocol (TCP) connection to use multiple paths to maximize resource usage and increase redundancy" [source: wikipedia]. This talk reports some preliminary experiences about using VPNs on top of Multipath TCP. || talk || clauz || || || 18:00 - 19:00 || nmap security scanner || Presenting Nmap and how it can be used to investigate the security of our mesh networks, starting from basic usage, continuing explaining how to extend NSE (Nmap Scripting Engine) and finally giving an overview of the work I have done on Nmap during GSoC 2015 as student.|| talk || g10h4ck || || || 19:00 - 20:00 || [[http://www.ligowave.com/ | LigoWave ]]|| Talk about LigoDLB devices|| talk || Ligowave || || |
|| 17:30 - 18:00 || Preliminary Experiments with MultiPath TCP VPNs || Multipath TCP "aims at allowing a Transmission Control Protocol (TCP) connection to use multiple paths to maximize resource usage and increase redundancy" [source: wikipedia]. This talk reports some preliminary experiences about using VPNs on top of Multipath TCP. || talk || clauz || [[attachment:mptcpvpns.pdf]] || || 18:00 - 19:00 || [[http://www.ligowave.com/ | LigoWave ]]|| Talk about LigoDLB devices|| talk || Ligowave || || || 19:00 - 20:00 || nmap security scanner || Presenting Nmap and how it can be used to investigate the security of our mesh networks, starting from basic usage, continuing explaining how to extend NSE (Nmap Scripting Engine) and finally giving an overview of the work I have done on Nmap during GSoC 2015 as student.|| talk || g10h4ck || cancelled || || 19:00 - 19:15 || News from the IETF Homenet WG || Homenet is an IETF working group that defines the architecture of future home routers. Homenet has a full implementation, based on OpenWRT and Babel. In this short talk, I will describe why the Homenet standardisation process is stuck. || talk || Juliusz Chroboczek || || || 19:15 - 19:30 || A UDP-based multipath application: mpmosh || Multihomed networks with source-specific routing gives new opportunities for the design of multipath transport or application layer protocols. Such a transport protocol is Multipath TCP: a compatible multipath replacement for TCP. However, some applications takes benefit to use UDP instead of TCP, and would not be improved by MPTCP.<<BR>> Mosh is a lightweight interactive application built over UDP, which reacts well in most situations. However, in some multihomed situations, it has some flaws which could be solved by considering multiple paths. In this talk, I will speak about my multipath version of mosh, that we will call mpmosh.<<BR>> The source code is available at: https://github.com/boutier/mosh .<<BR>> And a (to-be-updated) paper at: http://arxiv.org/abs/1502.02402. || talk || Matthieu Boutier || [[attachment:2015-08-BM8-mosh.pdf]] || || 19:30 - 19:45 || Efficient Scientific Research || In this talk I address the typical hurdles of researchers organizing the body of literature they read and keep. Efficient researchers find ways to automate these boring tasks. Consequently, I present a utility belt of handy tools and scripts to automate the typical tasks. || talk || Thomas || [[https://github.com/Eden-06/gsresearch/blob/master/presentation.pdf]] || |
Line 50: | Line 52: |
|| 14:00 - 15:00 || project idea of „echt dezentrales Netz“ (EDN) || https://wiki.c3d2.de/Echt_Dezentrales_Netz/en || talk || demos || || || 15:00 - 15:20 || NetJSON || [[http://netjson.org|NetJSON]] is a data interchange format based on JavaScript Object Notation (JSON) designed to describe the basic building blocks of layer2 and layer3 networking. It defines several types of JSON objects and the manner in which they are combined to represent a network: configuration of devices, monitoring data, network topology and routing information. In this talk I'll introduce the basic concepts, motivations and goals. There will be some time left for questions and discussion. || talk and discussion || Nemesis || || || 15:20 - 16:00 || How different nodeDB projects can start joining forces on specific modules/packages || A few years ago we had a discussion about joining forces on a Common NodeDB project which didn't go well. After years of development we still don't have what we all hoped for, mainly because our efforts are disconnected and incostant. How we can remediate? NetJSON could be a step in the right direction, but I also want to talk about the work we have been doing in [[http://nodeshot.org|Nodeshot]] to extract key features in separate python packages and which benefits this has brought to us. || talk || Nemesis || || |
|| 14:00 - 15:00 || project idea of „Echt dezentrales Netz“ (EDN) || https://wiki.c3d2.de/Echt_Dezentrales_Netz/en || talk || Demos ||[[attachment:EDN_praesentation]] || || 15:00 - 15:20 || NetJSON || [[http://netjson.org|NetJSON]] is a data interchange format based on JavaScript Object Notation (JSON) designed to describe the basic building blocks of layer2 and layer3 networking. It defines several types of JSON objects and the manner in which they are combined to represent a network: configuration of devices, monitoring data, network topology and routing information. In this talk I'll introduce the basic concepts, motivations and goals. There will be some time left for questions and discussion. || talk and discussion || Nemesis || [[attachment:battlemesh-netjson.pdf]] || || 15:20 - 16:00 || How different nodeDB projects can start joining forces on specific modules/packages || A few years ago we had a discussion about joining forces on a Common NodeDB project which didn't go well. After years of development we still don't have what we all hoped for, mainly because our efforts are disconnected and inconstant. How we can remediate? NetJSON could be a step in the right direction, but I also want to talk about the work we have been doing in [[http://nodeshot.org|Nodeshot]] to extract key features in separate python packages and which benefits this has brought to us. || talk || Nemesis || [[attachment:battlemesh-netjson.pdf]] || |
Line 54: | Line 56: |
|| 17:00 - 17:45 || Crust - reliable p2p network connections in Rust || Crust, a library built by MaidSafe, ensures reliable connections to any p2p network including the SAFE Network. In this presentation, MaidSafe founder David Irvine will present the functions of the library and design considerations for mesh network integration.<<BR>>URL: https://github.com/maidsafe/crust|| talk || david + paige || || | || 17:00 - 17:45 || MaidSafe, a secure & serverless Internet || MaidSafe is secure platform for decentralised storage and communications. Paige will overview the technology, its stack (including the Crust library built for reliable p2p network connections) and design considerations for mesh network integration. The founder David Irvine will join over a voice call for questions and discussion. <<BR>>URL: https://github.com/maidsafe|| talk || Paige + David || [[attachment:MaidSafe_BattleMeshV8.pdf]] || |
Line 56: | Line 58: |
|| 19:00 - 20:00 || battlemesh community meeting || The good and bad things this year. Searching a place for next year || discussion || - || || | || 19:00 - 19:15 || alexandria || An open-source distributed library for sharing and preserving art, history and culture. Users can self-publish anything, including videos, music, books, 3D-printables, recipes, and more, without centralized servers. Content creators have complete control over how their work is published with several different monetization options. Only the publisher has the power to remove her/his content from the library. <<BR>>URL: http://blocktech.com || lightening talk || ryan || || || 19:15 - 20:00 || battlemesh community meeting || The good and bad things this year. Searching a place for next year || discussion || - || || || 20:00 - 21:00 || community networks roundtable || as discussed on the mailing list || open discussion || - || - || |
Line 58: | Line 62: |
Line 61: | Line 66: |
|| 13:00 - 14:00 || nmap security scanner || Presenting Nmap and how it can be used to investigate the security of our mesh networks, starting from basic usage, continuing explaining how to extend NSE (Nmap Scripting Engine) and finally giving an overview of the work I have done on Nmap during GSoC 2015 as student. || talk ||g10h4ck || || | |
Line 63: | Line 69: |
|| 16:00 - 17:00 || presenting the battle results || what are the test results? || talk || - || || || afternoon || BBQ & beer || - || social || - || - || |
|| 16:00 - 18:00|| BBQ & beer || - || social || - || - || || 19:00 - 20:00 || presenting the battle results || what are the test results? || talk || - || || |
Agenda
Contents
The venue is opened from 9:00 am every day until 1.00 am. During that time collaborative work between participants is going on.
Monday 3th August 2015
Time |
Title |
Abstract |
Type |
Speaker |
Slides & Documentation |
9:00 - |
collaborative work between participants |
- |
- |
- |
- |
19:00 - 20:00 |
inofficial welcome |
- |
social |
- |
- |
20:00 - 21:00 |
Wibed is a platform for facilitating the quick and cost-efficient acquisition, deployment, and management of testbeds based on commodity IEEE802.11 routers and enabling experimentation with wireless technology including the modification of low-level system components such as physical and link layer mechanisms, and network and transport layer protocols. WiBed was used, with partial (:-P) success in WBMv7 as the experiment firmware. |
talk |
Manos, Igor |
Tuesday 4th August 2015
Time |
Title |
Abstract |
Type |
Speaker |
Slides & Documentation |
9:00 - |
collaborative work between participants |
- |
- |
- |
- |
14:00 - 15:00 |
babel does not care |
Babel is a robust routing protocol that just doesn't care. While initially designed to be reasonably robust and efficient on both wireless mesh networks and classical wired networks, over the years Babel has been extended with delay-based routing for overlay networks, with radio-interference aware routing, and even with source-specific routing. Whatever you throw at it, Babel doesn't care, it just keeps pushing packets in the right direction. |
talk |
Juliusz |
|
15:00 - 16:00 |
collaborative work between participants |
- |
- |
- |
- |
16:00 - 17:00 |
lunch |
- |
social |
- |
- |
17:00 - 18:00 |
GNUnet in community mesh networks |
While originally meant to be used a framework for anonymous file-sharing, GNUnet has a lot to offer for wireless community networks as well: a truly distributed solution for name resolution, VPN tunnels and NAT traversal, to name just a few low-hangig fruits |
talk |
dango |
|
18:00 - 19:00 |
mesh in TV-whitespace |
Presenting the TV-Whitespace experiment of Freifunk. The development of the equipment we use. Properties of the frequency band and ideas about the future use of the UHF. |
talk |
elektra |
|
19:00 - 20:00 |
KORUZA- wireless optical system (beta presentation) |
|
talk |
Musti |
Wednesday 5th August 2015
Time |
Title |
Abstract |
Type |
Speaker |
Slides & Documentation |
9:00 - |
collaborative work between participants |
- |
- |
- |
- |
13:00 - 14:00 |
source specific routing in babel |
multihoming is a difficult problem, and, unsurprisingly enough, there are many techniques for multihoming, none of which are applicable in all cases. The mesh networking community has standardised on using tunnels for multihoming (as with the "smart gateway" OLSR plugin). The home networking community has chosen a different solution, called "source-specific routing.". |
talk |
Matthieu Boutier |
|
14:00 - 15:00 |
peer to peer IPv6 networking in cjdns |
Cjdns builds end-to-end encrypted, peer-to-peer IPv6 networks with useful properties -- the biggest so far being Hyperboria. We'll give a brief introduction to cjdns, its goals, and design decisions. We'll also show a few interesting use cases, and what the Hyperboria community is up to. |
talk |
ansuz & Lars |
|
15:00 - 16:00 |
redistributing the web with IPFS |
IPFS is a global, versioned, peer-to-peer filesystem. It combines good ideas from Git, BitTorrent, Kademlia, SFS, and the Web. It is like a single BitTorrent swarm, exchanging Git objects. IPFS provides an interface as simple as the HTTP web, but with permanence built in. I'll give a brief introduction to IPFS, then show its potential use in mesh networks, for example as a distributed content cache. |
talk |
juan |
|
16:00 - 17:00 |
lunch |
- |
social |
- |
- |
17:30 |
organized transport to city center |
- |
social |
- |
- |
18:00 |
Tour of Tkalka and KreatorLab |
Find out more about |
social |
- |
- |
20:00 - 24:00 |
Party at GT22 |
Tour of the GT22, bar with beer and entertainment by Dj Splinta 639 and Vj Sajko |
social |
- |
Thursday 6th August 2015
Time |
Title |
Abstract |
Type |
Speaker |
Slides & Documentation |
9:00 - |
collaborative work between participants |
- |
- |
- |
- |
14:00 - 14:30 |
Cake |
Comprehensive Queue Management Made Easy - fq_codel is now widely deployed, and achieving vast reductions in network latency with load, primarily in QoS systems. Cake leverages the algorithms developed in fq_codel, is faster, uses less memory, and has fewer hash collisions. Work on cake is feeding back into the make-wifi-fast effort, as we also attempt to improve wifi behaviors under a wide range of conditions. |
talk |
Jonathan |
|
14:30 - 15:00 |
Why the Insecurities? |
The state of security of all edge devices, and in particular, the tiny internet of things devices, is terrible. This short talk, goes into the cross layer issues at all 11 layers of the ISO network statck. |
talk |
dave / jim |
|
15:00 - 16:00 |
openWRT vs. FCC - forced firmware lockdown? |
The new FCC rules are in effect in the United States from June 2nd 2015 [1] for WiFi devices such as Access Points. They require to have the firmware locked down so End-Users can't operate with non-compliant parameters (channels/frequencies, transmit power, DFS, ...). In response, WiFi access point vendors start to lock down firmwares to prevent custom firmwares (such as OpenWRT) to be installed, using code signing, etc. Since the same type of devices are often sold world wide, this change does not only affect routers in the US, but also Europe, and this will also effect wireless communities. |
discussion |
Simon Wunderlich |
2015-08-06_wbmv8_FCC.pdf ; Etherpad: http://tinyurl.com/WBMFCC |
16:00 - 17:30 |
lunch |
- |
social |
- |
- |
17:30 - 18:00 |
Preliminary Experiments with MultiPath TCP VPNs |
Multipath TCP "aims at allowing a Transmission Control Protocol (TCP) connection to use multiple paths to maximize resource usage and increase redundancy" [source: wikipedia]. This talk reports some preliminary experiences about using VPNs on top of Multipath TCP. |
talk |
clauz |
|
18:00 - 19:00 |
Talk about LigoDLB devices |
talk |
Ligowave |
|
|
19:00 - 20:00 |
nmap security scanner |
Presenting Nmap and how it can be used to investigate the security of our mesh networks, starting from basic usage, continuing explaining how to extend NSE (Nmap Scripting Engine) and finally giving an overview of the work I have done on Nmap during GSoC 2015 as student. |
talk |
g10h4ck |
cancelled |
19:00 - 19:15 |
News from the IETF Homenet WG |
Homenet is an IETF working group that defines the architecture of future home routers. Homenet has a full implementation, based on OpenWRT and Babel. In this short talk, I will describe why the Homenet standardisation process is stuck. |
talk |
Juliusz Chroboczek |
|
19:15 - 19:30 |
A UDP-based multipath application: mpmosh |
Multihomed networks with source-specific routing gives new opportunities for the design of multipath transport or application layer protocols. Such a transport protocol is Multipath TCP: a compatible multipath replacement for TCP. However, some applications takes benefit to use UDP instead of TCP, and would not be improved by MPTCP. |
talk |
Matthieu Boutier |
|
19:30 - 19:45 |
Efficient Scientific Research |
In this talk I address the typical hurdles of researchers organizing the body of literature they read and keep. Efficient researchers find ways to automate these boring tasks. Consequently, I present a utility belt of handy tools and scripts to automate the typical tasks. |
talk |
Thomas |
https://github.com/Eden-06/gsresearch/blob/master/presentation.pdf |
Friday 7th August 2015
Time |
Title |
Abstract |
Type |
Speaker |
Slides & Documentation |
9:00 - |
collaborative work between participants |
- |
- |
- |
- |
14:00 - 15:00 |
project idea of „Echt dezentrales Netz“ (EDN) |
talk |
Demos |
||
15:00 - 15:20 |
NetJSON |
NetJSON is a data interchange format based on JavaScript Object Notation (JSON) designed to describe the basic building blocks of layer2 and layer3 networking. It defines several types of JSON objects and the manner in which they are combined to represent a network: configuration of devices, monitoring data, network topology and routing information. In this talk I'll introduce the basic concepts, motivations and goals. There will be some time left for questions and discussion. |
talk and discussion |
Nemesis |
|
15:20 - 16:00 |
How different nodeDB projects can start joining forces on specific modules/packages |
A few years ago we had a discussion about joining forces on a Common NodeDB project which didn't go well. After years of development we still don't have what we all hoped for, mainly because our efforts are disconnected and inconstant. How we can remediate? NetJSON could be a step in the right direction, but I also want to talk about the work we have been doing in Nodeshot to extract key features in separate python packages and which benefits this has brought to us. |
talk |
Nemesis |
|
16:00 - 17:00 |
lunch |
- |
social |
- |
- |
17:00 - 17:45 |
MaidSafe, a secure & serverless Internet |
MaidSafe is secure platform for decentralised storage and communications. Paige will overview the technology, its stack (including the Crust library built for reliable p2p network connections) and design considerations for mesh network integration. The founder David Irvine will join over a voice call for questions and discussion. |
talk |
Paige + David |
|
18:00 - 19:00 |
nodewatcher 3.0 release |
nodewatcher, version 3.0, will hopefully be released during this talk. Nodewatcher is an open source network planning, deployment, monitoring and maintenance platform with emphasis on community. Version 3.0 is a complete rewrite bringing modularity and extensibility. |
talk |
Mitar, Kostko |
|
19:00 - 19:15 |
alexandria |
An open-source distributed library for sharing and preserving art, history and culture. Users can self-publish anything, including videos, music, books, 3D-printables, recipes, and more, without centralized servers. Content creators have complete control over how their work is published with several different monetization options. Only the publisher has the power to remove her/his content from the library. |
lightening talk |
ryan |
|
19:15 - 20:00 |
battlemesh community meeting |
The good and bad things this year. Searching a place for next year |
discussion |
- |
|
20:00 - 21:00 |
community networks roundtable |
as discussed on the mailing list |
open discussion |
- |
- |
Saturday 8th August 2015
Time |
Title |
Abstract |
Type |
Speaker |
Slides & Documentation |
9:00 - |
collaborative work between participants |
- |
- |
- |
- |
13:00 - 14:00 |
nmap security scanner |
Presenting Nmap and how it can be used to investigate the security of our mesh networks, starting from basic usage, continuing explaining how to extend NSE (Nmap Scripting Engine) and finally giving an overview of the work I have done on Nmap during GSoC 2015 as student. |
talk |
g10h4ck |
|
14:00 - 15:00 |
i18n for the Freifunk API |
The Freifunk API is a collection of tools to get information from communities. The API files are hosted by the community itself. Let us show you our latest features and let's evolve an international version of it. |
workshop |
andi + monic |
|
15:00 - 16:00 |
make wifi fast |
This will go into all the techniques we think can go into wifi to make it feel faster under more circumstances, that I have described in various talks, in more depth than ever before, and talk about how to get them tested and deployed. |
talk |
dave |
|
16:00 - 18:00 |
BBQ & beer |
- |
social |
- |
- |
19:00 - 20:00 |
presenting the battle results |
what are the test results? |
talk |
- |
|
Sunday 9th August 2015
Do-what-you-want day. There are no programmed talks or workshops on Sunday, we can continue working on projects or just hang out together.
Lightening talks
The lightening talks will be held as self organized sessions. Feel free to pick any time without a talk and present your project/…. A good time is probably in the evening after the talks. That's also why they stop at (latest) 20:00.
Time |
Title |
Abstract |
Type |
Speaker |
Slides & Documentation |