-
Notifications
You must be signed in to change notification settings - Fork 171
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
ability to restrict exported peers #195
Comments
gregorydlogan
added a commit
to gregorydlogan/ansible-role-wireguard
that referenced
this issue
Mar 5, 2024
…master Pull request githubixx#196 Fixes githubixx#195 Add support for wireguard_include_peers variable
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(this is related to #101, but not exactly the same)
I have a complex wireguard setup where not all nodes can directly talk to each. This works fine at the moment (prior to migration no ansible-wireguard) because there is one central node that all peers can reach (and which has an allowed_ips configured that is wide enough to cover all nodes). I only configure peers that are actually reachable.
It would be great if there was a way of explicitly specifying the peers that should be exported for a particular node, and otherwise exporting all available peers.
The text was updated successfully, but these errors were encountered: