Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Eicke Herbertz <wolletd@posteo.de>
To: jason@zx2c4.com
Cc: wireguard@lists.zx2c4.com, wolletd@posteo.de
Subject: Re: Invalid handshake initiation after peer reboot: bug?
Date: Mon, 24 Aug 2020 20:19:37 +0200	[thread overview]
Message-ID: <7aa9fe5e-2ae2-cf8b-ae6d-d98de2031b44@posteo.de> (raw)
In-Reply-To: <CAHmME9pC+M1Wh-NCa5XAUAVFhT5hnJA2Rdnfj+DWdmxk5S5rLA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 742 bytes --]

Hi Jason,

thanks for your help, you were correct!
It dawned on me the moment I read "real time clock": While OpenWRT
enables network time synchronization by default, our customer blocks all
internet access other than to our VPN server for the devices. That's why
it wasn't reproducible in the office.
After pointing NTP to our server as well, WireGuard is back to it's
instantaneous beauty.

Would it be feasible to distinguish some cases of "Invalid handshake" in
the debug log? Simply reading "replay" somewhere would've helped
probably. I'm using WireGuard for about two years now and this was the
first time I actually had to enable debug logging to understand my
issue, but the debug logging didn't help much.

Eicke


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2020-08-24 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21 20:42 Eicke Herbertz
2020-08-22 19:11 ` Jason A. Donenfeld
2020-08-24 18:19   ` Eicke Herbertz [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=7aa9fe5e-2ae2-cf8b-ae6d-d98de2031b44@posteo.de \
    --to=wolletd@posteo.de \
    --cc=jason@zx2c4.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).