Live data from Hacker News

Netbird – Open Source Zero Trust Networking

netbird.io

51–60 of 299 posts

Re: Netbird – Open Source Zero Trust Networking

#52
post #31

Earlier quoted context omitted.

The word "auth keys" meant nothing to you, I guess: https://tailscale.com/kb/1085/auth-keys

What would be your use-case for auth keys with long expiry times? Auth keys are only required for registering new nodes.

When managing your infrastructure as code, it’s quite common to deploy new instances for upgrades etc. Having these keys expire after 3 months is a big pain. Eg doing a routine update by rebuilding an AMI.

I don’t understand how they can have such a strategy, and then not having any decent way to programmatically allocate new keys.

Re: Netbird – Open Source Zero Trust Networking

#53
post #3

But it's missing a tailscale funnel like feature, right? That's one of the main features that I use for some home assistant instances.

Please be aware that when you use tailscale funnel you announce to the whole world that your service exists (through certificate transparency), and you will get scanned immediately. If you don't believe me just put up a simple http server and watch the scanning request come in within seconds of running `tailscale funnel`.

Do not expose anything without authentication.

And absolutely do not expose a folder with something like `python -m http.server -b 0.0.0.0 8080` if you have .git in it, someone will help themselves to it immediately.

If you are aware of this, funnel works fine and is not insecure.

Tailscale IMHO failing in educating people about this danger. They do mention in on the docs, but I think it should be a big red warning when you start it, because people clearly does not realise this.

I took a quick look a while ago and watching just part of the CT firehose, I found 35 .git folders in 30 minutes.

No idea if there was anything sensitive I just did a HEAD check against `.git/index` if I recall.

https://infosec.exchange/@gnyman/115571998182819369

Re: Netbird – Open Source Zero Trust Networking

#55
For someone who want to setup a private network between host/devices, I feel the dilemma is always:

1. Trust a third party like Tailscale by giving them the key to your kingdom, but everything is incredibly easy and secure.

2. Self-host but need at least one host with a fixed IP address and an open port on the Internet. What requires a set of security skills and constant monitoring. That includes headscale, selhosted netbird, zerotier or a private yggdrasil mesh.

Re: Netbird – Open Source Zero Trust Networking

#56

Last time I checked it couldn't do ipv6... in 2026?

Could be intentional: German privacy advocates really like that the limited ipv4 pool forces reusing IPs and prevents accidental imprinting a practically static address on a device.

Makes a lot of sense.

But self-hosting still require at least a public domain name [0], so here goes your privacy right?

- [0] https://docs.netbird.io/selfhosted/selfhosted-quickstart#inf...

Re: Netbird – Open Source Zero Trust Networking

#58

Last time I checked it couldn't do ipv6... in 2026?

Could be intentional: German privacy advocates really like that the limited ipv4 pool forces reusing IPs and prevents accidental imprinting a practically static address on a device.

Can't do IPv6 internally or externally? Internally there should be zero need for ~infinite addresses. Externally though I certainly hope all software is capable of operating via IPv6 at this point because otherwise it will only be increasingly broken.

Re: Netbird – Open Source Zero Trust Networking

#60
post #5
post #3

But it's missing a tailscale funnel like feature, right? That's one of the main features that I use for some home assistant instances.

Out of curiosity, why? I use TS for all my homelab bits (including my HA instance), but connect to TS before opening the HA app. Is it just a case of making it easier/ possible to connect if you’re on another VPN? Are you not concerned with having something from your local network open to the internet?

Besides the use cases listed, we see this as an opportunity for homelabers and organizations to add authentication with access control to already exposed services.
Post reply on HN