2024-09-30, 02:08 PM
The LAN networks field is simply for determining what clients are "remote" and which ones are "local". Making this distinction is important for two reasons: If a client is "remote" (not in the LAN list) and you disabled remote connections they would be blocked, and for bit rate throttling for "remote" clients whereas local clients don't have any bit rate restrictions.
If you have physically remote clients, but you've defined their address space in LAN Networks (which we did for tailscale), those physically remote clients are now considered local. They are allowed to connect, even if remote connections is disabled, and no bit rate restriction is applied.
I'm not sure if the service discovery function will be broadcast on tailscale. I'm pretty sure that will only work on your actual LAN.
I'm not a Tailscale expert, so I may be missing something if the issue is with the Tailscale config.
If you have physically remote clients, but you've defined their address space in LAN Networks (which we did for tailscale), those physically remote clients are now considered local. They are allowed to connect, even if remote connections is disabled, and no bit rate restriction is applied.
I'm not sure if the service discovery function will be broadcast on tailscale. I'm pretty sure that will only work on your actual LAN.
I'm not a Tailscale expert, so I may be missing something if the issue is with the Tailscale config.