CollabVPN: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(added link to forkie.dev) |
||
| Line 52: | Line 52: | ||
*** Also inbound connections are let in on IPv6 and IPv4. |
*** Also inbound connections are let in on IPv6 and IPv4. |
||
*** You can request to have a few IPv4 ports routed to you. |
*** You can request to have a few IPv4 ports routed to you. |
||
*** You can request to have subdomains on forkie.dev aswell as RDNS on IPv6. |
*** You can request to have subdomains on [https://forkie.dev forkie.dev] aswell as RDNS on IPv6. |
||
*** Hosting WebServers is possible thanks to [https://github.com/AGWA/snid snid]. Simply tell users to host an HTTPS server on 443 with your subdomain and IPv4 connections from for example 192.0.2.0 will show up to come from the IPv6 NAT64 subnet of 64:ff9b:1:fffe:80:ff7f::/96, so it would be 64:ff9b:1:fffe:80:ff7f:192.0.2.0 aka 64:ff9b:1:fffe:80:ff7f:c000:200. |
*** Hosting WebServers is possible thanks to [https://github.com/AGWA/snid snid]. Simply tell users to host an HTTPS server on 443 with your subdomain and IPv4 connections from for example 192.0.2.0 will show up to come from the IPv6 NAT64 subnet of 64:ff9b:1:fffe:80:ff7f::/96, so it would be 64:ff9b:1:fffe:80:ff7f:192.0.2.0 aka 64:ff9b:1:fffe:80:ff7f:c000:200. |
||
Revision as of 17:29, 6 May 2024
CollabVPN is a VPN provided to users who want to host CollabVMs/UserVMs but don't want to use their existing ISP/NSP as an exit.
It is not affiliated with Computernewb or CollabVM in any way.
This was created by Julia because many commercial VPN providers are not equipping users with enough global IPv6 addresses, resulting in an IPv4-only or IPv4-prefferred network.
Technical details
- It is currently hosted on a VPS at Ukrainian Data Network but there are plans to move it to her own ASN once she is an LIR at RIPE.
- WireGuard Endpoint:
collabvpn.julias.zone:80
| Used For | Pool | Description |
|---|---|---|
| IPv6 Peers | 2a0f:e586:f:2c02::/64 | These are assigned to the WireGuard peers and are used to route their /64s |
| IPv6 Pool | 2a0f:e586:f:2c10::/60 | This pool contains 16 /64s for assignment to peers. More can be added once necessary. |
| IPv4 Peers | 10.1.1.0/24 | This pool contains 254 IPv4 addresses used for NAT purposes assigned to the peers. |
| IPv4 SRCNAT | 193.218.118.174:49152-65535 | The NAT uses these ports for outgoing IPv4 connections. |
| IPv4 DSTNAT | 193.218.118.174:1024-49151 | These IPv4 ports can be routed to peers on demand. |
Requesting a Tunnel
It is possible to request a WireGuard tunnel from Julia (wiki, website) that you can connect to and tunnel your VMs over.
You need to include the following information when requesting a tunnel:
- Your WireGuard public key
- Your GPG public key (optional, but nice to have for extra security like WireGuard PSKs). Sign and encrypt it with 0075530C72926390787F472D2CB69D1DB326E875 if you like.
- How many /64 IPv6 subnets you need, aka how many bridges you want to tunnel.
- What firewall configuration you want:
- Restricted
- Only outbound IPv6 and IPv4 connections are permitted.
- Inbound connections are filtered and only responses/packets from tracked connections are let in.
- This is the default unless you explicitly request exposure.
- Exposed
- Also inbound connections are let in on IPv6 and IPv4.
- You can request to have a few IPv4 ports routed to you.
- You can request to have subdomains on forkie.dev aswell as RDNS on IPv6.
- Hosting WebServers is possible thanks to snid. Simply tell users to host an HTTPS server on 443 with your subdomain and IPv4 connections from for example 192.0.2.0 will show up to come from the IPv6 NAT64 subnet of 64:ff9b:1:fffe:80:ff7f::/96, so it would be 64:ff9b:1:fffe:80:ff7f:192.0.2.0 aka 64:ff9b:1:fffe:80:ff7f:c000:200.
- Restricted
To Do
- Further technical details like blocked ports