fix: don't send keep-alives as responder without session #16
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.
In WireGuard, sessions expire after 180s. In case data has been sent through the tunnel already, WireGuard will initiate a re-key after 120s. Otherwise, the tunnel will expire. Here is the catch: If both sides have a persistent keep-alive configured, attempting to send the next keep-alive with an expired tunnel will initiate a new handshake. This results in both parties sending handshake initiations to each other, effectively fighting over being the initiator of the new handshake. Here are some logs from a test run that demonstrates this:
We can mitigate this by adding an additional condition to the
keepalive_required
condition: