319 points by quyleanh 1 day ago | 76 comments
SuperShibe 1 day ago
The entire premise of Tailscale SaaS builds on creating tunnels around your firewalls, then enabling the user to police what is allowed to be routed through these tunnels in a intuitive and unified way.
Headscale seems to have nailed down the part of bypassing the firewall and doing fancy NAT-traversal, but can they also fulfill the second part by providing enough of their own security to make up for anything they just bypassed, or will they descend to just being a tool for exposing anything to the internet to fuck around with your local network admin? To me, not giving your Tailscale implementation any way for the user to understand or veto what the control server is instructing the clients to do while also not auditing your servers code at all sure seems daring…
nativeit 23 hours ago
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.
bingo-bongo 21 hours ago
jacobtomlinson 15 hours ago
throawayonthe 21 hours ago
xrd 15 hours ago
password4321 12 hours ago
Also I believe it implements a lower layer of the network stack so more options are supported, though I haven't needed to investigate in detail.
password4321 10 hours ago
bananapub 19 hours ago
codethief 15 hours ago
SuperShibe 14 hours ago
botto 16 hours ago
gpi 24 hours ago
wutwutwat 24 hours ago
gpi 24 hours ago
palotasb 21 hours ago
themgt 24 hours ago
Happily2020 19 hours ago
mynameisvlad 9 hours ago
Tailscale is still running for now, but I'm getting closer and closer to decommissioning it and switching entirely to Netbird.
davidcollantes 14 hours ago
unixfox 7 hours ago
yamrzou 16 hours ago
mrbluecoat 13 hours ago
infogulch 12 hours ago
So here's my proposal: commit to ipv6-only overlay network in the unique local address (ULA) range, then split up the remaining 121 bits into 20 low bits for device addresses (~1M) and 101 high bits that are the hash of the server's public key. Federate by adding the public key of the other instance and use policy and ACLs to manage comms between nodes.
I think it's a nice idea, but the maintainer kradalby said it's out of scope when I brought it up in 2023: https://github.com/juanfont/headscale/issues/1370
telotortium 1 day ago
Headscale has been on HN many times.