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: Re: Troubleshooting WireGuard connections
Date: Fri, 13 Apr 2018 23:54:25 +0200	[thread overview]
Message-ID: <CAHmME9rFZMXcjZgFQBrZHDCbqmYT+MdBEJmS6f6=5=F-7nrJBA@mail.gmail.com> (raw)
In-Reply-To: <628776a245ad4895630fd727c80e8bf1@rcrdbrt.com>

When you type "wg", does it show you a "latest handshake"? If not,
perhaps they're not even communicating at all. For this, you could
look for udp packets on port 21 and see what's up.

Also, you might simplify things a bit by:
- Removing all mentions of Endpoint on the server, since the server
will learn these from roaming
- Removing all mentions of Port on the clients, since these can be
randomly selected

  reply	other threads:[~2018-04-13 21:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13  9:23 Riccardo Berto
2018-04-13 21:54 ` Jason A. Donenfeld [this message]
     [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
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

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='CAHmME9rFZMXcjZgFQBrZHDCbqmYT+MdBEJmS6f6=5=F-7nrJBA@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).