feature/wgcf/optional-keepalive-generation - #620
Merged
ViRb3 merged 6 commits intoSep 18, 2026
Merged
Conversation
ViRb3
force-pushed
the
feature/wgcf/optional-keepalive-generation
branch
from
September 18, 2026 17:36
498c2b1 to
0cce359
Compare
Owner
|
Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Clients behind NAT may lose their port mapping after a period of inactivity. When that happens, the wg peer can no longer receive traffic until it sends a new packet itself.
This adds an optional
--keepaliveflag to generated profiles so users behind NAT can enable wireguard'sPersistentKeepalivesetting when needed, while preserving the existing output by default.Description
Adds optional persistent keepalive support when generating WireGuard profiles.
Usage:
PersistentKeepalive is omitted when the flag is not used.
Tests added for the flag parsing and generated profile output.
Side note
To be clear don't know what style and other things should be used in a PRs and code, did not find it in a readme. Tried to follow your commit naming convention and code habits.
@ViRb3