From: Jonathon Fernyhough <jonathon.fernyhough@york.ac.uk>
To: wireguard@lists.zx2c4.com
Subject: Re: Production usage of Wireguard
Date: Tue, 7 Nov 2017 09:34:04 +0000 [thread overview]
Message-ID: <698e22a4-a358-d3fa-16a3-c576fee8a253@york.ac.uk> (raw)
In-Reply-To: <CAC4KqtwH_XAXeXHSf9Kxs5t80Qag9GrMwp6SaPnO9bj=GVL-7w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 706 bytes --]
On 06/11/17 21:41, Ferris Ellis wrote:
> I know the project is still young but was
> wondering if anyone on the mailing list had started using WireGuard in
> production? And, if so, if they’d be willing to share some details about
> their use case and experience?
>
I use on on several high-traffic web servers to secure backend
communication to a separate Redis instance.
It's configured as a mesh to remove any reliance on a single WireGuard
"server" node (that is, each server knows the endpoint and single
allowed IP of each of the others).
It has worked without issue since deployment (March 2017). It's easily
one of the most satisfying layers I've added to any stack.
J
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-11-07 9:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 21:41 Ferris Ellis
2017-11-07 9:34 ` Jonathon Fernyhough [this message]
2017-11-07 9:38 ` Greg KH
2017-11-07 10:52 ` Outback Dingo
2017-11-07 12:05 ` Fredrik Strömberg
2017-11-07 12:57 ` William Öling
2017-11-07 13:27 ` Reuben Martin
2017-11-07 13:29 ` Ryan Whelan
2017-11-08 21:40 ` Ferris Ellis
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=698e22a4-a358-d3fa-16a3-c576fee8a253@york.ac.uk \
--to=jonathon.fernyhough@york.ac.uk \
--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).