Navigating the world of self hosting brings incredible freedom, but unlocking seamless remote access to your entire home lab can be tricky. Tailscale often feels like magic, effortlessly connecting your devices. However, many users hit a wall when trying to reach services on their NAS or other private network devices that don’t run Tailscale directly. This common hurdle often leads to misdirected attempts with exit nodes. This guide will clarify the crucial distinction between Tailscale exit nodes and subnet routers, empowering you to truly master remote access solutions for your self-hosted setup.
Tailscale Exit Nodes: About Internet Traffic
Tailscale is an Overlay Network First
When you first set up Tailscale and add devices, it acts as an overlay network. It connects these devices running Tailscale to each other and leaves everything else alone, meaning your browsing, streaming, and app traffic still goes out whatever internet connection you’re on. It’s why your phone that’s connected to your tailnet can reach the other devices on it but not the printer that isn’t part of that network.
An exit node changes how your internet traffic leaves your device, not necessarily which home devices it can reach. When you use a device as an exit node, your device will send all of its traffic through that machine, so websites and apps will see your home IP address instead of whatever network is actually giving you connection to the internet. In practice, it works similarly to a traditional VPN with a server you own, which can absolutely be useful for network security and privacy, but it doesn’t aim your connection directly at the devices in your home that aren’t part of your tailnet.
Subnet Routing: Your Gateway to the Entire Home Network
Tailscale Has This Functionality Built-In, Too
If you’re trying to reach devices on your home LAN, subnet routers are the better way to do it. A lot of users mistake the "Allow local network access" toggle for an exit node for a switch that allows them to access their home LAN, but that switch affects the network your device is currently on, like the coffee shop or hotel Wi-Fi.
A subnet router is a device on your tailnet that advertises a range of local addresses—the normal 192.168.x.x type—and forwards traffic to that range for everything else in your tailnet. This lets Tailscale reach devices that don’t run Tailscale without changing the way your internet traffic is routed. This is obviously good for devices that you haven’t installed Tailscale on, but it’s the perfect solution for devices that can’t install it at all, like a printer or many smart home gadgets in your home lab.
Setup only takes a few minutes: you will need a device on your network that will always be on, like a Raspberry Pi or a small Linux VM or LXC. You can run Tailscale on it with the --advertise-routes flag with your home subnet, and then you approve the route in your Tailscale admin console. Windows, macOS, iOS, and Android clients will pick up the new route automatically. For Linux, it needs the --accept-routes flag before it can use the routes other devices advertise.
A small pitfall that’s worth looking out for is which local address space your router uses. For most people this will be the standard 192.168.0.x space, but if your home LAN and network you’re connecting from both use that same space, your device won’t be able to tell local addresses from remote ones. If you’re setting this up, moving your home network to a less common range (e.g., 10.0.0.0/8 or 172.16.0.0/12) does prevent headaches like this later, especially when dealing with multiple networks during travel.
Sometimes You Don’t Need Either
Exit Nodes and Subnet Routers Might Be Overkill
Before setting up a subnet router, it’s worth checking to see if the device you want to reach can run Tailscale itself. If it can, installing it directly is just the cleanest option. Each device gets its own address and MagicDNS name, which is a lot simpler to work with than multiple subnets. Tailscale also runs natively on a surprising number of devices. It offers official apps for Synology, QNAP, TrueNAS, Unraid, and more. If it’s a desktop or it can run Linux, you’re pretty much good to go for NAS access and other server management.
What to Actually Use Exit Nodes For
They’re Very Useful in Specific Circumstances
When traveling or working remote, exit nodes can come in handy. On untrusted networks, routing everything through your home network can be a sensible precaution, bolstering your network security. Using them as a way to get around geolocation restrictions is another underrated use case. For services that only work in your country of origin, like banking or streaming, an exit node does that for you. And for someone brand new to Tailscale, picking an exit node from a menu is undeniably easier than advertising routes and approving them in a web console.
Accessing Your Home Network Doesn’t Have to Be Complicated
If Tailscale is already connecting your phone and computer, you’re most of the way there. Installing it directly on the devices you need access to should be primary method, but for something like a printer or smart home device that can’t run it natively, subnet routing is the next best thing. Exit nodes are best saved for when you want your traffic to look like it’s coming from home.
FAQ
Question 1: What's the fundamental difference between Tailscale exit nodes and subnet routers for self-hosters?
Answer 1: Exit nodes primarily route *all your internet traffic* through a device on your tailnet, making it appear as if you're browsing from that location (e.g., your home IP). Subnet routers, on the other hand, allow your Tailscale-connected devices to access *non-Tailscale devices on your local area network (LAN)*, like a printer or an IoT device, without rerouting your general internet traffic. For self-hosters aiming for **remote access solutions** to their entire home lab, subnet routers are usually the correct choice.
Question 2: Can Tailscale subnet routing securely access smart home devices or printers without native Tailscale support?
Answer 2: Yes, absolutely! This is one of the primary benefits of using a subnet router. By having a device on your tailnet (like a Raspberry Pi or a NAS) advertise your home LAN's subnet, all your Tailscale-connected devices can then reach any device on that local network, including smart home hubs, network printers, or IP cameras, even if those devices cannot install Tailscale directly. This greatly enhances your **home lab** capabilities.
Question 3: What's a niche but powerful use case for Tailscale exit nodes beyond basic IP spoofing?
Answer 3: A powerful, albeit niche, use case for exit nodes is maintaining digital continuity for services tied to your home network. For instance, if you have a **self hosting** setup that relies on local DNS resolution or specific network conditions within your home to function correctly (e.g., internal APIs, license servers), an exit node ensures your remote device operates within that familiar network context, simplifying troubleshooting and enhancing application compatibility while traveling.