Skip to content
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

Private / Nat peers with persistence but no endpoint #215

Open
defect-track opened this issue Dec 20, 2024 · 0 comments
Open

Private / Nat peers with persistence but no endpoint #215

defect-track opened this issue Dec 20, 2024 · 0 comments

Comments

@defect-track
Copy link

Hello,

have the use case where some of my peers are behind a Firewall where it isn't possible to get an inbound port opened for security reasons. However, if you just configure the persistence for these clients like described in https://www.wireguard.com/quickstart/#nat-and-firewall-traversal-persistence they can be still part of your VPN.
Reading through the code you can set the persistence but only if an endpoint is defined which will of course fail in this scenario. Believe that this is quite a common use case?

My suggestion would be to introduce a new variable like "wireguard_private_peers" where you can define a list of peers located behind a firewall which will trigger to not populate the "Endpoint".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant