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
Wireguard - not able to create an Instance without Public Key like in official Doc #7229
Closed
2 tasks done
Comments
I think I have been a bit to enthusiastic in #7110, if there should be a constraint on the instance, it should be on private key not public... but dropping it doesn't hurt either. I'll drop the instance constraint and we'll wait if anything else is needed. The original ticket was about duplicate peers... |
AdSchellevis
added a commit
that referenced
this issue
Feb 21, 2024
…in model and remove required tag also validate on base64. #7229
fichtner
pushed a commit
that referenced
this issue
Mar 12, 2024
…ld only apply on peers (not instances). closes #7229
fichtner
pushed a commit
that referenced
this issue
Mar 12, 2024
…in model and remove required tag also validate on base64. #7229
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
The WireGuard new Instance interface requires that the public key be unique and is filled. This check was probably implemented with #7110. This behavior makes sense to prevent duplicate public keys on the same WireGuard instance, but breaks(?) functionality when using some privacy VPN endpoints where none public keys is needed.
The instance - for dialing in - only have a PrivateKey. In the official Documentation its written for AZIRE VPN correct:
https://docs.opnsense.org/manual/how-tos/wireguard-client-azire.html#step-2-setup-wireguard-instance
--> "In the field Private Key insert the value from your text file and leave Public Key empty."
To Reproduce
Steps to reproduce the behavior:
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 24.1.1 (amd64).
The text was updated successfully, but these errors were encountered: