tailscaletom

29 ms·

1. 1.▲
   by tailscaletom 3y ago

   Yepp! Strong recommend on using systemd-resolvd, we've observed the least bugs and issues there.
2. 2.▲
   by tailscaletom 3y ago

   Userspace mode might be an option (runs without a TUN or doing any system network wiring, at the expense of performance): https://tailscale.com/kb/1112/userspace-networking/ Running Tailscale without privileg
3. 3.▲
   by tailscaletom 4y ago

   Yes. Peers added in this fashion would not have been signed by a trusted tailnet-lock key, so clients would refuse to trust them.
4. 4.▲
   by tailscaletom 4y ago

   If you're excited about tailnet lock and want to get on the alpha sooner rather than later, feel free to drop me an email. As Dave mentioned we are slowly crunching through the waitlist to get some miles in, but I'm also happy to
5. 5.▲
   by tailscaletom 4y ago

   (Tailscalar and a tailnet lock author here) If you're okay with trusting Tailscale's control plane, we have a feature for exactly this use case! Its called Device Authorization: https://tailscale.com/kb/1099&#
6. 6.▲
   by tailscaletom 4y ago

   (Tailscalar and a tailnet lock author here) Thanks for the feedback!! Writing the documentation for how this worked was a challenge, and its good to hear what pieces we need to call out more strongly in the future. If you're interested