From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Joshua Sjoding <joshua.sjoding@scjalliance.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Intermittent handshake failures in WireGuard for Windows
Date: Fri, 30 Apr 2021 15:49:18 +0200 [thread overview]
Message-ID: <CAHmME9omvixbuE0EgKAU-gD-UYwVsxj7keC5+toQRepdSmbXCA@mail.gmail.com> (raw)
In-Reply-To: <CALaUSuu24kKAXN18KoHz0Cby0Xn-RGEMjs7GuA97m7=JYRSrbA@mail.gmail.com>
Hi Joshua,
Is it possible that something nasty is happening with UDP
NAT/Conntracking tables on whatever intermediate device?
It might help to take some TCP dumps along the way and see where the
packets are going and whether they're lost past a certain hop.
Jason
prev parent reply other threads:[~2021-04-30 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 3:39 Joshua Sjoding
2021-04-30 13:49 ` Jason A. Donenfeld [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=CAHmME9omvixbuE0EgKAU-gD-UYwVsxj7keC5+toQRepdSmbXCA@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=joshua.sjoding@scjalliance.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).