Skip to content

Accept service routes and allow other tunnels - #5

Open
vkz wants to merge 2 commits into
tailscale:mainfrom
vkz:service-routing
Open

vkz wants to merge 2 commits into
tailscale:mainfrom
vkz:service-routing

Conversation

@vkz

@vkz vkz commented Aug 5, 2026

Copy link
Copy Markdown

NB: I patched it for myself in the fork - enough for me. Please close if unwanted or redo - I don't need credit. My usecase maybe too weird 🤷

Problem

Machine:

  • Mac not on tailnet and can't be because IP ranges conflict with Cloudflare ;
  • must be able to reach Tailscale services yes services not just nodes.

Issues with upstream ts-unplug-proxy:

  • on Mac tsnet auto binds en0 ignores (correctly) utun0 to avoid looping, but
  • it is being wrong when you know for sure it is a different overlay with default route. Must be an opt-in switch to allow when you know what you're doing.
  • wasn't accepting advertised service routes;
  • strange name resolution where it tried to be clever and resolve to host not service on conflict instead of consulting TS DNS.

Summary

  • Add -disable-interface-binding an opt-into competing tunnels like Cloudflare WARP.
  • Add opt-in -accept-routes.
  • Prefer Tailscale DNS over peer aliases so Service VIPs resolve correctly.

CLOSE me if don't care

vkz added 2 commits August 5, 2026 16:15
Support macOS environments with competing tunnel interfaces and preserve Tailscale Service VIP resolution.
The narrower macOS binding workaround left tsnet unable to reach tailnet peers when another tunnel controlled route selection. Restore the network namespace bypass while retaining Service VIP resolution and bounded dials.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant