From: Lev Stipakov <lstipakov@gmail.com>
To: openvpn-devel <openvpn-devel@lists.sourceforge.net>,
wireguard@lists.zx2c4.com
Subject: Re: [Openvpn-devel] Wintun performance results
Date: Fri, 14 Jun 2019 18:56:56 +0300 [thread overview]
Message-ID: <CAGyAFMWaHBAR1fPVx5PUERg=JU9hg+mQMhtQExqpE_tHvevSAw@mail.gmail.com> (raw)
In-Reply-To: <CAGyAFMUqqjF67DDdr+BQXvFU515_zK=fDehUJH1TF+zjyjuiAA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 996 bytes --]
Hi,
I got some new Wintun (I used version 0.2) performance stats I would like
to share. I have tested openvpn2 and openvpn3 (both with openssl) on the
client against openvpn2 and proprietary openvpn3 server (which is openvpn3
with kernel acceleration). Cipher AES-256-GCM.
Server - proprietary openvpn3
----------------------------------------------------
ovpn3 wintun 1.90 Gbit/s
ovpn3 tap6 890 Mbit/s
ovpn2 wintun 870 Mbit/s
ovpn2 tap6 440 Mbit/s
Server - open source openvpn2
----------------------------------------------------
ovpn3 wintun 670 Mbit/s
ovpn3 tap6 580 Mbit/s
ovpn2 wintun 610 Mbit/s
ovpn2 tap6 450 Mbit/s
As you see, in every case Wintun overperforms tap-windows6 and approaches
mind boggling 2 Gbit/s.
My openvpn2 wintun patch could be found here
https://github.com/lstipakov/openvpn/tree/feature/wintun, and openvpn3 -
https://github.com/lstipakov/openvpn3/tree/fix/wintun-fixes
Jason / Simon - great work on Wintun!
--
-Lev
[-- Attachment #1.2: Type: text/html, Size: 1530 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-06-18 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 13:48 Wintun performance results 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
2019-05-20 12:03 ` Lev Stipakov
2019-06-03 18:04 ` Lev Stipakov
2019-06-14 15:56 ` Lev Stipakov [this message]
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='CAGyAFMWaHBAR1fPVx5PUERg=JU9hg+mQMhtQExqpE_tHvevSAw@mail.gmail.com' \
--to=lstipakov@gmail.com \
--cc=openvpn-devel@lists.sourceforge.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).