From: John <graysky@archlinux.us>
To: kolargol <kolargol@protonmail.com>
Cc: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: iOS WG Battery Life
Date: Sat, 2 Mar 2019 15:09:57 -0500 [thread overview]
Message-ID: <CAO_nJAZr1VcZ4vY+JKyQeEVsOdeDyLaJic4oRZVXZO9sEhZtwQ@mail.gmail.com> (raw)
In-Reply-To: <2iVkG0SJ64643A39NC7WLPcFxQc4oevInPxiNTvr0tixLQMLV3DyvvwNBLqj-tTk95sykibLeTPEPgDK1PvH4b-FS_YWR3kO9I3DLWuealE=@protonmail.com>
Does the iOS settings>battery show a consistent output for WG using
the CPU cycles?
On Sat, Mar 2, 2019 at 2:55 PM kolargol <kolargol@protonmail.com> wrote:
>
>
> > Possibly, is PersistentKeepalive defined at the "server" endpoint for your iOS peer ?
> >
> > I would expect a measurable additional battery usage if either peer endpoint had PersistentKeepalive defined (non-zero).
>
> Both server and peer have PersistentKeepalive disabled, there is no fancy apps runnign in backgroud - and i am using exac same WiFi and VPN endpoint (for OpenVPN and WG comparision).
> WiFI connection is stable and have strong signal, same with LTE.
> The battery grap shows sharp down in the night as something continuesly draing battery (here wg)
> How can i debug it ?
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-03-08 15:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 12:07 kolargol
2019-03-01 10:08 ` Kalin KOZHUHAROV
2019-03-02 0:30 ` Mark Finzel
2019-03-02 7:29 ` kolargol
[not found] ` <EA2CDA40-8988-4C4F-B848-B2F7C6D8716C@lonnie.abelbeck.com>
2019-03-02 19:54 ` kolargol
2019-03-02 20:09 ` John [this message]
2019-03-02 20:50 ` Mailing Lists
2019-03-03 15:30 ` kolargol
2019-03-02 21:22 ` Lonnie Abelbeck
2019-03-06 10:32 ` kolargol
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=CAO_nJAZr1VcZ4vY+JKyQeEVsOdeDyLaJic4oRZVXZO9sEhZtwQ@mail.gmail.com \
--to=graysky@archlinux.us \
--cc=kolargol@protonmail.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).