Wireguard roadwarrior : Add tip to use peer generator and clarify DNS when using Unbound #650
Conversation
This file contains 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
AdSchellevis
reviewed
Jan 3, 2025
Co-authored-by: Ad Schellevis <AdSchellevis@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Wireguard roadwarrior : Add tip to use peer generator and clarify DNS when using Unbound. The current tuto doesn't mention the peer generator feature. I think the right way would be to rewrite section 2 entirely to leverage the peer generator feature and explain to use the QR code before saving it, but at least with the tip people will know they can use it (and configuration is pretty much the same).
Also, client config needs the DNS to be the tunnel address for it to work.
=====
For context, I've been trying to setup VPN for the past few days. I gave up on IPSec and tried Wireguard next. Followed the how-to step by step a few times and never could get it to work, until I found that I simply needed to configure the DNS on the client side to be the address of the tunnel (10.10.10.1 in the tuto example).