Setting up subnet routes on Linux relays

The subnet routing feature allows incremental deployment by allowing a single Tailscale agent to forward packets to entire subnets, rather than just a single machine.

For instance, a relaynode deployed on an AWS NAT Instance could provide access to all machines running on both the private and public subnets.

To define available subnets that you wish a relaynode to provide access to, use the --routes=... switch. For example, --routes=10.0.0.0/24,10.0.1.0/24 will permit access to two subnets.

Then, in the admin console, activate them by selecting the Enable Subnet Routes option in the relaynode’s entry:

Last updated