From: Laszlo KERTESZ <laszlo.kertesz@gmail.com>
To: "Ivan Labáth" <labawi-wg@matrix-dream.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Keep-alive does not keep the connection alive
Date: Wed, 28 Aug 2019 10:43:32 +0300 [thread overview]
Message-ID: <CANcuY=qhYgh5AFmu-opyf95cuTqGuUgPN0te7dCR563ZGwkpTQ@mail.gmail.com> (raw)
In-Reply-To: <20190828065411.GA6914@matrix-dream.net>
[-- Attachment #1.1: Type: text/plain, Size: 564 bytes --]
> As a workaround you could
> - unconditionally periodically update the endpoint
> - monitor last handshake time, when large update endpoint or restart
> tunnel
> - add keepalive to server - it might reduce your downtime
>
Keepalive does not seem to work in my experience.
On Linux i set up a recurrent script that tests connection to the wg tunnel
gateway and restarts the connection if the connection test fails.
But on Android this is not possible without additional tools running in
background that will use battery and negate wireguard's benefits.
[-- Attachment #1.2: Type: text/html, Size: 895 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-08-28 7:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 19:13 Keep-alive does not keep the connection alive Hendrik Friedel
[not found] ` <CANH_QeYQ7hyBG1qK9PJB9E77gggW0NYe70vv8m6Dn=fU5zHQbg@mail.gmail.com>
2019-08-25 18:44 ` Re[2]: " Hendrik Friedel
2019-08-26 18:02 ` Ivan Labáth
2019-08-28 6:06 ` Re[2]: " Hendrik Friedel
2019-08-28 6:17 ` Laszlo KERTESZ
2019-08-28 6:25 ` Re[2]: " Hendrik Friedel
2019-08-28 6:37 ` Laszlo KERTESZ
2019-08-28 6:54 ` Ivan Labáth
2019-08-28 7:43 ` Laszlo KERTESZ [this message]
2019-09-07 10:04 ` Re[2]: " Hendrik Friedel
2019-09-10 9:19 ` Ivan Labáth
2019-09-11 13:28 ` Vincent Wiemann
2019-10-17 19:03 ` Re[2]: " Hendrik Friedel
2019-10-20 20:25 ` Ivan Labáth
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='CANcuY=qhYgh5AFmu-opyf95cuTqGuUgPN0te7dCR563ZGwkpTQ@mail.gmail.com' \
--to=laszlo.kertesz@gmail.com \
--cc=labawi-wg@matrix-dream.net \
--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).