Difference between revisions of "ChaosVPN"

From CCCHHWiki
Jump to: navigation, search
(noisebridge - San Francisco)
(ChaosVPN 2.0)
Line 32: Line 32:
 
= ChaosVPN 2.0 =
 
= ChaosVPN 2.0 =
  
 +
== redesign ==
 
The Rebuild of the ChaosVPN became nessesary at some point, as the vermittlung is blackholed. Furthermore we would like to put live back to the ChaosVPN and use it to interconnect the hackerspaces.
 
The Rebuild of the ChaosVPN became nessesary at some point, as the vermittlung is blackholed. Furthermore we would like to put live back to the ChaosVPN and use it to interconnect the hackerspaces.
  
We are working on a redesign.
+
So we thought its a good time to redesign stuff. We will climb up to tinc 1.0.10.
  
Updated (Backported) tinc 1.0.10 packages for are available at:
+
== software ==
* for Debian Etch: http://debian.sdinet.de/etch/sdinet/tinc/
+
=== Config builder ===
* for Debian Lenny: http://debian.sdinet.de/lenny/sdinet/tinc/
+
Currently we are porting haegars script from perl to c and strip off curl and openssl, so it fits in a OpenWRT box.  
  
 +
=== OpenWRT Packages ===
 +
Blogic will build a special OpenWRT package, which is called chaosvpn at the moment and a recent tinc 1.0.10 for that.
 +
 +
=== Debian Packages ===
 +
Haegar updated (backported) tinc 1.0.10 packages for debian. They are availible at:
 +
* Debian Etch: http://debian.sdinet.de/etch/sdinet/tinc/
 +
* Debian Lenny: http://debian.sdinet.de/lenny/sdinet/tinc/
 +
 +
=== sources ===
 +
The scripts are availible at: http://github.com/ryd/chaosvpn
  
 
== Participants: ==
 
== Participants: ==

Revision as of 00:05, 25 October 2009

ChaosVPN 1.0

TINC SETUP

At the moment the Hamburg ccc Erfa uses TINC together with some dirty perl-scripts, which are used to read the routes and peers.

For this Setup we have howtos for Debian and Gentoo (in german).

Beginninig in 2003

(haegar:) For me the whole setup with Openvpn was to complicated. It would take some time till its done and the scaling problems were forseable.

Therefore i took time today to get a working mini-solution with tinc running real quick.

The bigger issues with ip-submission and database are able to be added later without any big effort.

Most importand design goals were:

  • data traffic between participants must not rely on the ccc infrastructure.
  • failure of any parts of the infrastructure must not shut down the network completely
  • no work needed for participants just because a new participant is joining or a old one quitting.

system requirements

  • linux only first
    • tinc is availible for nearly all unix variants and windows, but my perl script is only working on linux so far.
  • perl with LWP and https support
  • working dyndns hostname that conains the actual router-ip or static ip

Update 2006

Today (2006) i would implement things different than i did before, but when this happens is completely up in the stars. Until there is a better setup we will use the old setup.

ChaosVPN 2.0

redesign

The Rebuild of the ChaosVPN became nessesary at some point, as the vermittlung is blackholed. Furthermore we would like to put live back to the ChaosVPN and use it to interconnect the hackerspaces.

So we thought its a good time to redesign stuff. We will climb up to tinc 1.0.10.

software

Config builder

Currently we are porting haegars script from perl to c and strip off curl and openssl, so it fits in a OpenWRT box.

OpenWRT Packages

Blogic will build a special OpenWRT package, which is called chaosvpn at the moment and a recent tinc 1.0.10 for that.

Debian Packages

Haegar updated (backported) tinc 1.0.10 packages for debian. They are availible at:

sources

The scripts are availible at: http://github.com/ryd/chaosvpn

Participants:

ccchh - Hamburg

nycresistor - New York

noisebridge - San Francisco

PS:one - Chicago

what about:

ccc hannover

  • (in chaosvpn 1.0)

ccc berlin

  • (in chaosvpn 1.0)

ccc cologne

  • (in chaosvpn 1.0)