←back to thread

An open source, self-hosted implementation of the Tailscale control server

(github.com)
345 points quyleanh | 1 comments | 03 Apr 25 00:23 UTC | HN request time: 0.207s | source
Show context
pilif ◴[03 Apr 25 03:15 UTC] No.43564293[source]▶
Keep in mind that for many use cases (mobile access, GUI on macOS), this relies on the official Tailscale clients keeping the ability to set the control server.

The moment the inevitable enshitification will start at Tailscale, this feature will go away.

I’m saying this as a currently super happy Tailscale customer who was burned multiple times in the past by other companies being sold or running out of VC money

replies(3): >>43564474 #>>43569271 #>>43574311 #
sixothree ◴[03 Apr 25 13:25 UTC] No.43569271[source]▶
Tailscale clients are the thing I am least happy about with Tailscale. Specifically mobile clients and battery usage.

The reason I can't use Tailscale at work is because it routes traffic through servers we can't control.

I would _love_ to use tailscale at work. It would solve so many problems. I am okay with being forced to open ports. But tunneling traffic through them is extremely worrysome.

replies(2): >>43569840 #>>43570062 #
1. techsupporter ◴[03 Apr 25 14:17 UTC] No.43570062[source]▶
> The reason I can't use Tailscale at work is because it routes traffic through servers we can't control.

You can run your own DERP servers and exclude the Tailscale ones even if you don’t run your own Headscale server: https://tailscale.com/kb/1118/custom-derp-servers