tailscale: Set Default Exit-Node Policy

What are you trying to do?

When a tailscale client connects to a tailnet, the tailscale client gets the policy define in the admin console. Then the client applies rule to itself. Client ACL needs to be managed outside of this.

How should we solve this?

After a tailscale client authentic/verified authentication and downloads tailnet client list, tailscale client downloads tailnet exit-node policy. Tailnet admins can lock clients to specific node or not using an exit node. Tags are used for filtering. Most exact wins.

Example of exit-node policy in XML. Root exitNodePolicy is default for the tailnet:

<exitNodePolicy userLocked="false" >
    <exitNode weight=1>device-name-1</exitNode>
    <exitNode weight=2>device-name-2</exitNode>
    <exitNodePolicy userLocked="true" tags="limited-devices" >
        <exitNode weight=1>device-name-3</exitNode>
        <exitNode weight=2>device-name-4</exitNode>
    </exitNodePolicy>
</exitNodePolicy>

Initial tailnet exit-node policy: <exitNodePolicy userLocked="false" />

What is the impact of not solving this?

Tailnet admins can’t automatically apply exit-node policies across a tailnet systematically.

Anything else?

Also talked about on reddit: https://www.reddit.com/r/Tailscale/s/rbYJc6CAqs

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 12
  • Comments: 20 (4 by maintainers)

Most upvoted comments

unclear if MDM will support the suggest keyword or MDM will continue to only allow a single node ID

@mrbluecoat we’re working on it! coming soon, with some advanced configurations options available via MDM. Keep following the change log for updates.

The main issue here is it doesn’t support Linux, which is a requirement for me. I’m a home user with about 25ish devices that would need tailscale. Some for exit nodes and others for mobile/laptop. This is a bit big for configuring each separately but I don’t also have an MDM either.

It seems like you want to deploy a default and not a forced value, and it seems like you want to do this using ACLs… that said, if you’re deploying Tailscale to a fleet of devices using MDM, we offer a system policy on Windows, macOS, iOS, and Android that allows you to force the use of a given exit node: https://tailscale.com/kb/1315/mdm-keys#force-an-exit-node-to-always-be-used

I set up an exit node for the first time and was surprised I had to manually assign it in my android client app.

Would be great if we could use the admin web interface to force the use of an exit node by default, or for specific clients