Comment on Classification need with Tailscale, remote access, and local access.
gazter@aussie.zone 5 days agoI 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.
just_another_person@lemmy.world 5 days ago
Tailscale is a group of clients on a Tailnet which are all equal, unless you tell it otherwise. That means you need to set the client you installed on your router as a subnet router.
Even then, if you’re not familiar with networking, you’ll probably have duplicate routes if you’re not paying attention. The other option is to just install Tailscale on each server you want access to.
gazter@aussie.zone 5 days ago
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.
Onomatopoeia@lemmy.cafe 2 days ago
Just verifying, after enabling subnet routing, did you create the routes (it’s in the docs for subnet router).
I have the same problem you do - for some reason TS will “steal” the route, even when correctly configured.
just_another_person@lemmy.world 5 days ago
Yes, if Tailscale on your router is advertising routes, and your other devices while connected to Tailscale are picking up those advertised routes, they won’t be able to figure out how to get to your local network devices if both things are advertising the same routes.