I kind of follow what you’re putting down.
I am not using an exit node. How do I go about splitting my routes?
What I want to achieve is ‘normal’ access for within the lan, as well as remote access over tailscale for things I cannot run tailscale on.
I have a commercial VPN, but I am not connected. What tinkering did you have to do?
I set up subnet advertisements by doing tailscale set --advertise-routes=192.168.1.0/24. I did not touch ACL.
The home PC is Windows, the context menu for the tray app give the option to ‘use tailscale subnets’ which is enabled- I assume this is the equivalent of accepting advertised routes.
From the home PC, tailscale ping 192.168.1.2 returns a pong, from the tailscale IP. tracert fails.
The router is set as a subnet router, that is how I am able to access other machines on my lan remotely.
I don’t want to, and sometimes can’t, install tailscale on every device I want remote access to.
So I may have duplicate routes- Does that explain the behaviour in my original post? And how would I go about avoiding that?
I could turn off subnet routing, and only turn it on when needed, but I’ll be putting up a bunch of other services that will want to talk to each other- I’m assuming this will break whenever I turn subnet routing on.