From: "Aleksandr V. Piskunov" <aleksandr.v.piskunov@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: OpenWRT dynamic IP watchdog
Date: Sat, 16 Jun 2018 17:50:38 +0300 [thread overview]
Message-ID: <20180616144440.GA6799@d1781> (raw)
In-Reply-To: <CAHmME9ricuvsu=vpg4MQO0wBAXgoCdTSVMwP=BCd0Jt9Y3ZH+Q@mail.gmail.com>
Yes, I've tried 135 first, but during the real usage there were quite
a few false alarm situations with watchdog reconnecting at
136..~140 seconds. So.. changed it to 150 secs, which seems to work OK
for my conditions.
I can try to send a git patch to contrib/examples/reresolve-dns,
if rest is OK.
Regards,
Aleksandr
On Sat, Jun 16, 2018 at 03:00:45PM +0200, Jason A. Donenfeld wrote:
> Hi Aleksandr,
>
> Nice script. One question:
>
> > [ ${idle_seconds} -lt 150 ] && return 0;
>
> Is there a reason why you went with 150? My original reresolve-dns.sh
> went with 135 (REKEY_AFTER_TIME + KEEPALIVE_TIMEOUT + REKEY_TIMEOUT).
> Did you find 150 matched network conditions better?
>
> Regards,
> Jason
prev parent reply other threads:[~2018-06-16 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 9:27 Aleksandr V. Piskunov
2018-06-16 13:00 ` Jason A. Donenfeld
2018-06-16 14:50 ` Aleksandr V. Piskunov [this message]
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=20180616144440.GA6799@d1781 \
--to=aleksandr.v.piskunov@gmail.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).