All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Whelan <rcwhelan@gmail.com>
To: Reuben Martin <reuben.m.work@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Production usage of Wireguard
Date: Tue, 7 Nov 2017 08:29:52 -0500	[thread overview]
Message-ID: <CAM3m09T26HgZfNihNO+-QR-5bsd=m+koY=gudThW6Kii9jETgQ@mail.gmail.com> (raw)
In-Reply-To: <CALJ2VGZzPmYvVDethJkeYzGq38g1Y4Nj6=QyscWcXVY+xnWXow@mail.gmail.com>

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

On Tue, Nov 7, 2017 at 8:27 AM, Reuben Martin <reuben.m.work@gmail.com>
wrote:

> On Nov 6, 2017 3:41 PM, "Ferris Ellis" <ferris@ferrisellis.com> 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
>> 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.
>>
>
> I've been using it for about 6 months to tie together remote video
> streaming servers in a star pattern with a vxlan overlay running on top of
> the wireguard connections. I mostly push low latency video over the
> connections.
>
> I've only had an issue once which was a bug resulting from some
> refactoring work, and Jason immediately pounced on it and had a fixed
> release out within a few hours. Honestly, a project with a maintainer that
> takes ownership of the code base like that imparts much more cred than any
> "stable" or "production ready" label does.
>
> -Reuben
>

I'll second that.  I've never seen a developer / maintainer thats as
engaged and responsive as Jason.

...And he sends out free stickers!

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

  reply	other threads:[~2017-11-07 13:26 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
2017-11-07 12:57 ` William Öling
2017-11-07 13:27 ` Reuben Martin
2017-11-07 13:29   ` Ryan Whelan [this message]
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='CAM3m09T26HgZfNihNO+-QR-5bsd=m+koY=gudThW6Kii9jETgQ@mail.gmail.com' \
    --to=rcwhelan@gmail.com \
    --cc=reuben.m.work@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 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.