From: Jan Just Keijser <janjust@nikhef.nl>
To: "David Sommerseth" <openvpn@sf.lists.topphemmelig.net>,
"Илья Шипицин" <chipitsine@gmail.com>,
"Lev Stipakov" <lstipakov@gmail.com>
Cc: openvpn-devel <openvpn-devel@lists.sourceforge.net>,
wireguard@lists.zx2c4.com
Subject: Re: [Openvpn-devel] Wintun performance results
Date: Thu, 16 May 2019 12:14:10 +0200 [thread overview]
Message-ID: <bfead88f-3e91-6d49-ea70-e73f626468f1@nikhef.nl> (raw)
In-Reply-To: <7bdf712d-4e0c-0667-c9eb-1bdd862b1e40@sf.lists.topphemmelig.net>
Hi David, *
On 15/05/19 19:32, David Sommerseth wrote:
> On 15/05/2019 16:49, Илья Шипицин wrote:
>> it will most probably get lost in mailing list.
>> can we add it to https://openvpn.net website ? something like "performance
>> testing" with full configs provided ?
> Good idea, but maybe not the official corp web pages just yet. But we should
> definitely have some wiki pages under https://community.openvpn.net/ related
> to how to prepare a good setup for performance testing.
>
>
a community wiki page on how to prepar a good setup for performance
testing sounds like a good plan.
However, if I am not mistaken the version of OpenVPN used in the test
was a *Windows* build of OpenVPN3 with a wintun patch included. That is
not open source, is it? I'd *not* be in favour of writing community
wiki pages on the non-open source version of OpenVPN.
JM2CW,
JJK
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-05-18 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 13:48 Lev Stipakov
2019-05-15 14:49 ` [Openvpn-devel] " Илья Шипицин
2019-05-15 15:31 ` Lev Stipakov
2019-05-15 17:32 ` David Sommerseth
2019-05-16 10:14 ` Jan Just Keijser [this message]
2019-05-16 11:59 ` Lev Stipakov
2019-05-20 12:03 ` Lev Stipakov
2019-06-03 18:04 ` Lev Stipakov
2019-06-14 15:56 ` Lev Stipakov
2019-05-16 11:44 ` Jason A. Donenfeld
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=bfead88f-3e91-6d49-ea70-e73f626468f1@nikhef.nl \
--to=janjust@nikhef.nl \
--cc=chipitsine@gmail.com \
--cc=lstipakov@gmail.com \
--cc=openvpn-devel@lists.sourceforge.net \
--cc=openvpn@sf.lists.topphemmelig.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 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).