Live data from Hacker News

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

github.com

21–30 of 85 posts

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

#23
post #5

This looks interesting! What's the added value over wireguard + openwrt setup?

It's a mesh VPN, so peers communicate directly without additional delay. I opted for Netbird myself because Headscale's UI felt too basic for me back then. Has that improved over the years probably?

How is netbird? Is it more stable than tailscale/headscale? How is your performance while streaming a video?

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

#24
post #20

Earlier quoted context omitted.

As in you rolled out an internal service for the whole company?!

I’d love to see a write-up on that. Especially in the unlikely event that you used Nix for the deployment.

I've done exactly that: headscale in production at work, a few hundred client devices, infrastructure mostly powered by nix. What would you want to hear about it?

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

#25

How does headscale hold up when you're streaming video over jellyfin/plex?

Do you mean when using it as a relay because p2p connectivity isn't possible? The preferred operating mode of Tailscale networks is for the bulk of traffic to go p2p, using various tricks for NAT and firewall traversal.

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

#26
post #17

Earlier quoted context omitted.

maintainer's employment != security audit

My thinking is their time is divided now and could lead to less efforts spent on headscale.

Not compared to the previous state where he worked for an unrelated company and only had his free time to contribute to Headscale.

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

#27
post #12

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

arent most of the the tailscale clients open source aside from the gui portion of the non open source os's?

Yes they are, unless you're using a mainstream OS and/or want to use a GUI, which is probably the most common use case.

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

#28

Every few months I come back to this repo to check if they finally got Tailnet lock running or if someone security audited them in the meanwhile. Unfortunately neither of these things seem to make any progress and thus, I’ve grown uncertain in how much I can trust this as a core part of my infrastructure. The entire premise of Tailscale SaaS builds on creating tunnels around your firewalls, then enabling the user to…

> Headscale seems to have nailed down the part of bypassing the firewall and doing fancy NAT-traversal Did they really roll-their-own for those functions? I thought this was just a control layer on top of Tailscale’s stock services on the backend, are they facilitating connections with novel methods? Apologies if I’m asking obvious questions, I use ZeroTier pretty regularly, but I am not too familiar with Tailscale.

They have a really great in-depth blog post describing how they do it: https://tailscale.com/blog/how-nat-traversal-works

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

#29
post #5

This looks interesting! What's the added value over wireguard + openwrt setup?

Some do not want/have a fixed IP address or anything listening on their home network.

Tailscale or having Headscale hosted somewhere else allows you to do that.

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

#30

Earlier quoted context omitted.

> Headscale seems to have nailed down the part of bypassing the firewall and doing fancy NAT-traversal Did they really roll-their-own for those functions? I thought this was just a control layer on top of Tailscale’s stock services on the backend, are they facilitating connections with novel methods? Apologies if I’m asking obvious questions, I use ZeroTier pretty regularly, but I am not too familiar with Tailscale.

They have a really great in-depth blog post describing how they do it: https://tailscale.com/blog/how-nat-traversal-works

i think they mean headscale's implementation specifics
Post reply on HN