Comment on Classification need with Tailscale, remote access, and local access.
gazter@aussie.zone 5 days agoI 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.
rtxn@lemmy.world 5 days ago
That’s unfortunate, I have no idea how Tailscale does routing on Windows. Try running the client without accepting any subnet advertisements.
I’ve also found this: tailscale.com/kb/1023/troubleshooting#lan-traffic… The solution might be to advertise a larger subnet (e.g. 192.168.1.0/23) to make the route advertisements on the tailnet less specific than on the LAN. Advertising a larger subnet won’t cause any additional issues because it’s in a private IP range.