Since distributing own wintun binaries goes against recommended way (which
is MSM modules), here are steps to try out openvpn with wintun (which is
even simpler than previous way):
- Install wireguard windows client from https://www.wireguard.com/install/
- Download patched openvpn binaries
Double checked that it was in my original email :)
> * if you have OpenVPN GUI client installed, run under administrative
command prompt:
> c:\Program Files\TAP-Windows\bin>tapinstall.exe install
c:\Temp\wintun\wintun.inf wintun
> * alternatively you can install driver via windows device
Hi,
On Fri, Sep 20, 2019 at 1:55 PM Lev Stipakov wrote:
>
> Hi Steffan,
>
>> Out of curiosity: does the (signed) driver from wintun.net not work? Of so,
>> why?
>
>
> It does. It is just not usable for openvpn yet because:
>
> 1) Wintun is distributed as msm module, which is supposed to be
Hi Steffan,
Out of curiosity: does the (signed) driver from wintun.net not work? Of so,
> why?
>
It does. It is just not usable for openvpn yet because:
1) Wintun is distributed as msm module, which is supposed to be integrated
into MSI installer.
Our MSI installer doesn't support wintun yet.
Hi,
On Fri, Sep 20, 2019, 15:47 Lev Stipakov wrote:
> Wintun driver is now signed for Windows 10,
>
> https://staging.openvpn.net/openvpn2/wintun-0.6-signed.zip
>
> So if you want to try out super fast openvpn2, no need to meddle anymore
> with test mode / disabling signature checks.
>
Out of
Hello,
Wintun driver is now signed for Windows 10,
https://staging.openvpn.net/openvpn2/wintun-0.6-signed.zip
So if you want to try out super fast openvpn2, no need to meddle anymore
with test mode / disabling signature checks.
ti 17. syysk. 2019 klo 15.45 Lev Stipakov (lstipa...@gmail.com)
Hello,
> Does the VS build target a more
> recent Windows runtime than the legacy one (msvcrt.dll) that mingw
> would link against?
Yes, VS build targets Universal CRT, while mingw targets "classis",
pre-Visual Studio 2015 CRT.
Answering to Gert's question in IRC - CPU load was 25% on 4-core
Hi,
Turns out that our build script for windows-nsis/generic doesn't specify
any optimization flags.
I added -O2 and got 400Mbit/s with mingw, which is better than 340 but
worse than VS's 425.
Haven't yet checked which flags are used for openssl build.
Also adding "-O2" to CFLAGS breaks rc
From: Lev Stipakov
This set of patches adds support of wintun kernel driver
(https://www.wintun.net) to OpenVPN.
While wintun is in beta, it performs significantly faster comparison to
tap-windows6.
Here are some performance numbers (download bandwidth):
Server - community openvpn2
mingw,
