monorailmedic
Occasional Visitor
That may well be the case - so then we still end up with the core issue of "why doesn't this work?"My
My understanding (at least in user mode) is that when you connect to devices on the local lan from the tailnet, it appears to the device to be coming from the router ip, not some new vpn subnet like the other vpn servers do. So if the tailnet process initiates the outbound connection to the tailnet, this whole scheme eliminates any need to touch iptables.
I'm remoted into a box on the network in question and I can't reach anything on the tailnet. Devices connected to Tailscale via any other connection can see each other, admin shows the router in question as connected. The red flag (beyond simply not working) is that --status always shows the router as idle.