From: Steve Brown <sbrown@ewol.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Keep alive being sent when PersistentKeepalive = 0
Date: Thu, 15 Apr 2021 10:02:14 -0400 [thread overview]
Message-ID: <7a8e0f8f25c43effb17b01e6344678ba9c6462a6.camel@ewol.com> (raw)
I have no PersistentKeepalive set, but the peer gets sent a keep alive
every 60 seconds anyway.
This is verified by the both the wireguard log on the sending side and
firewall log on the receiving side. The peer is nat'd and sends its own
keep alive every 15 seconds.
wg showconf <intf> doesn't show a keep alive value for the peer.
This isn't a problem other than a little noise in the log. The packet
gets dumped by the peer's firewall.
I'm running openwrt with kernel 5.10.23.
Steve
next reply other threads:[~2021-04-15 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 14:02 Steve Brown [this message]
2021-04-15 17:11 ` Jason A. Donenfeld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7a8e0f8f25c43effb17b01e6344678ba9c6462a6.camel@ewol.com \
--to=sbrown@ewol.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).