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
_______________________________________________
WireGuard mailing list
[email protected]
https://lists.zx2c4.com/mailman/listinfo/wireguard
