fix: move STUN servers into their own regions #9030
Merged
Conversation
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.
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.
Tailscale only tries a single STUN server in each region before cancelling all other pending STUN requests and moving on. This is usually fine, but in the case of "hard NAT" tailscale needs to get responses from two STUN regions to know that the public IP is variable and it should deploy countermeasures to get direct working.
This moves the STUN nodes out of the default region and into a new region for each STUN server starting at region ID 999+1. This should allow connections behind "hard NAT" to upgrade to direct (although this will take a bit longer, about 5-30s).
Also updates the default STUN server list to include every Google STUN server so clients have a lot to pick from. On the first netcheck, only a single STUN server will be pinged. On subsequent checks, others will be pinged to check for variability.