Strange exit node behaviour in Ubuntu 18.04 LTS


I’ve submitted a ticket however haven’t heard back so I figured I’d try my luck here in the interim.

We’ve been using exit nodes without any issues for a few months now. We’re in the midst of on boarding some staff who run Ubuntu 18.04 LTS however we’re running into issues with the exit nodes.

We’re using the latest version from the repository provided for Ubuntu 18.04 LTS. When we tell TailScale to use an exit node all internet connectivity seizes. When looking at the machine itself it appears it sets the default route properly however it can’t reach anything (, 100.x.x.x).

I’ve tested this in a fresh Ubuntu 18.04 LTS VM with the same results:

  1. Download and install TailScale via the repositories here: Download · Tailscale

  2. Authenticate as normal with tailscale up

  3. Utilize an exit node with tailscale up --exit-node=100.x.x.x --shields-up

  4. Internet connectivity seizes

Some notes:

  • I’ve tested this with several exit nodes we use in production and work flawlessly in MacOS & Windows
  • The ACL’s are configured properly. To verify it wasn’t a mistake I made a broad ACL rule and the behaviour still exists:
  { "action": "accept", "src": ["autogroup:members"], "dst": ["autogroup:internet:*"] }

I’ve generated a bug report as well: BUG-1f6760fb72dcfec98a40064156da46aa638ab4b34532d10455e94910bc6e993c-20220810134835Z-6239e1d05a7935d5

Any advice on how to debug this further would be fantastic.


Replying to this to confirm it’s a bug on Ubuntu 18.04 LTS. TailScale has opened a GitHub issue to track this here for anyone it affects: Ubuntu 18.04 has no connectivity through an exit node · Issue #5409 · tailscale/tailscale · GitHub