tailscale / tailscale/tailscale

Elevated packet latency macOS → Linux, only on same LAN(?)

Open
#10,356 3 comments 0 reactions 0 assignees View on GitHub
L1 Very few needs-triage needs-triage-eng OS-macos P2 Aggravating T3 Performance/Debugging
Dominant language
Go
Stars
36.5k
Forks
3.2k
Avg merge
2d 3h
Merged PRs (30d)
123

Description

### What is the issue?

When connecting on a local network from macOS to Linux, I experience elevated packet loss, up to 15%, both for ping and ssh. Latency is not impaired--given the RTT, the packets are obviously not leaving my LAN.

The problem is specific to the Mac. When I have two Linux boxes connecting to each other, there is no packet loss. Similarly it's specific to Tailscale - while experiencing packet loss via Tailscale, concurrent connections to the local IPs are unaffected.

### Steps to reproduce

I ran ping side by side in many terminals at the same time, to both the "true" local IP address and to the Tailscale interface.

#### From Mac to Linux:

```
--- 192.168.0.2 ping statistics ---
576 packets transmitted, 576 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.561/3.593/12.269/1.604 ms
```

```
--- mana-tailscale ping statistics ---
562 packets transmitted, 498 packets received, 11.4% packet loss
round-trip min/avg/max/stddev = 2.778/11.321/1149.472/61.257 ms
```

#### From Linux to Mac

```
--- 192.168.0.15 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99143ms
rtt min/avg/max/mdev = 1.674/22.680/114.468/34.407 ms

--- hydra-tailscale ping statistics ---
100 packets transmitted, 94 received, 6% packet loss, time 99275ms
rtt min/avg/max/mdev = 3.353/8.414/101.229/16.486 ms
```

#### From a different Linux box to Linux

```
--- 192.168.0.2 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 846ms
rtt min/avg/max/mdev = 0.177/0.211/0.258/0.019 ms

--- mana-tailscale ping statistics ---
125 packets transmitted, 125 received, 0% packet loss, time 411ms
rtt min/avg/max/mdev = 0.714/2.038/108.693/9.581 ms
```

### Are there any recent changes that introduced the issue?

This has been happening for a few weeks now. Took me a while to track it down to Tailscale specifically (I first suspected degraded network hardware, but the non-Tailscale pings rule out that explanation. That's very much a compliment to the quality of your software that it was so deep into the list of hypotheses :smile:)

### OS

_No response_

### OS version

MacOS Sonoma 14.1.1, Raspbian buster, Ubuntu focal

### Tailscale version

1.54.0 on all

### Other software

This is over a wifi connection, though intuitively it feels like that shouldn't much matter given the concurrent connections are okay.

### Bug report

BUG-b7bfb2cca2685b00ef26ca6f8ce36066dbdd6f96d71d6de050d4e9ac35058039-20231121224148Z-b9ba52d3cfe6e9f6

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.