From: Alex Davies <alex@davz.net>
To: Varun Priolkar <me@varunpriolkar.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [ANNOUNCE] OPNsense 19.7 supports WireGuard
Date: Wed, 28 Aug 2019 20:08:13 +0100 [thread overview]
Message-ID: <CAHwDNp2pLJBV8M0sPa+XA4MDMVqJOp2=PQ1B=_W++k7V=wYfGA@mail.gmail.com> (raw)
In-Reply-To: <CALwBDFtP-QkGVZ6EncjtQxZ1--sGWKwzXwpNPaiLYymR5=+G6Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1744 bytes --]
This is great news. We have been using wireguard on OPNSense (mostly as
servers, but also as a client in a few places) in production for some time
now, without drama (we found one bug with a trivial workaround, see email
chain "Table=off behavior (not adding any route *at all*)" to this list).
We can now upgrade to something formally "supported" ;-)
If anybody else tries to use the hardware appliances provided by the
founders of OPNSense (Deciso[1]) as a wireguard server or client, we found
the performance on the non-x86 CPUs (A10, etc.) was not great (they have
all sorts of ipsec type offloads, but not for WG). IIRC we struggled to get
more than a few gigabits per second in aggregate. The Intel E3 models are
able to run as close to line rate on 10G as makes no odds for us.
[1]
https://www.deciso.com/wp-content/uploads/2015/11/Brochure-OPNsense-appliances_ordered-rev201603.pdf
On Mon, Aug 26, 2019 at 1:32 PM Varun Priolkar <me@varunpriolkar.com> wrote:
> Congratulations! :) I did test it out when it wasn’t stable and well
> things weren’t stable(as expected). Hope to have an another crack at it.
>
> On Sun, 25 Aug 2019 at 21:32, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
>> Congratulations on the release. That's great news.
>>
>> Would you like me to add some blurb to https://www.wireguard.com/install/
>> on it?
>> _______________________________________________
>> WireGuard mailing list
>> WireGuard@lists.zx2c4.com
>> https://lists.zx2c4.com/mailman/listinfo/wireguard
>>
> --
> Regards,
>
> Varun Priolkar
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
[-- Attachment #1.2: Type: text/html, Size: 3089 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-08-28 19:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 12:05 [ANNOUNCE] OPNsense 19.7 supports WireGuard Muenz, Michael
2019-08-25 15:45 ` Jason A. Donenfeld
2019-08-26 8:09 ` Varun Priolkar
2019-08-28 19:08 ` Alex Davies [this message]
2019-08-29 4:47 ` Muenz, Michael
2019-08-26 9:37 ` Muenz, Michael
[not found] <mailman.1.1566813601.6235.wireguard@lists.zx2c4.com>
2019-08-26 11:44 ` Vincent
2019-08-26 12:50 ` Chriztoffer Hansen
2019-08-26 14:25 ` Muenz, Michael
2019-08-27 4:28 Vincent
2019-08-27 5:15 ` Muenz, Michael
2019-08-27 7:35 ` Vincent
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='CAHwDNp2pLJBV8M0sPa+XA4MDMVqJOp2=PQ1B=_W++k7V=wYfGA@mail.gmail.com' \
--to=alex@davz.net \
--cc=me@varunpriolkar.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).