Skip to content

feat: support bundle: automatically diagnose STUN issues in network support bundle #12165

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

Closed
Tracked by #12160
johnstcn opened this issue Feb 15, 2024 · 3 comments · Fixed by #12951
Closed
Tracked by #12160

feat: support bundle: automatically diagnose STUN issues in network support bundle #12165

johnstcn opened this issue Feb 15, 2024 · 3 comments · Fixed by #12951
Assignees

Comments

@johnstcn
Copy link
Member

johnstcn commented Feb 15, 2024

Part of #12160

The support bundle includes a netcheck report.
We can potentially automatically diagnose STUN issues by checking the netcheck output:

  • Is there at least one configured STUN server,
  • Can we reach all configured STUN servers,
  • Does the address detected by STUN vary by STUN region (Hard NAT)
@johnstcn
Copy link
Member Author

@spikecurtis @deansheather are there other things we should be looking for w.r.t. STUN programmatically?

@spikecurtis
Copy link
Contributor

With respect to STUN, the main things to know are

a) whether we can reach the configured STUN servers (or, that there are no configured STUN servers)
b) whether the detected address varies by STUN region (Hard NAT)

DERP doesn't enter into STUN issues really at all.

@johnstcn
Copy link
Member Author

Notes for self: https://github.com/tailscale/tailscale/blob/main/ipn/localapi/debugderp.go has some stuff directly related to this

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 a pull request may close this issue.

2 participants