From: Roman Mamedov <rm@romanrm.net>
To: Ole-Morten Duesund <olemd@glemt.net>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Wireguard behind NAT
Date: Mon, 3 Sep 2018 15:55:49 +0500 [thread overview]
Message-ID: <20180903155549.0677bf87@natsu> (raw)
In-Reply-To: <429987c9-26e4-edb7-4d31-c8e611615670@glemt.net>
On Mon, 3 Sep 2018 12:43:19 +0200
Ole-Morten Duesund <olemd@glemt.net> wrote:
> Adding a "PersistentKeepalive = 5" to your config on SIDE_A_SERVER
> should keep the connection up.
Do you encounter any difference between 5, 25 and 55, only 5 works for you? If
not, setting it to such a low interval seems wasteful, especially on
LTE/mobile with possibly metered bandwidth and battery concerns.
--
With respect,
Roman
next prev parent reply other threads:[~2018-09-03 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 10:28 Wireguard behind NAT Adrián Mihálko
2018-09-03 10:43 ` Ole-Morten Duesund
2018-09-03 10:55 ` Roman Mamedov [this message]
2018-09-03 10:59 ` Ole-Morten Duesund
-- strict thread matches above, loose matches on Subject: below --
2018-09-02 19:51 Adrián Mihálko
2018-09-07 3:39 ` Jason A. Donenfeld
2018-09-07 15:17 ` Steven Honson
2018-03-12 11:22 Adrián Mihálko
2018-04-14 2:06 ` 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=20180903155549.0677bf87@natsu \
--to=rm@romanrm.net \
--cc=olemd@glemt.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).