Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "William Öling" <william@azirevpn.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Production usage of Wireguard
Date: Tue, 7 Nov 2017 13:57:03 +0100 (CET)	[thread overview]
Message-ID: <993737547.71422.1510059423267.JavaMail.zimbra@azirevpn.com> (raw)
In-Reply-To: <CAC4KqtwH_XAXeXHSf9Kxs5t80Qag9GrMwp6SaPnO9bj=GVL-7w@mail.gmail.com>

Hello,

We run WireGuard in production for a sizable user base. We've had no proble=
ms with it at all so far. However, we'd like to create problems as a means =
of finding any latent bugs, so yesterday we opened up our service for free,=
 so we can get more people toasting our servers.

Check out https://www.azirevpn.com/wireguard if anybody wants to put some b=
andwidth through our pipes.

Br,
William, AzireVPN

----- Original Message -----
From: "Ferris Ellis" <ferris@ferrisellis.com>
To: wireguard@lists.zx2c4.com
Sent: Monday, November 6, 2017 10:41:18 PM
Subject: Production usage of Wireguard

Hello Wireguard mailing list!=20

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=E2=80=99t uncover many of the issues that can potentia=
lly wake one up at 3am. I=E2=80=99d hunted around on the web for a while bu=
t wasn=E2=80=99t able to find any articles on running WireGuard in a produc=
tion environment. I know the project is still young but was wondering if an=
yone on the mailing list had started using WireGuard in production? And, if=
 so, if they=E2=80=99d be willing to share some details about their use cas=
e and experience?=20

Cheers,=20
Ferris=20

--=20
Ferris Ellis=20

_______________________________________________=20
WireGuard mailing list=20
WireGuard@lists.zx2c4.com=20
https://lists.zx2c4.com/mailman/listinfo/wireguard=20

  parent reply	other threads:[~2017-11-07 12:53 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
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 [this message]
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=993737547.71422.1510059423267.JavaMail.zimbra@azirevpn.com \
    --to=william@azirevpn.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).