Skip to content
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

fix: plan v4/v6 STUN probing based on relative index #43

Merged
merged 2 commits into from
Nov 6, 2023

Conversation

spikecurtis
Copy link

I'm still noticing some instability and my agent isn't probing STUN regions, and therefore failing netchecks.

I've noticed a bug in our planning, introduced with my previous change. The choice of number of probes and v4 vs v6 for the probes was being computed based on the sorted speed index, rather than the relative index of only STUN regions. So, if the first STUN region wasn't in the top 3 by speed, it could only get a single try and/or only v6 probes. In pathological cases, you could end up with only v6 probes and no v4 probes.

@spikecurtis spikecurtis merged commit ba3acaa into main Nov 6, 2023
32 of 35 checks passed
spikecurtis added a commit to coder/coder that referenced this pull request Nov 7, 2023
Fixes STUN probe issues on dual stack systems by incorporating coder/tailscale#43
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