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

Flag order affects VPN behavior #691

Closed
jdknives opened this issue Feb 23, 2021 · 1 comment
Closed

Flag order affects VPN behavior #691

jdknives opened this issue Feb 23, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@jdknives
Copy link
Member

Describe the bug
If the -killswitch flag is set first, before -srv or -passcode, the VPN-client does not work as the flags after the -killswitch are not read bz or not provided to the VPN-client.

Consequently this fails

[
					"-killswitch",
					"true",
					"-passcode",
					"",
					"-srv",
					"02e346d917500aadb71c8b0eafb4125c0e03723a0671dc7352cdd106ab215ef8e5"
				],

While this works:

[
					"-passcode",
					"",
					"-srv",
					"02e346d917500aadb71c8b0eafb4125c0e03723a0671dc7352cdd106ab215ef8e5",
					"-killswitch",
					"true"
				],
@jdknives jdknives added the bug Something isn't working label Feb 23, 2021
@jdknives
Copy link
Member Author

Just wrong flag usage apparently. Need to change the endpoint for setting the flag from the hypervisorUI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant