Denton Gentry
Denton Gentry
Tailscale at `HEAD` uses Go 1.20. We expect the Tailscale 1.38 release to be built using Go 1.20.
So far as I understand: - the problem was that Go apps prior to Go 1.20 would read /etc/resolv.conf for nameservers - the App Store Tailscale.app runs within a sandbox...
When we have news to report we will update this issue. I understand that there is interest in this feature request.
I believe the ACL described in https://github.com/tailscale/tailscale/issues/5692#issuecomment-1298447249 is the reason for this behavior.
> Thank you so much for your help! It turns out my issue was that my Tailscale and Ethernet interfaces were not in the same zone (in fact they weren't...
https://github.com/tailscale/tailscale/issues/5783 has more context and brainstorming about solutions. Dup of https://github.com/tailscale/tailscale/issues/5783
At this point I don't expect to be able to diagnose what was happening last August. If it happens again please reopen the bug and attach a fresh bugreport.
Possibly relevant: after this feature request was filed, the [Tailscale Funnel feature became available in alpha release](https://tailscale.com/blog/introducing-tailscale-funnel/).
Implementation of this feature has begun in earnest.
Simultaneous operation on multiple tailnets (https://github.com/tailscale/tailscale/issues/183) is substantially harder, and is not being attempted in this round of development. As one example, the tailnets could offer routes to subnets or...