I self-host my mesh VPN with NetBird instead of Tailscale — here's the one reason, and where Tailscale still wins

说明与用途

NetBird 允许创建完全自托管的 WireGuard 网格，并与现有身份提供商集成，消除第二个控制平面，将所有访问决策集中在一个地方。

问题

Need a VPN that integrates with existing identity provider and keeps control plane self-hosted, avoiding a third‑party brain.

结果

NetBird enabled a fully self‑hosted WireGuard mesh that integrates with the existing IdP, eliminating a second control plane and keeping all access decisions in one place. It required some configuration work (token format, split‑horizon DNS) but provided tighter security alignment.

工作流

• 1. Install NetBird server and client on devices
• 2. Configure NetBird to use OIDC with existing IdP
• 3. Set dashboard to use ID token (JWT) instead of opaque access token
• 4. Verify peer connectivity and name resolution over mesh
• 5. Test split‑horizon DNS behavior and adjust resolvers
• 6. Monitor and back up NetBird control plane
• 7. Offboard devices/users via IdP to remove them from VPN

证据

NetBird speaks OIDC to my existing self-hosted identity provider. So logging into the mesh is logging into everything else — same username, same 2FA, same place to revoke a person.

来源

The token format gotcha. Wiring NetBird to my identity provider, the dashboard authenticated fine but API calls failed. The cause: my IdP was handing out opaque access tokens, and NetBird's dashboard needed a JWT it could actually read claims from.

来源