Development discussion of WireGuard
 help / color / mirror / Atom feed
From: <scorba69@seznam.cz>
To: <wireguard@lists.zx2c4.com>
Subject: Wireguard sending keepalives even if keepalives disabled
Date: Tue, 04 Aug 2020 15:28:20 +0200 (CEST)	[thread overview]
Message-ID: <7iV.N1fS.68VV8Wp67zX.1VAM9p@seznam.cz> (raw)

Hello,

sorry if this is not a bug and also sorry if I am not using mailing lists in the right way (I was not sure where to ask)...

I have a little problem with wireguard. I have 2 devices:
1) Debian Linux server with Wireguard service
2) Android phone with Wireguard app
They are both on the same local network (no subnets, no NAT etc.)

Everything works fine, but I have noticed that keepalive packets are being sent between the two devices on regular basis, even if PersistentKeepalive is not set.
They are sent like every few minutes, sometimes twice in a row. The behavior does not change even if I set PersistentKeepalive on both devices to e.g. 3600 seconds (1 hour).
It seems, that the communication is little bit chatty. I have also noticed that every few minutes a handshake also happens.

The reason I am talking about this is that this is causing unnecessary traffic and therefore increased battery consumption of the Android phone.
For example on my phone, battery usually drops by 3% over night, but with wireguard turned on it drops by 10%.

I know that wireguard is still in development, I would just like to see some information regarding this topic.

More information (including log from android app) can be found on reddit: https://www.reddit.com/r/WireGuard/comments/hm4h88/wireguard_battery_drain_on_android_phone/

Thanks a lot for any reply
Tom

                 reply	other threads:[~2020-08-06 14:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7iV.N1fS.68VV8Wp67zX.1VAM9p@seznam.cz \
    --to=scorba69@seznam.cz \
    --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).