tailscale: No internet connectivity when using Mullvad as exit node

What is the issue?

When I have a Mullvad exit node selected, I lose internet connectivity. Disabling exit nodes fix the issue and I’m able to resolve network requests again.

This is the output of tailscale status while the Mullvad exit-node is enabled:

~ $ tailscale status
100.___.___.___    elliots-macbook-air-1 elliotdohm@  macOS   -
100.___.___.___    ca-tor-wg-001.mullvad.ts.net tagged-devices         active; exit node; direct 178.249.214.2:51820, tx 61544 rx 536
100.___.___.___    redacted             elliotdohm@  linux   -
100.___.___.___    redacted             elliotdohm@  android offline
100.___.___.___    redacted             elliotdohm@  linux   active; offers exit node; direct 192.168.1.33:41641, tx 9128 rx 16840

Eg. ping output when Mullvad exit nodes are enabled:

~ $ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26

...

--- 1.1.1.1 ping statistics ---
89 packets transmitted, 0 packets received, 100.0% packet loss

Steps to reproduce

Enable Tailscale, observe network requests resolving as expected
Enable a Mullvad exit node (eg. in my case I chose Toronto)
Wait 30s or so to let things propagate
Notice that network requests no longer resolve

Are there any recent changes that introduced the issue?

Recently updated to Tailscale 1.54.0. Did not have this problem on the previous version.

OS

macOS

OS version

Sonoma 14.0

Tailscale version

1.54.0

Other software

No response

Bug report

BUG-e4f48117206c116af5374318582ed9bc4fd0fcca68c7e41ad5a7cb2feb44daf3-20231118190318Z-0aac8eb665fd528d

About this issue

Original URL
State: open
Created 7 months ago
Reactions: 2
Comments: 20 (1 by maintainers)

Most upvoted comments

Had the same issue described the last few days. Like @patosullivan, removing this device in the Tailscale Mullvad settings page and adding it again did not resolve my issue.

Today I noticed though that while the Tailscale macOS app said ‘Device key expires in 5 months’, the Machines settings page in the admin console said that the key for the device had expired ‘1 day ago’ (curiously, I had recently tried to resolve the problem by doing ‘Reauthenticate’ via the macOS app in the last few days, so not sure why it had expired). That weird inconsistency prompted me to try removing the machine and adding again, then adding to Tailscale Mullvad settings again, too. That has resolved my issue.

huwmartin on Dec 20, 2023

I have the same issue on Windows 11 with Tailscale version 1.54.1 No custom firewall, regular Mullvad works fine when installed.

I’ve tried the following, none of which fixed things:

enabling local LAN access, setting a global DNS override (to multiple DNS options) , with both, and with neither

unregistering the device and re-registering

restarting tailscale between making these changes

choosing different mullvad exit nodes

waiting a longer period of time after enabling

When a mullvad exit node is enabled, all external connectivity is disabled (including to other tailscale nodes). When the exit node is removed, connectivity is restored.

#> tailscale status 100..._ _ @ windows - 100... _ @ android offline 100... ca-mtr-wg-001.mullvad.ts.net tagged-devices active; exit node; direct 146.70.198.66:51820, tx 444 rx 0 100..._ _ @ android offline 100... _ _@ android -

Sounds exactly like what I’m seeing on macOS.

patosullivan on Dec 7, 2023