At the moment the Hamburg ccc Erfa uses TINC together with some dirty perl-scripts, which are used to sread the routes and peers.
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.
- 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
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.
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.
Updated (Backported) tinc 1.0.10 packages for are available at:
- for Debian Etch: http://debian.sdinet.de/etch/sdinet/tinc/
- for Debian Lenny: http://debian.sdinet.de/lenny/sdinet/tinc/
ccchh - Hamburg
- connector: haegar
- url: http://hamburg.ccc.de
nycresistor - New York
noisebridge - San Francisco
- connector: aestetix
- url: https://www.noisebridge.net
PS:one - Chicago
- connector: tcrown
- url: http://pumpingstationone.org/
- ccc hannover (in chaosvpn 1.0)
- ccc berlin (also)
- ccc cologne (same)