You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My PC is on a network that has a Tailscale subnet router that provides access to all the devices on the network. I connect to the Tailscale network from my iOS device, which can then directly access the PC, but comes from the 100.64.0.0/10 network block (which is what Tailscale uses by default). Sunshine doesn't recognize that this is "on my network" since it isn't a traditional internal address block. It then tries to do the port mapping, but fails since there is no firewall in between.
I'd like to be able to somehow specify that the 100.64.0.0/10 address block should be treated as an internal direct connection.
Current workarounds:
use the subnet router as an exit node so that the traffic reaching the PC looks local, but that adds a little bit of latency and messes up access to some other things that are served directly from that exit node.
Install Tailscale on the gaming pc and connect it directly to Tailscale. Trying to avoid that for management reasons given that it is already accessing the tailnet just fine otherwise and to avoid having the gaming PC needing to do all the encrypting/decrypting of traffic.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Feature Request
Body
My PC is on a network that has a Tailscale subnet router that provides access to all the devices on the network. I connect to the Tailscale network from my iOS device, which can then directly access the PC, but comes from the 100.64.0.0/10 network block (which is what Tailscale uses by default). Sunshine doesn't recognize that this is "on my network" since it isn't a traditional internal address block. It then tries to do the port mapping, but fails since there is no firewall in between.
I'd like to be able to somehow specify that the 100.64.0.0/10 address block should be treated as an internal direct connection.
Current workarounds:
Beta Was this translation helpful? Give feedback.
All reactions