An open source, self-hosted implementation of the Tailscale control server
Go to file
Ward Vandewege a71387f9d2 Add additional locations to look for the config.json file:
/etc/headscale and $HOME/.headscale
2021-04-21 17:33:09 -04:00
cmd/headscale Add additional locations to look for the config.json file: 2021-04-21 17:33:09 -04:00
docker added dockerfile 2020-07-27 22:07:23 +10:00
.gitignore Fixed gitignore 2021-02-21 01:31:50 +01:00
api.go Initial multi-user support using namespaces 2021-02-28 00:58:09 +01:00
app.go Minor code reorg 2021-04-08 23:57:31 +02:00
cli.go Minor code reorg 2021-04-08 23:57:31 +02:00
config.json.example Load DERP servers from file 2021-02-20 23:57:06 +01:00
db.go Initial multi-user support using namespaces 2021-02-28 00:58:09 +01:00
derp.yaml Load DERP servers from file 2021-02-20 23:57:06 +01:00
go.mod Bump mod 2021-04-08 23:57:47 +02:00
go.sum Bump mod 2021-04-08 23:57:47 +02:00
LICENSE Initial commit 2020-06-21 11:21:07 +02:00
machine.go Removed log message 2021-03-17 23:09:45 +01:00
namespaces.go Initial multi-user support using namespaces 2021-02-28 00:58:09 +01:00
README.md Minor readme fixes 2021-03-18 23:02:36 +00:00
utils.go Seed the random IP address generator 2021-02-21 22:11:27 +01:00

Headscale

An open source implementation of the Tailscale coordination server.

Overview

Tailscale is a modern VPN built on top of Wireguard. It works like an overlay network between the computers of your networks - using all kinds of NAT traversal sorcery.

Everything in Tailscale is Open Source, except the GUI clients for proprietary OS (Windows and macOS/iOS), and the 'coordination/control server'.

The control server works as an exchange point of cryptographic public keys for the nodes in the Tailscale network. It also assigns the IP addresses of the clients, creates the boundaries between each user, enables sharing machines between users, and exposes the advertised routes of your nodes.

Headscale implements this coordination server.

Status

  • Basic functionality (nodes can communicate with each other)
  • Node registration through the web flow
  • Network changes are relied to the nodes
  • Multiuser Namespace support
  • Basic routing (advertise & accept)
  • Share nodes between users namespaces
  • Node registration via pre-auth keys
  • ACLs
  • DNS

... and probably lots of stuff missing

Roadmap 🤷

Basic multiuser support (multinamespace, actually) is now implemented. No node sharing or ACLs between namespaces yet though...

Pre-auth keys should also be feasible.

Suggestions/PRs welcomed!

Running it

  1. Compile the headscale binary
go build cmd/headscale/headscale.go 
  1. Get youself a PostgreSQL DB running (yes, I know)
docker run --name headscale -e POSTGRES_DB=headscale -e \
  POSTGRES_USER=foo -e POSTGRES_PASSWORD=bar -p 5432:5432 -d postgres
  1. Sort some stuff up (headscale Wireguard keys & the config.json file)
wg genkey > private.key
wg pubkey < private.key > public.key  # not needed 
cp config.json.example config.json
  1. Create a namespace (equivalent to a user in tailscale.com)
./headscale namespace create myfirstnamespace
  1. Run the server
./headscale serve
  1. Add your first machine
tailscale up -login-server YOUR_HEADSCALE_URL
  1. Navigate to the URL you will get with tailscale up, where you'll find your machine key.

  2. In the server, register your machine to a namespace with the CLI

./headscale register YOURMACHINEKEY myfirstnamespace

Disclaimer

  1. I have nothing to do with Tailscale, or Tailscale Inc.
  2. The purpose of writing this was to learn how Tailscale works.
  3. I don't use Headscale myself.