Reise Djursland 2005

Datei:Route nach djursland.jpg

Route nach Djursland

Programm

Diskussion im Forum: http://forum.opennet-initiative.de/thread.php?threadid=332
Wetter: http://www.wetteronline.de/Daenemark/Arhus.htm

Freitag

Abreise: 14 Uhr CSR Center, im Bus (Bestellung noch offen)

Late arrival

Treffen in Friland, an der Adresse: Econ Pavillonen, Friland 12, Feldballe, 8410 Ronde.

Samstag

• Breakfeast at Fuglsoecentret
• Visit to the Europeia Science Center
• Short presentation of DjurslandsNet and the new Djursland Networking Project
• Drive to the headquarter at the eco-sustainable village Friland
• Lunch / picnic
• Guided trip through the world of DjurslandsNet
• Presentation of new EU project for 15 new Community Networks in the Balticum
• BBQ dinner at Friland and social event

Sonntag

• Breakfeast at Fuglsoecentret
• Short presentation of Rostock OpenNet
• Discussion and ideas session for further cooperation
• Ad-hoc
• Lunch
• Departure

Reisedetails

Anreise

Fahrtdauer mit dem Auto: 5 - 6 Stunden

Unterbringung

Variante 1: Camping

Friland Feldhalle, Camping, free of cost, food costs 15 - 20 (Währung erfrage ich noch)

Variante 2: Fuglsoecentret

Fuglsoecentret

Kosten: 50 - 60 pro Person (Währung erfrage ich noch).

Organizer

Lokaler Organizer ist Gregers Petersen, den manche bereits von seinem Vortrag in Rostock kennen.

Seine Handy Nummer: +45 3024 8064

Buchungen

Clemens Cap

Identität

Clemens Cap, Blücherstraße 71, 18055 Rostock

Kommunikation

0381 498 7500 (Uni), 0381 499 54 85 (home), Handy (bitte nur im Notfall und während der Reise...) 0171 270 31 32, cap AT informatik DOT uni-rostock DOT de

Anreise

Mit dem eigenen Auto, nimmt noch Robert Nickel mit, hat noch zwei weitere sehr unbequeme Plätze im Kofferraum frei ;-)

Unterbringung

Single Room in the Guest House Fuglsoecentret

Robert Nickel

Identität

Robert Nickel

Kommunikation

ap11 AT opennet-initiative DOT de, mobil: 017670037598

Anreise

Unterbringung

Zelt

Ralph Oesker

Identität

Ralph Oesker, http://wiki.opennet-initiative.de/index.php/Benutzer:Mdbw

Kommunikation

Mail: opennet (at-zeichen) dynaperl.de, Mobil null eins sieben fünf - fünf acht sechs sechs sieben zwei zwei

Anreise

Eigenes Auto, Freitag vormittag ab Rostock bietet noch 2-3 Plätze an

Unterbringung

Zelt oder Auto

Sebastian Hagen

Identität

Sebastian Hagen, sh01; 18106 Rostock, Carl-von-Linne 12

Kommunikation

73656261737469616e5f686167656e406d656d6573706163652e6e6574

Anreise

Nutzung einer MFG von Ralph Oesker

Unterbringung

Zelt oder PKW (Ralph?)

Mathias Mahnke

Einige Infos fehlen noch

Identität

Mathias Mahnke, Am Kabutzenhof 17, 18057 Rostock, http://www.ger783.de/MathiasMahnke

Kommunikation

0381/2005569 (mit AB), 0172/3837053, mathias -AT- mycr -DOT- DE

Anreise

Benötige MFG.

Unterbringung

Zelt wäre ausreichend. Zelt vorhanden. Mitschläfer willkommen.

Rene Ejury

Identität

Rene Ejury, Waldemarstr. 47, 18057 Rostock

Kommunikation

0381/1286099, 0173/4726830 (nur sms), opennet -AT absorb -DOT- it

Anreise

brauche MFG

Unterbringung

Zelt reicht...

Friedrich Hartmann

Identität

Friedrich Hartmann, Borwinstr. 38, 18057 Rostock

Kommunikation

0176/23542708 mailfriedrich-hartmann.de

Anreise

Bei Ralph? Sixt? t.b.c.

Unterbringung

Kein eigenes Zelt in Rostock verfügbar

Template Copy Paste

Identität

Kommunikation

Anreise

Unterbringung

Übersicht

Wer	Anreise	Übernachtung
Clemens	Auto (eigenes)	Fuglsoecentret Single room
Robert	Auto (mit Clemens)	Zelt
Ralph	Auto (eigenes)	Zelt
Sebastian	Auto (mit Ralph)	??
Mathias	Auto (mit Ralph)	Zelt
Rene	Auto (mit Ralph)	??

Vortragsentwurf

Hier ein allererster Versuch die Inhalte unseres Vortrages zu strukturieren. Mir liegt vor allem daran, die kritischen Punkte unseres Wachstums zu beleuchten. Ich (Mathias) werde keine weiteren Änderungen mehr vornehmen.

Gliederung

1. introduction: Original motivation and project history
2. technology
   1. officially supported Access Points - Linksys WRT54g and Asus WL-500g
   2. IEEE80.211 compliant WIFI (ad-hoc mode), IPv4, OLSR
   3. node types
      1. stationary nodes
         1. antennas placed on the roof
         2. APs placed inside flats or offices
         3. to maintain an effective infrastructure, the association owns and administers APs at some important locations
      2. mobile nodes
         1. basically just notebooks with wifi-cards that run OLSR
         2. usable anywhere in the area serviced by ON
   4. history of infrastructure development
      1. temporary installations for test purposes
      2. point-to-point connections using highly directional antennas
      3. growth; mixed use of directional antennas and omnidirectional antennas placed inside of buildings
      4. tendency of members to attempt to establish direct wifi-links to APs linked by LAN to an internet-gateway, stagnation
      5. growth and increase of redundant routes through increase in AP density and use of less directional antennas
   5. history of transmission protocols
      1. WDS; bridging; ethernet Spanning Tree Protocol to deactivate redundant routes
      2. ad-hoc mode; IPv4 routing; OLSR
   6. address spaces
   7. gateway "titan"
      1. SNAT Opennet -> Internet
      2. OpenVPN 2.0; authentication through certificates signed by our CA
      3. DNAT (i.e. port forwarding) to openvpn Addresses; currently 10 ports per user
      4. DSL; theoretical bandwith 3000/384 (kbit/s)?
      5. logging of individual connections
         1. Ocellata - Connection Quality; measured by using ICMP ECHO Requests
            1. [1]
         2. Crinoidea (MySQLdb) - topN IP Addresses according to ON-Internet traffic caused
            1. [2]
         3. Alfredi (PIM) - Maps with colored nodes and connections
            1. [3]
            2. [4]
         4. Ketupo (olsrd, olsrd_dd_ti, dot, Pydot) - Topology Dot Graphs
            1. [5]
         5. Teucrium (netfilter, rrdtool, pyrddtool) - Traffic Graphs
            1. [6]
            2. [7]
   8. interfaces for users
      1. ethernet on their own AP
         1. possibility of using a second AP for private wireless use
      2. OpenVPN for internet-routing (endpoints on user-APs or client-systems)
   9. Acccess Point Firmware
      1. started out using Sveasoft's Alchemy on Linksys, default FW on Asus APs
      2. current versions based on OpenWRT
         1. legacy ON FW: based on Freifunk-Firmware 1.0.2, minor modifications
         2. "Opennet Firmware" based on OpenWRT whiterussian (currently rc2) (several modifications, including the FFF-webinterface)
            1. web-based installation and configuration possible
            2. OpenVPN use on the AP explicitly supported; automated certificate creation
            3. individual extensions still possible, of course
3. social issues
   1. general structure
      1. loosely organized, no pervasive hierarchial structure
      2. high importance of technologically skilled members
   2. day-to-day operation
      1. workshoops and meetings - also effective ways for interested persons to get involved
      2. documentation (e.g. HOWTOs) is collaboratively maintained on the ON wiki
      3. communication mostly per Forum, IRC and e-mail
      4. increasing interest in public relations issues
   3. motivation for individual members
      1. cheap internet access
      2. relatively fast internet access compared to the alternatives in areas without DSL coverage
      3. interest in technology / the community / ideological issues
      4. mobile internet access in the covered area
4. organisation
   1. some explicit internal rules
   2. responsibility for most of the infrastructure lies with AP-owners (i.e. individual members)
   3. individual competent members responsible for
      1. firmware design
      2. gateway administration
      3. management of jointly owned APs
      4. Public Relations
      5. support of new members
5. future relevance
   1. connecting villages without broadband-coverage?
   2. supported by people interested in technological and social issues in areas covered by broadband
   3. mobile use
6. guesstimated use of communication methods
   1. 45% - Forum (Wortlab Burning Board)
   2. 30% - Wiki (Mediawiki)
   3. 15% - Opennet IRC, increasing relevance
   4. 6% - Opennet mailing list (Mailman)
   5. 3% - Opennet Mail (apXX@..)
   6. 1% - Gallery

Wichtige Bilder

• 
  Opennet Firmware, OpenVPN-Dialog
• 
  Opennet Karte (Alfredi), Ausschnitt KTV
• 
  Opennet Karte (Alfredi), Gesamt
• 
  KTV, vllt. kann man noch ein Screenshot von Google Earth machen (Windows-Nutzer vor!)
• 
  Opennet Logo
• 
  Panel AP43
• 
  Panel AP38
• 
  Saugnapf-Omni AP24
• 
  Quad AP11
• 
  Reichweitentest
• 
  Netzwerk Grundlagen Workshop
• 
  Opennet Adressierung
• 
  Monatliche Top10-Nutzer (Transfervolumen)
• 
  Verbindungsqualität (Octella)
• 
  Ausschnitt Drahtlose Topologie (Dot-Graph)
• 
  Ausschnitt Drahtgebundene Topologie
• 
  1d Traffic
• 
  30d Traffic
• 
  356d Traffic

Weitere Bilder:

• http://www.opennet-initiative.de/gallery/Shootout2005