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: Mon, 20 May 2019 15:03:04 +0300	[thread overview]
Message-ID: <CAGyAFMWODccNnD+yby7HrOUfdDFaceC3AX70+jG9_hL9vF=q+A@mail.gmail.com> (raw)
In-Reply-To: <CAGyAFMW10tUVswPa8NfVieUJMm1oX1BFQaa9a0GP3NmgWpRshg@mail.gmail.com>


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

Hi,

While wintun support is not yet added to openvpn3 master, I think it would
be beneficial to share my own branch.

https://github.com/lstipakov/openvpn3/tree/feature/wintun-wip#building-the-openvpn-3-client-on-windows


See instructions in README on how to build openvpn3 library and test client
on Windows.

Note that only "topology subnet" is supported (see
https://community.openvpn.net/openvpn/wiki/Topology#Topologysubnet).

I have included test client and wintun driver binaries if someone would
like to try it out (Tested on Windows 10 and Windows Server 2016):

1. Since wintun driver is not signed, you need to enable loading of test
signed code. For that, run

> bcdedit /set testsigning

in admin command prompt and restart Windows.

2. Download and unzip wintun driver
https://github.com/lstipakov/openvpn3/blob/feature/wintun-wip/wintun.7z

3. Open Device Manager (Control Panel\System and Security\System\Device
Manager).
Right click on tree root, select "Add legacy hardware" -> "Next" -> "..
hardware that I manually select from a list" ->
"Next" -> "Show all devices" -> "Have Disk..." -> Locate wintun.inf
unpacked at step 2 -> select "Wintun Userspace Tunnel" ->
"Next" -> "Install this software anyway" (since driver is not signed).

4. Make sure you see "Wintun Userspace Tunnel" under Device Manager ->
Network adapters.

5. Download cli_wintun.exe from
https://github.com/lstipakov/openvpn3/blob/feature/wintun-wip/cli_wintun.exe

6. Open command prompt as an administrator and run:

> C:\Users\Administrator\Downloads>cli_wintun.exe <your_vpn_profile.ovpn>

7. Enjoy!

-- 
-Lev

[-- Attachment #1.2: Type: text/html, Size: 2757 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-06-06  9:36 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
2019-05-20 12:03         ` Lev Stipakov [this message]
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='CAGyAFMWODccNnD+yby7HrOUfdDFaceC3AX70+jG9_hL9vF=q+A@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).