fix: bump coder/tailscale to pick up RTM_MISS fix (cherry-pick #24187)#24214
Merged
spikecurtis merged 1 commit intorelease/2.32from Apr 10, 2026
Merged
fix: bump coder/tailscale to pick up RTM_MISS fix (cherry-pick #24187)#24214spikecurtis merged 1 commit intorelease/2.32from
spikecurtis merged 1 commit intorelease/2.32from
Conversation
github-actions
bot
added
the
community
sreya
approved these changes
Apr 9, 2026
ethanndickson
approved these changes
Apr 10, 2026
## What Bumps `coder/tailscale` to [`e956a95`](coder/tailscale@e956a95) ([PR #113](coder/tailscale#113)) to pick up the `RTM_MISS` fix for the Darwin network monitor. Already released on `release/2.31` as v2.31.8. (#24185) to unblock a customer. This PR is to update `main`. ## Why On Darwin, `RTM_MISS` route-socket messages (fired on every failed route lookup) were not filtered by `netmon`, causing each one to be treated as a `LinkChange`. When netcheck sends STUN probes to an IPv6 address with no route, this creates a self-sustaining feedback loop: `RTM_MISS` → `LinkChange` → `ReSTUN` → netcheck → v6 STUN probe → `RTM_MISS` → … The loop drives DERP home-region flapping at ~70× baseline, which at fleet scale saturates PostgreSQL's `NOTIFY` lock and causes coordinator health-check timeouts. The upstream fix adds a single `if msg.Type == unix.RTM_MISS { return true }` check to `skipRouteMessage`. This is safe because `RTM_MISS` is a lookup-path signal, not a table-mutation signal — route withdrawals always emit `RTM_DELETE` before any subsequent lookup can miss. Of note is that this issue has only been reported recently, since users updated to macOS 26.4. Relates to ENG-2394
spikecurtis
force-pushed
the
cherry-pick/24187/release/2.32
branch
from
cb69b23 to
047477c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick of #24187 onto
release/2.32This cherry-picks commit ad2415e to bring the
coder/tailscalebump (e956a95, PR #113) onto therelease/2.32branch.Context
On Darwin,
RTM_MISSroute-socket messages (fired on every failed route lookup) were not filtered bynetmon, causing each one to be treated as aLinkChange. When netcheck sends STUN probes to an IPv6 address with no route, this creates a self-sustaining feedback loop:RTM_MISS→LinkChange→ReSTUN→ netcheck → v6 STUN probe →RTM_MISS→ …The loop drives DERP home-region flapping at ~70× baseline, which at fleet scale saturates PostgreSQL's
NOTIFYlock and causes coordinator health-check timeouts.The upstream fix adds a single
if msg.Type == unix.RTM_MISS { return true }check toskipRouteMessage, which is safe becauseRTM_MISSis a lookup-path signal, not a table-mutation signal.This issue has been reported since users updated to macOS 26.4.
Relates to ENG-2394