Ability to use an existing private key#385
Merged
ViRb3 merged 2 commits intoViRb3:masterfrom Mar 9, 2024
Merged
Conversation
In my case, it was necessary to use an existing WireGuard private key. I added the ability to specify an existing private key when registering with CloudFlare through the "-k" argument.
ViRb3
requested changes
Mar 7, 2024
Owner
|
Apologies, I thought I submitted the review comment but it was stuck in Pending. I submitted it now, pls make the change and I am happy to merge. |
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.
Hi!
First of all, I want to thank you for this amazing tool. It has saved me a ton of time during the integration of CloudFlare WARP into our infrastructure. This tool allowed us to utilize existing complex routing and firewall settings on the server without having to rely on the cumbersome utility provided by CloudFlare itself.
My case involved a pre-configured and operational WireGuard server, to which clients connect. I needed to reroute all server traffic through CloudFlare WARP. However, in its standard setup, the tool generates and registers a new private key. This would have required me to reconfigure numerous active clients to enable traffic redirection to CloudFlare WARP servers. Attempting to establish two wg interfaces was unsuccessful, although it seemed like a potential solution.
To address this issue, I added the capability to use an existing private key by using the
-k(--key) argument in theregistercommand. If a key is provided, that key is used. Otherwise, a new one is generated.I hope this helps someone else, besides just me.