-
Notifications
You must be signed in to change notification settings - Fork 627
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
PersistentKeepalive Client #990
Comments
What would be the benefit? |
No comments in a while, closing... |
Add PersistentKeepalive parameter to client config, closes pivpn#990
Would suggest to reopen this: I have the same issue. As to your question: adding this keeps the connection alive through most NAT setups. WG will only use the tunnel when a packet needs to be sent. Most (all) NAT gateways / firewalls / routers, will see that no traffic happens for a while, and will wipe the NAT entry. If the client (behind NAT) needs to connect to the server, that's fine: the client initiates a new connection, this is picked up by the NAT gw, etc. But if the connection has expired and the server needs to connect to the client, it can't. Adding "PersistentKeepalive = 25" will send a keep-alive packet from the client to the server every 25 seconds, thus forcing the NAT gateway to keep everything in place, allowing the server to connect to the client if needed. More info: https://www.wireguard.com/quickstart/#nat-and-firewall-traversal-persistence Patch: #1174 |
FYI: Added to wireguard profiles |
Is your feature request related to a problem? Please describe.
A PersistentKeepalive should be added automatically when creating a client, I use PersistentKeepalive 1
Describe the solution you'd like
Add PersistentKeepalive to the script
The text was updated successfully, but these errors were encountered: