Increase robustness of VPN connect.#208
Draft
Gerrit91 wants to merge 1 commit into
Draft
Conversation
Gerrit91
force-pushed
the
robustness-vpn-connect
branch
from
b5eef64 to
3433e1d
Compare
Contributor
|
Nice effort, the real solution should be to pass the connected ip from inspection of headscale on the metal-api back to the metalctl. In metal-apiserver this is already done and should also be carried over. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This was still in my local working copy... tried with @vknabel to make VPN connection establishment more reliable, but it not really improve the situation. Nevertheless, some ideas are quite alright I think, so maybe we would like to integrate some of them?
Used AI-Tools ✨