| Filename | Latest commit message | Latest commit date |
|---|---|---|
| README.md | ||
otter.rocks
This project is very young and filled with potential improvements
The internet is quite rapidly becoming a more hostile place[^1] to share little projects in the open. With LLM tools being leveraged to find and exploit security vulnerabilities quicker than fixes can be applied, my general approach has been to pull more and more off of the public internet and onto my private Tailscale VPN. Many of the projects that I would like to pull off of the internet are shared with friends who are not on my tailnet, a casualty of the desire to reduce potential surface area for exploitation.
Otter.rocks is a private network which bridges that gap between multiple tailnets so we can restore some of the lost connectivity and restore some peace of mind with a network of people I know and trust.
Who this project is for
Otter.rocks is specifically for Friends and Friends of Friends who want to either access this network or want to add to our little home here. If you feel that you even slightly fit that description, please reach out and I'll get you an invite code to the network.
What this project is not
This project does not aim to solve a security threat inside of the network and makes no guarantees about safety between the connector network, its clients, and bridged overlay networks. It only aims to reduce the potential surface area of attack from literally the entire internet to a group of friends that all have quick access to each other.
Architecture
At the end of the day this is an overlay network used to bridge other overlay networks together.
┌────────────────────────────────────────────────────────────────────────────────┐
│ Tailscale Network A │
│ ┌──────────────────────┐ ┌───────────────┐ │
│ ┌─────────┐ ┌─────────┐ │ Reverse Proxy │ │ Local Service │ │
│ │ User 1 │ │ User 2 │ │ svc-a.a.otter.rocks ┼────► Svc:A │ │
│ └────┬────┘ └────┬────┘ └───────▲──────────────┘ └───────────────┘ │
│ │ │ └──────────────┐ │
│ │ [ svc-a.a.otter.rocks ] │ │
│ │ │ ┌───────────────────────────┐ │ │
│ └─────┐ │ │ Traefik │ │ │
│ │ │ │ │ │ │
│ │ └──────┤► HostSNI(`a.otter.rocks`) ┼─┘ │
│ [ svc-b.b.otter.rocks ] │ │ │
│ └──────────────┤► HostSNI(`*.otter.rocks`) ┼─┐ │
│ │ │ │ │
│ └───────────────────────────┘ │ │
│ │ │
└─────────────────────────────────────────────────────────┼──────────────────────┘
│
┌─────────────────────────────────────────────────────────┼──────────────────────┐
│ Otter.rocks Network │ │
│ ┌──────────────────────────────────────────────────────┘ │
│ │ ┌───────────────────────────┐ │
│ │ │ Traefik │ ┌─────────┐ ┌─────────┐ │
│ │ │ │ │ User 3 │ │ User 4 │ │
│ │ │ HostSNI(`a.otter.rocks`) │ └─────────┘ └─────────┘ │
│ │ │ │ │
│ └──┼► HostSNI(`b.otter.rocks`) ┼─┐ │
│ │ │ │ │
│ │ HostSNI(`c.otter.rocks`) │ │ │
│ │ │ │ │
│ │ HostSNI(`...`) │ │ │
│ └───────────────────────────┘ │ │
│ │ │
│ │ │
└───────────────────────────────────┼────────────────────────────────────────────┘
│
┌───────────────────────────────────┼────────────────────────────────────────────┐
│ Tailscale Network B │ │
│ │ │
│ ┌───────────────────────────────┘ ┌─────────┐ ┌─────────┐ │
│ │ ┌───────────────────────────┐ │ User 5 │ │ User 6 │ │
│ │ │ Traefik │ └─────────┘ └─────────┘ │
│ │ │ │ │
│ └─┼► HostSNI(`b.otter.rocks`) ┼─┐ │
│ │ │ │ │
│ │ HostSNI(`*.otter.rocks`) │ │ │
│ │ │ │ │
│ └───────────────────────────┘ │ │
│ ┌────┘ │
│ │ ┌───────────────────────┐ ┌───────────────┐ │
│ │ │ Reverse Proxy │ │ Local Service │ │
│ └───┼► svc-b.b.otter.rocks ┼───► Svc:B │ │
│ └───────────────────────┘ └───────────────┘ │
└────────────────────────────────────────────────────────────────────────────────┘
We separate this into two primary roles.
- Consumers
- Service Bridges
Consumers are your day to day users who exist as individuals on any connected overlay network or the Otter.rocks network directly. They do not have the ability to expose their own services, only access services throughout the broader network.
Service Bridges are responsible for routing bidirectional traffic between their respective overlay networks and the otter.rocks network. Currently this is a pair of side car containers which have credentials to connect to the overlay network and Otter.rocks as well as a reverse proxy to expose those services.
Service Bridge
When a service bridge is created, a namespace is reserved on Otter.rocks as
<namespace>.otter.rocks. All subdomains of this namespace are reserved for
that service bridge. Each namespace has a single IP within the Otter.rocks
network so multiple services will need to be proxied through a reverse proxy.
Currently there is a requirement for overlay network maintainers to maintain DNS records on their network to allow services within the otter.rocks network to be routable to users on the overlay network.
Quick Start
Roadmap / Feature Work
- Convert Service Bridge to TCP routers to preserve TLS information
- Push namespace certificates to Service Bridge
- Otter.rocks DNS Service