6 ms·

NAT busting, and no key management. What extra dependencies does Tailscale have?

• nine_k 1y ago
  How do you identify yourself to Tailscale?
  • pcpuser 1y ago
    Google auth but you can run your OIDC provider if you're into that: https://tailscale.com/kb/1240/sso-custom-oidc https://tailscale.com/kb/1240/sso-custom-oidc.
  • supermatt 1y ago
    My nodes identify themselves with keys signed by the other nodes as per tailnet lock: https://tailscale.com/kb/1226/tailnet-lock https://tailscale.com/kb/1226/tailnet-lock
• akerl_ 1y ago
  Well, the dependency on Tailscale's servers, for one. You're getting that NAT-busting because Tailscale is running servers to handle that for you, and you're getting around key management by having them manage your keys and overlay their own auth layer for you.
  • pcpuser 1y ago
    So Tailscale has "extra dependencies" on Tailscale. Gotcha.
    • akerl_ 1y ago
      Tailscale is an extra dependency vs using WireGuard directly, which is what was being discussed.
  • theshrike79 1y ago
    You can always run Headscale: https://tailscale.com/opensource#encouraging-headscale https://tailscale.com/opensource#encouraging-headscale > Headscale is a re-implemented version of the Tailscale coordination server, developed independently and completely separate from Tailscale. Headscale is a project that complements Tailscale — with its own independent community of users and developers. Tailscale does not set Headscale’s product direction or manage the community, and neither prohibits nor requires employees from contributing to Headscale.
  • sampullman 1y ago
    I had a Headscale server running for a few years with no hiccups. Setup was easy, it's not too resource intensive, and you can use the normal Tailscale client.