All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferris Ellis <ferris@ferrisellis.com>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Production usage of Wireguard
Date: Mon, 06 Nov 2017 21:41:18 +0000	[thread overview]
Message-ID: <CAC4KqtwH_XAXeXHSf9Kxs5t80Qag9GrMwp6SaPnO9bj=GVL-7w@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 675 bytes --]

Hello Wireguard mailing list!

I have been very interested in the WireGuard project for a little while now
and am in the process of evaluating it. While benchmarks and code reviews
are useful, they don’t uncover many of the issues that can potentially wake
one up at 3am. I’d hunted around on the web for a while but wasn’t able to
find any articles on running WireGuard in a production environment. 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?

Cheers,
Ferris

-- 
Ferris Ellis

[-- Attachment #2: Type: text/html, Size: 932 bytes --]

             reply	other threads:[~2017-11-06 21:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06 21:41 Ferris Ellis [this message]
2017-11-07  9:34 ` Production usage of Wireguard Jonathon Fernyhough
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='CAC4KqtwH_XAXeXHSf9Kxs5t80Qag9GrMwp6SaPnO9bj=GVL-7w@mail.gmail.com' \
    --to=ferris@ferrisellis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.