Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Lev Stipakov <lstipakov@gmail.com>
To: Jan Just Keijser <janjust@nikhef.nl>
Cc: "David Sommerseth" <openvpn@sf.lists.topphemmelig.net>,
	openvpn-devel <openvpn-devel@lists.sourceforge.net>,
	wireguard@lists.zx2c4.com, "Илья Шипицин" <chipitsine@gmail.com>
Subject: Re: [Openvpn-devel] Wintun performance results
Date: Thu, 16 May 2019 14:59:52 +0300	[thread overview]
Message-ID: <CAGyAFMW10tUVswPa8NfVieUJMm1oX1BFQaa9a0GP3NmgWpRshg@mail.gmail.com> (raw)
In-Reply-To: <bfead88f-3e91-6d49-ea70-e73f626468f1@nikhef.nl>


[-- Attachment #1.1: Type: text/plain, Size: 466 bytes --]

Hi,

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.


Correct.


> 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.
>

That's an open source openvpn3 test client, which is part of library
(openvpn/test/ovpncli/cli.cpp).

We'll incorporate required changes into master branch soon.

-- 
-Lev

[-- Attachment #1.2: Type: text/html, Size: 992 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

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

  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
2019-05-16 11:59       ` Lev Stipakov [this message]
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=CAGyAFMW10tUVswPa8NfVieUJMm1oX1BFQaa9a0GP3NmgWpRshg@mail.gmail.com \
    --to=lstipakov@gmail.com \
    --cc=chipitsine@gmail.com \
    --cc=janjust@nikhef.nl \
    --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).