Get started
© 2024

Exit nodes (route all traffic)

Exit nodes are available for all plans.

Exit nodes capture all your network traffic. To configure Tailscale to only route specific subnets (the more common configuration), refer to subnet routers instead.

The exit node feature lets you route traffic through a specific device on your Tailscale network (known as a tailnet). The device routing your traffic is called an exit node. There are many ways to use exit nodes in a tailnet. For example, you can:

Routing app traffic?

Consider using an app connector to route traffic for a specific application. App connectors let you control device and user access to your third-party applications, without requiring any end-user configuration.

How exit nodes work

By default, Tailscale acts as an overlay network: it only routes traffic between devices running Tailscale, but doesn't touch your public internet traffic, such as when you visit Google or Twitter. The overlay network configuration is ideal for most people who need secure communication between sensitive devices (such as company servers or home computers), but don't need extra layers of encryption or latency for their public internet connection.

A diagram showing four devices in a Tailscale overlay network. A laptop is making a direct connection to

However, there might be times when you want Tailscale to route your public internet traffic. For example, you might want to route all your public internet traffic if:

  • You're in a coffee shop with untrusted Wi-Fi.
  • You're traveling overseas and need access to an online service (such as banking) only available in your home country.
A diagram showing four devices in a Tailscale overlay network where one is highlighted in blue and designated as an exit node. The laptop makes its connection to through the Desktop device designated as an exit node.

You can route all your public internet traffic by setting a device on your network as an exit node. When you route all traffic through an exit node, you're effectively using default routes (, ::/0), similar to how you would if you were using a typical VPN.

Configure an exit node

Use the following steps to configure an exit node:

  1. Install the Tailscale client.
  2. Advertise the device as an exit node.
  3. Allow the exit node.
  4. Use the exit node.

You can also get a suggested exit node.


Before you can configure an exit node, you must:

  • Set up a Tailscale network, called a tailnet.
  • Ensure both the exit node and devices using the exit node run Tailscale v1.20 or later.
  • Ensure the exit node is a Linux, macOS, Windows, or Android device.
  • Ensure you allow (intended) users to use the exit node.

If your tailnet is using the default ACL, users of your tailnet already have access to any exit nodes that you configure. If you have modified your ACL, ensure you create an access rule that includes exit node uses in the autogroup:internet. They do not need access to the exit node itself to use the exit node.

The following example configuration to add to your ACL that allows all users access to the internet through an exit node:

// All users can use exit nodes
// If you are using the default ACL, this rule is not needed because the
// default ACL allows all users access to the internet through an exit node
{ "action": "accept", "src": ["autogroup:member"], "dst": ["autogroup:internet:*"] },

For security purposes, you must opt-in to exit node functionality. For example:

  • Every device must explicitly opt-in to using an exit node.
  • A device must advertise that it's willing to be an exit node.
  • An Owner, Admin, or Network admin must allow a device to be an exit node for the network.

Install the Tailscale client

Download and install Tailscale onto the exit node machine. Each of the three macOS variants supports running an exit node.

There are three ways to run Tailscale on macOS. This document only applies to the macOS App Store and Standalone (GUI) versions. If you use tailscaled on macOS, use the Linux instructions.

From the Tailscale client installed on the device you plan to use as an exit node, select Exit Node > Run Exit Node.

If the device is authenticated by a user who can approve exit nodes in autoApprovers, the exit node will automatically be approved.

Allow the exit node from the admin console

This step is not required if you use autoApprovers.

You must be an Admin to allow a device to be an exit node.

  1. Open the Machines page of the admin console and locate the exit node.
  2. Locate the Exit Node badge in the machines list or use the property:exit-node filter to list all devices advertised as exit nodes.

From the ellipsis icon menu of the exit node, open the Edit route settings panel, and enable Use as exit node.

Use the exit node

Each device must enable the exit node separately. The instructions for enabling an exit node vary depending on the device's operating system.

You can use an exit node from the menu bar. Open the Tailscale menu and select Exit Nodes. (If you are running a Tailscale client version earlier than v1.60.0, the menu string to select is Use exit node.) Then, select the machine name of the exit node to use.

To allow direct access to your local network when routing traffic through an exit node, select Allow Local Network Access.

The option to use an exit node only displays if there's an available exit node in your tailnet.

You can verify that your traffic is routed by another device by checking your public IP address using online tools. You should see the exit node's public IP rather than your local device's IP.

You can turn off routing through an exit node by selecting None from the Exit Node drop-down.

Destination logging in network flow logs

Destination Logging is available for Enterprise.

Tailnets on the Enterprise plan can enable destination logging for exit nodes.

By default, destination logging is disabled for traffic flowing through an exit node across all tailnets, for privacy, abuse, and security purposes. Tailnets on the Enterprise plan can, however, enable destination logging across the tailnet for increased visibility of traffic across the tailnet and forensic analysis during security incidents. Destinations are logged in Network flow logs.

You must enable Log Streaming before using exit node destination logging.

To enable destination logging for exit nodes:

  1. Navigate to the Logs page in the admin console.
  2. Select Network flow logs.
  3. Select the Logging Actions menu, then select Enable exit node destination logging.

To disable destination logging for exit nodes:

  1. Navigate to the Logs page in the admin console.
  2. Select Network flow logs.
  3. Select the Logging Actions menu, then select Disable exit node destination logging.


Tailscale support for running exit nodes on macOS is new and still undergoing optimization. macOS exit nodes are limited to userspace routing and require you to prevent your device from sleeping to maintain a connection.


On macOS, the exit node is implemented in userspace, which differs from the default Linux exit node implementation and is not as mature or fully optimized. For details, refer to Kernel vs. netstack subnet routing & exit nodes.


When running an exit node, you currently must prevent the computer from going to sleep if you want the exit node to remain available.

In macOS System Preferences, under Energy Saver, select Prevent computer from sleeping automatically when the display is off.