Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fix: never use STUN latency for DERP region netcheck #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 31, 2023

Conversation

deansheather
Copy link
Member

Changes the STUN probe to still run as usual, but avoid storing the latency in the region report. This was causing Google STUN to artificially make the default region have an extremely low latency.

Also fixes HTTPS latency check to work on ForceHTTP nodes.

Changes the STUN probe to still run as usual, but avoid storing the
latency in the region report. This was causing Google STUN to
artificially make the default region have an extremely low latency.

Also fixes HTTPS latency check to work on ForceHTTP nodes.
@deansheather deansheather merged commit b5a9b1b into main Jul 31, 2023
@deansheather deansheather deleted the dean/never-use-stun-latency branch July 31, 2023 10:50
deansheather added a commit that referenced this pull request Jul 31, 2023
Changes the STUN probe to still run as usual, but avoid storing the
latency in the region report. This was causing Google STUN to
artificially make the default region have an extremely low latency.

Also fixes HTTPS latency check to work on ForceHTTP nodes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants