Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Riccardo Berto <riccardo@rcrdbrt.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Troubleshooting WireGuard connections
Date: Sun, 15 Apr 2018 01:19:38 +0200	[thread overview]
Message-ID: <CAHmME9rUuheX=nHWfiNHj+gnZ2bJhu9up-TOR6TPKJk2n0fCmw@mail.gmail.com> (raw)
In-Reply-To: <9896807f0c6cbee1c7c99647a3c289cc@rcrdbrt.com>

Hi Riccardo,

That's a confusing result. The tcpdump also shows two sequences of
completed handshakes happening, about 7 seconds apart. It might be
best in the end to hop onto IRC next week, and we can debug this in
real time. But based on the erratic behavior, my only guess remaining
is that you've mixed up the public and private keys -- perhaps sharing
a private key amongst hosts -- and so one session is interrupting the
handshake of another? Hmm...

Jason

  reply	other threads:[~2018-04-14 23:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13  9:23 Riccardo Berto
2018-04-13 21:54 ` Jason A. Donenfeld
     [not found]   ` <33d0fd1f4c60919b98b50e2b9d04fe78@rcrdbrt.com>
2018-04-13 22:36     ` Riccardo Berto
2018-04-14  1:26       ` Jason A. Donenfeld
2018-04-14  7:56         ` Riccardo Berto
2018-04-14 23:19           ` Jason A. Donenfeld [this message]
2018-04-20 13:57           ` Riccardo Berto
2018-04-20 19:37             ` Jason A. Donenfeld
2018-04-20 19:39               ` Jason A. Donenfeld
2018-04-20 19:51                 ` Jason A. Donenfeld
2018-04-20 20:31                   ` Riccardo Berto
2018-04-25 11:46                     ` Riccardo Berto
2018-04-25 11:51                       ` Jason A. Donenfeld
2018-04-25 12:40                         ` logcabin
2018-04-25 22:56                         ` Riccardo Berto
2018-04-26  9:52                         ` Riccardo Berto
  -- strict thread matches above, loose matches on Subject: below --
2018-04-12  9:09 Riccardo Berto
2018-04-12 20:57 ` Eric Light

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='CAHmME9rUuheX=nHWfiNHj+gnZ2bJhu9up-TOR6TPKJk2n0fCmw@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=riccardo@rcrdbrt.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).