From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: nicolas prochazka <prochazka.nicolas@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [wireguard-dev] Help about configuration
Date: Wed, 20 Sep 2017 23:17:30 +0200 [thread overview]
Message-ID: <CAHmME9oaM+n6DNN-pVfx+4D2_r=FEo=D9hEKyuLrO7rJu1tY9g@mail.gmail.com> (raw)
In-Reply-To: <CADdae-j5Xr0jqB+dHcX7aYat60tahMCBTKiWVnSm_A-cQuf=qA@mail.gmail.com>
Hi Nicolas,
Great that fixed it. Sometimes WireGuard can be a good diagnostic for
figuring out various network misconfigurations, because WireGuard's
allowed-ips binding is very strict and explicit.
By the way, you might want to change your private key to something
new, since your first email contained these in plaintext.
Jason
prev parent reply other threads:[~2017-09-20 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 15:11 nicolas prochazka
[not found] ` <CAHmME9qrtSm1Y-h9FfyXWVCmrvmtciFau0jG2144Yrwu=BRMig@mail.gmail.com>
[not found] ` <CAHmME9r0hXW8CT5wO10X-b-9HUBDzzvSAbnn69aFav+6ovxQGA@mail.gmail.com>
2017-09-20 15:21 ` Jason A. Donenfeld
2017-09-20 18:09 ` nicolas prochazka
2017-09-20 21:17 ` 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='CAHmME9oaM+n6DNN-pVfx+4D2_r=FEo=D9hEKyuLrO7rJu1tY9g@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=prochazka.nicolas@gmail.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).