You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+34-9Lines changed: 34 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,9 @@ An open source implementation of the Tailscale coordination server.
6
6
7
7
## Overview
8
8
9
-
Tailscale is [a modern VPN](https://tailscale.com/) built on top of [Wireguard](https://www.wireguard.com/). It [works like an overlay network](https://tailscale.com/blog/how-tailscale-works/) between the computers of your networks - using all kinds of [NAT traversal sorcery](https://tailscale.com/blog/how-nat-traversal-works/).
9
+
Tailscale is [a modern VPN](https://tailscale.com/) built on top of [Wireguard](https://www.wireguard.com/). It [works like an overlay network](https://tailscale.com/blog/how-tailscale-works/) between the computers of your networks - using all kinds of [NAT traversal sorcery](https://tailscale.com/blog/how-nat-traversal-works/).
10
10
11
-
Everything in Tailscale is Open Source, except the GUI clients for proprietary OS (Windows and macOS/iOS), and the 'coordination/control server'.
11
+
Everything in Tailscale is Open Source, except the GUI clients for proprietary OS (Windows and macOS/iOS), and the 'coordination/control server'.
12
12
13
13
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.
14
14
@@ -20,9 +20,10 @@ Headscale implements this coordination server.
20
20
-[x] Node registration through the web flow
21
21
-[x] Network changes are relied to the nodes
22
22
-[x]~~Multiuser~~ Namespace support
23
-
-[x] Basic routing (advertise & accept)
23
+
-[x] Basic routing (advertise & accept)
24
24
-[ ] Share nodes between ~~users~~ namespaces
25
25
-[x] Node registration via pre-auth keys
26
+
-[X] JSON-formatted output
26
27
-[ ] ACLs
27
28
-[ ] DNS
28
29
@@ -42,18 +43,18 @@ Suggestions/PRs welcomed!
42
43
```shell
43
44
make
44
45
```
45
-
46
+
46
47
2. Get yourself a PostgreSQL DB running (yes, [I know](https://tailscale.com/blog/an-unlikely-database-migration/))
47
48
48
-
```shell
49
+
```shell
49
50
docker run --name headscale -e POSTGRES_DB=headscale -e \
2. Use the authkey from your machine to register it
91
+
```shell
92
+
tailscale up -login-server YOUR_HEADSCALE_URL --authkey YOURAUTHKEY
93
+
```
94
+
95
+
96
+
Please bear in mind that all the commands from headscale support adding `-o json` or `-o json-line` to get a nicely JSON-formatted output.
97
+
98
+
82
99
## Configuration reference
83
100
84
101
Headscale's configuration file is named `config.json` or `config.yaml`. Headscale will look for it in `/etc/headscale`, `~/.headscale` and finally the directory from where the Headscale binary is executed.
@@ -131,7 +148,15 @@ To get a certificate automatically via [Let's Encrypt](https://letsencrypt.org/)
131
148
132
149
## Disclaimer
133
150
134
-
1.I have nothing to do with Tailscale, or Tailscale Inc.
151
+
1. We have nothing to do with Tailscale, or Tailscale Inc.
135
152
2. The purpose of writing this was to learn how Tailscale works.
0 commit comments