2024-01-26, 02:04 AM
(This post was last modified: 2024-01-26, 02:07 AM by SilveryAbaba. Edited 1 time in total.)
(2024-01-26, 01:41 AM)tmsrxzar Wrote: alright, makes sense
i can give you some testing hints, i believe the routing on the machine running all these is incorrect
basic overview guide of routing on windows is here https://www.howtogeek.com/22/adding-a-tc...ting-table
what i believe needs to happen is your machine needs a route for tailscale that tells it to only send that traffic to tailscale
since the 'automatic' split tunneling doesn't (seem to) work, it will be manual
need to add a route using 'route add' that directs all traffic from your "LAN IP" to the Tailscale Gateway Server IP VIA your LAN Gateway so that it doesn't try to send it to (or through) expressVPN
example
Lan IP 192.168.0.20
Lan Gateway 192.168.0.1
Tailscale Server 2.3.4.5
route add 2.3.4.0 MASK 255.255.255.0 192.168.0.1
it gets quite involved doing routing and it's been years since i've done it on windows but i believe this should be the path forward
Wow, that's definitely something I never would have thought to try! I added -p to make it persistent, and it didn't work with the mask, but it autofills with that anyway if you leave it out. So I did: route -p add [tailscale provided server ip] [my computer's default gateway from ipconfig] Thank you so much tmsrxzar!
Edit: Now I can't access tailscale client on the server computer on external browser or media player, but localhost still works fine, so who cares.