Dieses Wiki ist ein Archiv bis 2023. Das aktuelle Wiki findet sich unter https://wiki.hamburg.ccc.de/
Difference between revisions of "ChaosVPN"
(→ip ranges: Added Noisebridge) |
|||
(138 intermediate revisions by 34 users not shown) | |||
Line 1: | Line 1: | ||
− | + | {{Template:ChaosVPNBanner}} | |
− | + | = 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: | |
+ | * http://vpnhub1.hack/chaosvpn.png (only from inside ChaosVPN; updated once per hour) | ||
+ | * http://vpnhub1.hack/chaosvpn.svg | ||
+ | and a simple display of node-uptimes: | ||
+ | * http://vpnhub1.hack/chaosvpn.nodes.html. | ||
− | + | = Howto join ChaosVPN? = | |
− | + | You want to join ChaosVPN and experience the awesomeness of it? | |
− | |||
− | |||
− | |||
− | + | * 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. | |
− | |||
− | |||
− | = | + | = 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: == | == IP Ranges and Participants: == | ||
− | + | Please see [[ChaosVPN:IPRanges | IP Range ]] for more Infos. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | == Other related software == | |
− | + | === DNS === | |
− | + | See [[ChaosVPN:DNS | 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 [[ChaosVPN:IPRanges#ccc_hannover|Hannover]] and [[ChaosVPN:IPRanges#ccchh_-_Hamburg|Hamburg]] hackerspaces. <br> | |
− | + | 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? | |
− | |||
− | |||
− | |||
− | |||
− | + | [[ChaosVPN:todo|A collection of short term changes]] | |
− | |||
− | |||
− | |||
− | == | + | = Chaosvpn Geekends = |
− | |||
− | |||
− | |||
− | |||
+ | * [[ChaosVPN:geekend0|geekend 0 at Hamburg]] | ||
+ | * [[ChaosVPN:geekend1|geekend 1 at Hamburg]] | ||
+ | * [[ChaosVPN:geekend10|geekend 10 at Hamburg]] | ||
+ | = 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) | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | * | + | * [[ChaosVPN:Proxy|Proxy]] |
− | * http:// | + | * [[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]] | ||
− | + | [[Category:ChaosVPN]] |
Latest revision as of 19: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.
Contents
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:
- http://vpnhub1.hack/chaosvpn.png (only from inside ChaosVPN; updated once per hour)
- http://vpnhub1.hack/chaosvpn.svg
and a simple display of node-uptimes:
Howto join ChaosVPN?
You want to join ChaosVPN and experience the awesomeness of it?
- Go to our Generic Howto
- Go to our Debian Howto
- Go to our Ubuntu Howto
- Go to our OpenWRT Howto
- Go to our FreeBSD Howto
- Go to our NetBSD Howto
- Go to our NetBSD NAT VPN router using chaosvpn and ipnet Howto
- Go to our Apple Mac OSX Howto
- Go to our Raspbian Howto
- If you own a Fonera 2.0n you may want to try Fonera Howto (quite outdated)
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.
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)