All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fredrik Strömberg" <stromberg@mullvad.net>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: Production usage of Wireguard
Date: Tue, 7 Nov 2017 13:05:26 +0100	[thread overview]
Message-ID: <CANTUoec-8PeEJLLMASkjG8+bR9XjdXpmaEOeg2MdqZriEkYjPw@mail.gmail.com> (raw)
In-Reply-To: <20171107093832.GB7891@kroah.com>

On Tue, Nov 7, 2017 at 10:38 AM, Greg KH <gregkh@linuxfoundation.org> wrote=
:
> On Mon, Nov 06, 2017 at 09:41:18PM +0000, Ferris Ellis wrote:
>> 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 review=
s
>> are useful, they don=E2=80=99t uncover many of the issues that can poten=
tially wake
>> one up at 3am. I=E2=80=99d hunted around on the web for a while but wasn=
=E2=80=99t able to
>> find any articles on running WireGuard in a production environment. I kn=
ow
>> the project is still young but was wondering if anyone on the mailing li=
st
>> had started using WireGuard in production? And, if so, if they=E2=80=99d=
 be willing
>> to share some details about their use case and experience?
>
> There are at least two companies offering Wireguard as a VPN service
> "commercially" right now, so it is being used in that manner already.
>

Hi everyone,

We (Mullvad) use it in production on a bunch of our servers. Here's a
blog post I wrote about it that might be of interest to you Ferris:
https://mullvad.net/blog/2017/9/27/wireguard-future/

> But as "production environment" always means different things for
> different people, perhaps only you can answer this question?  What would
> it take for _you_ to be comfortable with it in your network environment?

I second Greg's question. What are your criteria?

Cheers,
Fredrik Str=C3=B6mberg

  parent reply	other threads:[~2017-11-07 12:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06 21:41 Production usage of Wireguard 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 [this message]
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=CANTUoec-8PeEJLLMASkjG8+bR9XjdXpmaEOeg2MdqZriEkYjPw@mail.gmail.com \
    --to=stromberg@mullvad.net \
    --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.