We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
$ sudo ./wag version remote Version: v4.1.1-1-gf055b4c Hash: 853da9fd51248b4cb68c9418b6e3fc871b7dad492521b5b7bb02689c14d04633
I just registered a new user, and it generated the config for me.
[Interface] PrivateKey = SuperSecretKey DNS = 10.10.6.254/32 Address = 192.168.254.27 [Peer] Endpoint = 82.123.123.123:51821 PresharedKey = SuperSecretKey PublicKey = SecretKey AllowedIPs = ... PersistentKeepAlive = 10
I wasn't paying attention, and then wondered why it never used resolvd and I could not do any DNS lookups.
It stuck a bogus /32 onto the DNS entry. Removed this and DNS now works.
/32
The text was updated successfully, but these errors were encountered:
Ah thanks for finding that. I don't use the dns directive myself.
I'll give that a fix today
Sorry, something went wrong.
a06307a
Done a little release enjoy :)
No branches or pull requests
I just registered a new user, and it generated the config for me.
I wasn't paying attention, and then wondered why it never used resolvd and I could not do any DNS lookups.
It stuck a bogus
/32
onto the DNS entry. Removed this and DNS now works.The text was updated successfully, but these errors were encountered: