Actions
Bug #15447
closedWireguard not sending keep-alives according to configuration
Status:
Closed
Priority:
Low
Assignee:
-
Category:
WireGuard
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
24.03
Affected Architecture:
Description
I have configured my wireguard peers with a 30s keep-alive interval. As I was viewing a packet capture in Wireshark I noticed that only one Keepalive is ever sent, immediately after every Handshake Response, there are no repeated Keepalives every 30s as I expected to find with the two minute handshake period.
This is no a biggie as I doubt it has any real-world implications, but I thought I'd report it.
Updated by Patrik Stahlman 12 months ago
Sorry, having though about this a bit longer I realise the Keepalive is only sent when there's no Transport data sent. Turning off dpinger shows wireguard sending Keepalives correctly. The redmine can be closed.
Updated by Kris Phillips 12 months ago
- Status changed from New to Closed
Closing this redmine, per request.
Actions