Description
I'm using a custom Tailscale coordination server (Headscale) at https://example.com. I need to forward local port 127.0.0.1:3900 to remote host server.com:3900 through Tailscale, with all traffic routed via a specific exit node exit-node1.
ts-proxy currently lacks the ability to specify:
- The coordination server URL (to work with Headscale).
- An exit node to route traffic through.
What I tried
- Set
TS_CONTROL_URL=https://example.com and used -exit-node exit-node1, but ts-proxy does not recognize these (see help output).
- Used
TS_AUTHKEY (generated from Headscale), but without --control-url the connection fails.
Expected behavior
ts-proxy should support:
- A
--control-url flag (or TS_CONTROL_URL environment variable) to specify an alternative coordination server.
- A
--exit-node flag (or similar) to select an exit node, like in the original tailscale and tailsocks.
Description
I'm using a custom Tailscale coordination server (Headscale) at
https://example.com. I need to forward local port127.0.0.1:3900to remote hostserver.com:3900through Tailscale, with all traffic routed via a specific exit nodeexit-node1.ts-proxycurrently lacks the ability to specify:What I tried
TS_CONTROL_URL=https://example.comand used-exit-node exit-node1, butts-proxydoes not recognize these (see help output).TS_AUTHKEY(generated from Headscale), but without--control-urlthe connection fails.Expected behavior
ts-proxyshould support:--control-urlflag (orTS_CONTROL_URLenvironment variable) to specify an alternative coordination server.--exit-nodeflag (or similar) to select an exit node, like in the originaltailscaleandtailsocks.