Difference between revisions of "ChaosVPN"

From CCCHHWiki
Jump to: navigation, search
m (the big pic)
m (Services available on ChaosVPN: -Minetest - service no more exists)
 
(164 intermediate revisions by 36 users not shown)
Line 1: Line 1:
''' the big picture '''
+
{{Template:ChaosVPNBanner}}
What is this all about?
 
  
 +
= Goals =
  
 +
ChaosVPN is a system to connect Hackers.
  
 +
Design principals include that it should be without Single Point of Failure, make usage of full encryption, use RFC1918 ip ranges, scales well on >100 connected networks and is being able to run on a embedded hardware you will find in our todays router.
  
= ChaosVPN 1.0 =
+
It should be designed that noone sees other peoples traffic.
  
== TINC SETUP ==
+
It should be mainly autoconfig as in that besides the joining node no administrator of the network should be in the need to acutally do something when a node joins or leaves.
At the moment the Hamburg ccc Erfa uses [http://www.tinc-vpn.org TINC] together with some dirty perl-scripts, which are used to read the routes and peers.
 
  
For this Setup we have howtos for
+
If you want to find a solution for a Network without Single Point of failure, has - due to Voice over IP - low latency and that noone will see other peoples traffic you end up pretty quick with a full mesh based network.
[[ChaosVPN::DebianHowto|Debian]] and [[ChaosVPN::GentooHowto|Gentoo]] (in german).
 
  
=== Beginninig in 2003 ===
+
Therefore we came up with the tinc solution. tinc does a fully meshed peer to peer network and it defines endpoints and not tunnels.
(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.
+
ChaosVPN connects hacker wherever they are. We connect roadwarriors with their notebook. Servers, even virtual ones in Datacenters, Hackerhouses and hackerspaces. To sum it up we connect networks - maybe down to a small /32.
  
The bigger issues with ip-submission and database are able to be added later without any big effort.
+
So there we are. ChaosVPN is working and it seems the usage increases, more nodes join in and more sevices pop up.
  
Most importand design goals were:
+
For now, an overview picture of the currently connected nodes:
* data traffic between participants must not rely on the ccc infrastructure.
+
* http://vpnhub1.hack/chaosvpn.png (only from inside ChaosVPN; updated once per hour)
* failure of any parts of the infrastructure must not shut down the network completely
+
* http://vpnhub1.hack/chaosvpn.svg
* no work needed for participants just because a new participant is joining or a old one quitting.
+
and a simple display of node-uptimes:
 +
* http://vpnhub1.hack/chaosvpn.nodes.html.
  
system requirements
+
= Howto join ChaosVPN? =
* 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 ===
+
You want to join ChaosVPN and experience the awesomeness of it?
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 =
+
* Go to our [[ChaosVPN:Howto|Generic Howto]]
 +
* Go to our [[ChaosVPN:DebianHowto|Debian Howto]]
 +
* Go to our [[ChaosVPN:UbuntuHowto|Ubuntu Howto]]
 +
* Go to our [[ChaosVPN:OpenWRTHowto|OpenWRT Howto]]
 +
* Go to our [[ChaosVPN:FreeBSDHowto|FreeBSD Howto]]
 +
* Go to our [[ChaosVPN:NetBSDHowto|NetBSD Howto]]
 +
* Go to our [[ChaosVPN:Netbsd_NAT_VPN_router_using_chaosvpn_and_ipnat|NetBSD NAT VPN router using chaosvpn and ipnet Howto]]
 +
* Go to our [[ChaosVPN:MacOSXHowto‎|Apple Mac OSX Howto]]
 +
* Go to our [[ChaosVPN:RaspbianHowto|Raspbian Howto]]
 +
* If you own a Fonera 2.0n you may want to try [[ChaosVPN:Fonera|Fonera Howto]] (quite outdated)
 +
 
 +
There is a short HowTo [[ChaosVPN:MeshYourNodes|how to better mesh your own nodes]] using ChaosVPN.
  
== redesign ==
+
= Mailinglist =
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.
+
We have a mailinglist, and invite all interested persons to join.
  
== software ==
+
https://www.hamburg.ccc.de/mailman/listinfo/chaosvpn
=== 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 ===
+
= ChaosVPN 2.0 =
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 ===
+
== IP Ranges and Participants: ==
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/
 
  
I will also create Debian packages of the config builder once it is in a usable state.
+
Please see [[ChaosVPN:IPRanges | IP Range ]] for more Infos.
  
=== sources ===
+
== Other related software ==
The scripts are availible at: http://github.com/ryd/chaosvpn
 
  
== IP Ranges and Participants: ==
+
=== DNS ===
 +
See [[ChaosVPN:DNS | DNS]]
 +
 
 +
=== IRC ===
 +
 
 +
irc.hackint.hack (172.31.0.30) or irc.hackint.net - join us in #chaosvpn
  
We need to have non colliding ip ranges and therefore we need some coordination of the used ip ranges.
+
=== VoIP ===
  
First of all we would like to be compilant to the used ip ranges of [http://www.freifunk.net freifunk] and [http://dn42.net dn42].
+
Asterisk servers allowing incoming and outgoing calls to POTS in [[ChaosVPN:IPRanges#ccc_hannover|Hannover]] and [[ChaosVPN:IPRanges#ccchh_-_Hamburg|Hamburg]] hackerspaces. <br>
 +
Ask the admins for more information.
  
The IP ranges overall are defined in the [http://wiki.freifunk.net/IP-Netze freifunk wiki ip-net] page as root source.
+
=== Requested applications ===
  
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.
+
During Chaos Communication Camp 2011, participants of the ChaosVPN workshop suggested various applications:
  
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.)
+
* Mirrors of interesting public FTP/WWW sites
 +
* Bittorrent trackers
 +
* Email (either transparently route email from public domains via ChaosVPN, or have .hack email addresses)
 +
* Censorship detection: service to request a public webpage from proxies at several nodes at once, compare the differences
 +
* GeoIP avoidance?
 +
* Social networking things
 +
* Varnish cache
 +
* LDAP (maybe to allow authenticating hackers against their own hackerspace's LDAP server, like Eduroam)
 +
* Multicast services (limited support in tinc, not automatically forwarded to the LANs)
 +
* TOR entry nodes in ChaosVPN
 +
* NNTP (already available on dn42)
 +
* More games!
 +
* Distributed computing (BOINC, GRID stuff)
  
{| class="wikitable"
+
== Wanted changes ==
|- bgcolor="#efefef"
 
! IP-subnets
 
! Node
 
| unique name
 
! Remarks
 
|-
 
| your subnet
 
| your url / description
 
| your unique name
 
| your remarks
 
|-
 
| 172.31.16.0/23 *planned*
 
|[http://www.hamburg.ccc.de CCC Hamburg].
 
| Chaos Computer Club Hansestadt Hamburg
 
|}
 
  
=== ccchh - Hamburg ===
+
Ideas?
* connector: [[User:Haegar]]
 
* url: http://hamburg.ccc.de
 
* added in Wiki
 
  
=== nycresistor - New York ===
+
[[ChaosVPN:todo|A collection of short term changes]]
* connector: [[User:openfly]] ( matt [at] nycresistor.com )
 
* url: http://www.nycresistor.com
 
* network Wiki: http://wiki.nycresistor.com/wiki/ResistorNET
 
  
=== noisebridge - San Francisco ===
+
= Chaosvpn Geekends =
* connector: aestetix
 
* url: https://www.noisebridge.net
 
* network setup: https://www.noisebridge.net/wiki/Network
 
  
=== PS:one - Chicago ===
+
* [[ChaosVPN:geekend0|geekend 0 at Hamburg]]
* connector: tcrown
+
* [[ChaosVPN:geekend1|geekend 1 at Hamburg]]
* url: http://pumpingstationone.org/
+
* [[ChaosVPN:geekend10|geekend 10 at Hamburg]]
  
what about:
+
= Services available on ChaosVPN =
=== ccc hannover ===
 
* (in chaosvpn 1.0)
 
* connector: [[User:Lotho]] ( lotho [at] hannover.ccc.de )
 
* url: http://hannover.ccc.de
 
  
=== ccc berlin  ===
+
Update:
* (in chaosvpn 1.0)
 
  
=== ccc cologne ===
+
If you have services you wish to be accessible to the whole of the Chaosvpn, please add your services to the online list available (within Chaosvpn) at:
* (in chaosvpn 1.0)
 
  
== wanted changes ==
+
http://list.weird.hack - Service list - 10.100.44.1 (but seems to be death currently)
=== 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 [http://wiki.hamburg.ccc.de/index.php/ChaosVPN#ChaosVPN_3.0 ChaosVPN 3.0]
 
  
* Participants can fake network ranges my intention or mistake. (control informations inside tinc are not proper authentificated)
+
* [[ChaosVPN:Proxy|Proxy]]
* http://www.cs.auckland.ac.nz/~pgut001/pubs/linux_vpn.txt
+
* [[ChaosVPN:CTF|OpenArena CTF]]
 +
* [[VoIP| Vermittlung Chaosphone]]
 +
* [[ChaosVPN:VoIP|VoIP]]
 +
* [[ChaosVPN:IRC|IRC]]
 +
* [[ChaosVPN:Minecraft|Minecraft]]
 +
* [[ChaosVPN:Bitlbee|Bitlbee]]
 +
* [[ChaosVPN:ZNC|ZNC]]
 +
* [[ChaosVPN:Jabber|Jabber]]
 +
* [[ChaosVPN:FTP|FTP]]
 +
* [[ChaosVPN:BBS|BBS]]
 +
* [[ChaosVPN:Cracking|HashCracking]]
 +
* [[ChaosVPN:Monitoring|Monitoring]]
 +
* [[ChaosVPN:News|Usenet]]
 +
* [[ChaosVPN:NZB|Usenet indexer (newznab)]]
 +
* [http://brmlab.cz/project/chaosvpn#brmlab_warzone Brmlab WarZone challenges]
 +
* [http://brmlab.cz/project/chaosvpn#tor_socks4_proxy Brmlab Tor SOCKS4 proxy]
 +
* [[ChaosVPN:whatsmyip|ifconfig.hack info, a whats my ip page]]
  
= ChaosVPN 3.0 =
+
[[Category:ChaosVPN]]

Latest revision as of 20:24, 6 June 2019

Note:
ChaosVPN is a VPN to connect Hackers and Hackerspaces - it does NOT provide anonymous internet access!
For this look at tor or other similar services.

It will also not help you to reach domains like .rdos, .lll, .clos or any other strange things supposed to be available on the "dark web".

Alternative: If you prefer BGP, you can also connect via https://dn42.net/, we are interconnected.

Goals

ChaosVPN is a system to connect Hackers.

Design principals include that it should be without Single Point of Failure, make usage of full encryption, use RFC1918 ip ranges, scales well on >100 connected networks and is being able to run on a embedded hardware you will find in our todays router.

It should be designed that noone sees other peoples traffic.

It should be mainly autoconfig as in that besides the joining node no administrator of the network should be in the need to acutally do something when a node joins or leaves.

If you want to find a solution for a Network without Single Point of failure, has - due to Voice over IP - low latency and that noone will see other peoples traffic you end up pretty quick with a full mesh based network.

Therefore we came up with the tinc solution. tinc does a fully meshed peer to peer network and it defines endpoints and not tunnels.

ChaosVPN connects hacker wherever they are. We connect roadwarriors with their notebook. Servers, even virtual ones in Datacenters, Hackerhouses and hackerspaces. To sum it up we connect networks - maybe down to a small /32.

So there we are. ChaosVPN is working and it seems the usage increases, more nodes join in and more sevices pop up.

For now, an overview picture of the currently connected nodes:

and a simple display of node-uptimes:

Howto join ChaosVPN?

You want to join ChaosVPN and experience the awesomeness of it?

There is a short HowTo how to better mesh your own nodes using ChaosVPN.

Mailinglist

We have a mailinglist, and invite all interested persons to join.

https://www.hamburg.ccc.de/mailman/listinfo/chaosvpn

ChaosVPN 2.0

IP Ranges and Participants:

Please see IP Range for more Infos.

Other related software

DNS

See DNS

IRC

irc.hackint.hack (172.31.0.30) or irc.hackint.net - join us in #chaosvpn

VoIP

Asterisk servers allowing incoming and outgoing calls to POTS in Hannover and Hamburg hackerspaces.
Ask the admins for more information.

Requested applications

During Chaos Communication Camp 2011, participants of the ChaosVPN workshop suggested various applications:

  • Mirrors of interesting public FTP/WWW sites
  • Bittorrent trackers
  • Email (either transparently route email from public domains via ChaosVPN, or have .hack email addresses)
  • Censorship detection: service to request a public webpage from proxies at several nodes at once, compare the differences
  • GeoIP avoidance?
  • Social networking things
  • Varnish cache
  • LDAP (maybe to allow authenticating hackers against their own hackerspace's LDAP server, like Eduroam)
  • Multicast services (limited support in tinc, not automatically forwarded to the LANs)
  • TOR entry nodes in ChaosVPN
  • NNTP (already available on dn42)
  • More games!
  • Distributed computing (BOINC, GRID stuff)

Wanted changes

Ideas?

A collection of short term changes

Chaosvpn Geekends

Services available on ChaosVPN

Update:

If you have services you wish to be accessible to the whole of the Chaosvpn, please add your services to the online list available (within Chaosvpn) at:

http://list.weird.hack - Service list - 10.100.44.1 (but seems to be death currently)