A traveler uses a laptop in a hotel room as a cloud network connects to home devices and the internet.
Tailscale feels like magic until you try to open your NAS dashboard or a security camera feed from a hotel room and nothing loads. The usual forum advice is to turn on an exit node. That's often the wrong tool. An exit node and a subnet router solve different problems, and picking the right one saves you a lot of head-scratching.

A traveler uses a laptop in a hotel room as a cloud network connects to home devices and the internet. The short version​

  • Install Tailscale directly on the device you want to reach, if it supports it.
  • Use a subnet router for devices that can't run Tailscale, such as printers, IP cameras and smart home hubs.
  • Use an exit node when you want your internet traffic to leave from another location, such as your home connection.

What an exit node actually does​

By default Tailscale is an overlay network. Tailscale injects routes into client routing tables so traffic reaches the correct destination for the features you've set up. Tailscale's own documentation describes the baseline as one that only routes traffic between devices running Tailscale and leaves your public internet traffic alone. Your web browsing, streaming and app traffic keep using whatever connection you're on.

An exit node changes that. When you route everything through one, you're effectively using default routes (0.0.0.0/0 and ::/0), much like a conventional VPN. Tailscale's documentation lists these example uses:

  • Protecting yourself on untrusted coffee-shop Wi-Fi.
  • Reaching an online service, such as banking, that's only available from your home country while you travel.

The exit node is also opt-in at several levels. The device must advertise itself, and an Owner, Admin or Network admin must allow it. Each client must also choose to use it.

The practical upshot is that sites see your home IP address. That doesn't make your printer or camera show up. Devices that don't run Tailscale still aren't part of your tailnet.

The "Allow Local Network Access" trap​

This setting causes a lot of confusion. While a client uses an exit node, it can't reach its own local network by default. The Allow Local Network Access option (the --exit-node-allow-lan-access flag on the command line) lifts that restriction. It applies to the network you're currently sitting on, such as the hotel or café, and not to your home LAN.

Tailscale also warns you to enable it only on networks you trust. You might trust your home network. You wouldn't trust a public hotspot.

Subnet routers: the right tool for the LAN​

A subnet router is a Tailscale device that advertises routes to private subnets it can reach. Tailscale says this is for cases where you can't install the client on every device on a physical network. Its home-use guide names IP cameras, smart home hubs, printers and network switches as typical examples.

Setup steps​

  1. Pick an always-on device on your home network. It needs to run Tailscale. Tailscale's guide says any device on the local network running the client can do the job. Linux, Windows, macOS and Apple TV are listed.
  2. Enable IP forwarding if the router is a Linux machine. Tailscale's subnet router setup guide shows this using sysctl settings for IPv4 and IPv6 forwarding.
  3. Advertise your home subnet. Tailscale's Windows example, run from an Administrator PowerShell prompt, is tailscale up --advertise-routes=192.168.1.0/24. Replace that example prefix with your real network. The current Linux docs use tailscale set --advertise-routes= for the same purpose.
  4. Approve the route. In the admin console, open the Machines page and find the router. Select Edit route settings, enable the routes you want and save. A policy-based autoApprovers setting can also approve routes automatically.
  5. Connect from elsewhere. The remote device needs Tailscale and must be signed into the same tailnet. Then you can use the target's normal private address, such as a camera at an address like 192.168.1.50.

Client behavior by platform​

Tailscale's tailscale up documentation says Windows, iOS, Android, the macOS App Store variant, and the macOS standalone variant accept routes by default. Its route-injection page also lists tvOS as accepting routes by default. Linux needs tailscale set --accept-routes, and the personal-use guide also shows sudo tailscale up --accept-routes. Windows users generally don't need to change anything once the route is approved.

Why a route can exist and still not work​

Plenty of people approve the route and then wonder why the connection fails. Tailscale treats routing and access control as separate layers. The route-injection page puts it this way: Grants control packet filtering, while routes are injected based on what subnet routers advertise and what the control plane approves. You need both a route and a rule that permits the traffic. You can have a route that gets blocked by policy. You can also have policy permission with no route to carry the packets.

If a route is present but traffic fails, check these things:

  • The destination is reachable from the subnet router itself.
  • Firewalls on the router or the target aren't blocking it.
  • A grant or ACL permits the traffic.
  • On Linux, RouteAll is true in tailscale debug prefs. If it's false, run tailscale set --accept-routes.
  • A more specific local route isn't taking precedence on the client.

Tailscale's LAN troubleshooting page adds a useful reminder. Rule out ordinary problems first, such as firewall rules, IP conflicts and DHCP errors. Try the connection with Tailscale disconnected.

Also watch for key expiry. Tailscale documents that when a connector's key expires, such as a subnet router's, the advertised routes stay configured on other devices but become unreachable. To avoid surprise outages, disable key expiry on the router or set up high availability.

The overlapping address problem​

The most common pitfall is address overlap. Suppose your home network is 192.168.1.0/24 and the café network you're sitting on uses the same range. Your device can't tell which one you mean.

Tailscale's documentation says Windows and macOS prioritize the most specific route (longest prefix match). Linux adds policy routing on top, which complicates things.

Options, from most to least invasive:

  • Renumber your home network to a less common range. That prevents the clash, but it affects every statically configured device, so don't treat it as a first troubleshooting step.
  • Use 4via6 subnet routing. Tailscale documents it for overlapping IPv4 subnets. It maps each IPv4 subnet to a unique IPv6 route generated with tailscale debug via.
  • Advertise a less specific route on a fixed network. Tailscale's docs describe advertising 192.168.2.0/23 to cover a 192.168.2.0/24 LAN. They caution against using this on non-fixed interfaces like laptop Wi-Fi.

A related quirk affects devices that share a LAN with the subnet router. If they also run Tailscale and accept routes, local traffic can detour through the tailnet. Tailscale's docs say you can stop this by passing --accept-routes=false on those devices. Community notes on GitHub describe the same fix, but treat those as informal guidance and not vendor documentation.

Do you even need a subnet router?​

Maybe not. Tailscale lists official apps for Synology, QNAP, TrueNAS SCALE and Unraid. Its NAS page says a subnet router is a device in your tailnet that you use as a gateway to advertise routes to other devices. For a NAS with an official app, though, installing Tailscale directly is simpler. Each device then gets its own tailnet address. FreeBSD and FreeNAS support is community-maintained, not an official app.

You also don't necessarily need a Raspberry Pi or a dedicated VM. Any always-on device on the LAN that can run Tailscale can do the job. A small Linux box is a popular choice because it's cheap and quiet, but that's a convenience, not a requirement.

Where exit nodes still shine​

Exit nodes are good at what they were built for:

  • Routing traffic through a trusted network when you're on untrusted Wi-Fi.
  • Appearing to be in your home country when you travel.
  • For managed fleets, forcing devices through an exit node via system policies deployed with MDM.

They're also easy to use. Picking one from a menu is simpler than advertising and approving routes. Tailscale itself notes that exit nodes route all your network traffic, which is often not what you want. It points to subnet routing as the more common configuration.

Bottom line​

Ask what you're trying to reach. If the device can run Tailscale, install it there. If it can't, advertise its subnet through a router and approve the route. If you want your traffic to appear to come from home, use an exit node. Exit nodes, subnet routers and direct installs can coexist in one tailnet.

 

References

  1. You don't need a Tailscale exit node just to reach devices on your home network XDA 2026-10-31T17:00:20+00:00
  2. Exit nodes (route all traffic) · Tailscale Docs tailscale.com
  3. Route traffic · Tailscale Docs tailscale.com