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

Can't set DERP_STUN and DERP_VERIFY_CLIENTS to false #4

Closed
tzhao11 opened this issue Dec 24, 2021 · 4 comments
Closed

Can't set DERP_STUN and DERP_VERIFY_CLIENTS to false #4

tzhao11 opened this issue Dec 24, 2021 · 4 comments

Comments

@tzhao11
Copy link

tzhao11 commented Dec 24, 2021

derper seems to parse boolean argument solely based on whether the corresponding command line flag exists or not, regardless of its value, so passing in --stun false or --verify-clients false has no effect. We might need to stop passing these flags to derper when DERP_STUN and DERP_VERIFY_CLIENTS are not set to true.

I can't think of a clean way to do this without introducing an entrypoint script. Any ideas?

@fredliang44
Copy link
Owner

fredliang44 commented Dec 24, 2021

thanks for your report, let me take a look.

@fredliang44
Copy link
Owner

fredliang44 commented Dec 24, 2021

it seems derper using the "flag" package, switching to "=" seems to be working.

https://github.com/tailscale/tailscale/blob/bc537adb1a6a9794f7e74337880cc63c915d19f9/cmd/derper/derper.go#L123

image

@fredliang44
Copy link
Owner

@tzhao11 I updated the command in the main branch, could you help me double check whether it works as expected now?

@tzhao11
Copy link
Author

tzhao11 commented Dec 25, 2021

@fredliang44 working as expected now. Thanks for the fix!

@tzhao11 tzhao11 closed this as completed Dec 25, 2021
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

No branches or pull requests

2 participants