Dieses Wiki ist ein Archiv bis 2023. Das aktuelle Wiki findet sich unter https://wiki.hamburg.ccc.de/

Difference between revisions of "ChaosVPN"

From CCCHHWiki
Jump to: navigation, search
(→‎ip ranges)
m (→‎IP Ranges and Participants:)
Line 75: Line 75:
 
However we will not support 192.168.0.0/16 ip ranges as they are used for various other reasons. This rfc1918 ip range will stay as private to use for internal use (and in fact its used in the dn42 for routing uses.)
 
However we will not support 192.168.0.0/16 ip ranges as they are used for various other reasons. This rfc1918 ip range will stay as private to use for internal use (and in fact its used in the dn42 for routing uses.)
  
−
Question: reverse DNS?<br/>
+
'''Question''': reverse DNS?<br/>
 
"yes" ;) - but we don't know how to implement them for the VPN yet, delegating it with forward zones in local nameservers does not sound very good to me. --[[User:Haegar|Haegar]] 00:40, 29 October 2009 (UTC)
 
"yes" ;) - but we don't know how to implement them for the VPN yet, delegating it with forward zones in local nameservers does not sound very good to me. --[[User:Haegar|Haegar]] 00:40, 29 October 2009 (UTC)
  
 +
'''Question''': Are other ChaosVPN ranges which were already allocated on the Freifunk Wiki also supported (i.e. 10.4.0.0/14 & 10.32.0.0/12)?
  
 
=== ip ranges ===
 
=== ip ranges ===

Revision as of 00:31, 11 November 2009

the big picture

What is this all about?

mc.fly will write some stuff about it. In case you have awesome ideas just add them.



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:

I will also create Debian packages of the config builder once it is in a usable state.

sources

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

IP Ranges and Participants:

We need to have non colliding ip ranges and therefore we need some coordination of the used ip ranges.

First of all we would like to be compilant to the used ip ranges of freifunk and dn42.

The IP ranges overall are defined in the freifunk wiki ip-net page as root source.

So we use 172.31.0.0/16 for the europeans and 10.100.0.0/13 for the americans. That should leave enough space for everone untill ipv6 is not the future but the present. (Real IPv6 ranges already in use can also be announced on the VPN, but there are no thoughts about private/internal adressing yet.)

However we will not support 192.168.0.0/16 ip ranges as they are used for various other reasons. This rfc1918 ip range will stay as private to use for internal use (and in fact its used in the dn42 for routing uses.)

Question: reverse DNS?
"yes" ;) - but we don't know how to implement them for the VPN yet, delegating it with forward zones in local nameservers does not sound very good to me. --Haegar 00:40, 29 October 2009 (UTC)

Question: Are other ChaosVPN ranges which were already allocated on the Freifunk Wiki also supported (i.e. 10.4.0.0/14 & 10.32.0.0/12)?

ip ranges

IP-subnets Unique Name Node Remarks
172.31.0.0/16 europe range europe range europe range
172.31.0.0/23 *reserved* *reserved* This range may be used for Single-IP-VPN nodes like servers which would participate directly but do not need a subnet.
172.31.2.0/23 none free none
your subnet your unique name your url / description your remarks
172.31.16.0/23 *planned* ccchh CCC Hamburg Chaos Computer Club Hansestadt Hamburg
172.31.18.0/23 haegarhome haegar home
172.31.20.0/23 *planned* CCC Hamburg Chaos Computer Club Hansestadt Hamburg Second Range
172.31.22.0/24 haegarvlad haegar hosted servers / vms
172.31.23.0/24 *reserved* *reserved* *reserved*
172.31.24.0/23 *planned* London Hackspace http://london.hackspace.org.uk
172.31.42.0/24 *reserved* *reserved* *reserved*
your subnet your unique name your url / description your remarks
172.31.100.0/24 datensumpf [http://www.datensumpf.de datensumpf mc.flys subnet at home
172.31.255.0/24 *reserved* *reserved* *reserved*
your subnet your unique name your url / description your remarks
10.100.0.0/14 us hackerspaces range us hackerspaces range us hackerspaces range
10.100.0.0/23 psone PS:one
10.100.2.0/23 ccckc CCCKC
10.100.4.0/23 noisebridge Noisebridge
10.100.69.0/23 ResistorNET ResistorNET Information NYC Resistor Hackerspace 397 Bridge Street 5th Flr Brooklyn NY 11201
10.100.100.0/23 hhh HHH network diagram former site og HHH: 114 Forrest St Apt 3A / Brooklyn NYC
your subnet your unique name your url / description your remarks
10.104.0.0/14 us hackerspaces range - reserved us hackerspaces range - reserved us hackerspaces range - reserved

ccchh - Hamburg

T42 - Hamburg

  • connector: winni (at) ccc.de
  • url: http://T42.de/
  • subnets: 10.10.10.0/23 and 10.11.22.0/24 - renumbering needed.

nycresistor - New York

noisebridge - San Francisco

PS:one - Chicago


Hive76 - Philadelphia

ccc hannover

  • (in chaosvpn 1.0)
  • connector: User:Lotho ( lotho [at] hannover.ccc.de )
  • url: http://hannover.ccc.de
  • subnet: 10.23.42.0/24 - renumbering needed due to collision with Freifunk Brandenburg.

ccckc

hhh


what about:

ccc berlin

  • (in chaosvpn 1.0)

ccc cologne

  • (in chaosvpn 1.0)

wanted changes

short term

  • The config file itself is not validated. We need a signing and validating structure. (.sig)
  • clients don't have to authentificate themself - everybody can see the config.
  • if admins are lazy and don't rebuild the config file properly we will have old routes in the network that don't dissapear (at least until the tinc is reconfigured and restarted)


long term

tinc does have some problems. That is the reason why we want to replace that in the forseable future. That will be ChaosVPN 3.0

ChaosVPN 3.0

Retrieved from "https://oldwiki.hamburg.ccc.de/index.php?title=ChaosVPN&oldid=6393"