[Solved] Testing WinTUN: Failure

Weekly dev snapshots are available for testing.
We talk about them here. Testing features in the dev snapshot helps the features make it to stable.
Forum rules
Please report your experience with testing branch. Include what you were using and how
If there is a problem, the more info the better!
Post Reply
roswitina
OpenVpn Newbie
Posts: 7
Joined: Sat Sep 08, 2012 9:58 am

[Solved] Testing WinTUN: Failure

Post by roswitina » Tue Aug 18, 2020 1:25 pm

Today I have installed version "OpenVPN-2.5-beta1-amd64.msi". While testing the WinTUN - driver I got the following error in the LOG.

Code: Select all

.........
2020-08-18 15:09:02 open_tun
2020-08-18 15:09:02 MANAGEMENT: Client disconnected
2020-08-18 15:09:02 ERROR:  Wintun requires SYSTEM privileges and therefore should be used with interactive service. If you want to use openvpn from command line, you need to do SYSTEM elevation yourself (for example with psexec).
2020-08-18 15:09:02 Exiting due to fatal error
My configuration file has the following content:

Code: Select all

#OpenVPN Client conf
dev tun
windows-driver wintun
tls-client
client
nobind
proto udp
tun-mtu 1500
remote 1.2.3.4 12345
remote 1.2.3.5 12345
resolv-retry infinite
pkcs12 file.p12
cipher AES-256-CBC
auth SHA1
...........
It is interesting that I had already installed the version "openvpn-install-2.5_git_wintun-I607-Win10.exe", and with this version the WinTUN - driver worked with the same configuration file.

Rosi

Ps.:
I have just reinstalled "openvpn-install-2.5_git_wintun-I607-Win10.exe" and the WinTUN - driver works with the connection....

I will stay with it for the first time, but I will test it in case of tips and report the result.
Last edited by roswitina on Tue Aug 18, 2020 2:13 pm, edited 2 times in total.

User avatar
TinCanTech
OpenVPN Protagonist
Posts: 7825
Joined: Fri Jun 03, 2016 1:17 pm

Re: Testing WinTUN: Failure

Post by TinCanTech » Tue Aug 18, 2020 1:37 pm

This is a Beta test version and so there are bound to be problems.

As for the privilege message, it is correct. The wintun driver must be using SYSTEM privilege.

The developer team are working on a more user friendly way to achieve this.

If you want to try again then you must login as a non-admin or non-primary account to your PC.

roswitina
OpenVpn Newbie
Posts: 7
Joined: Sat Sep 08, 2012 9:58 am

Re: Testing WinTUN: Failure

Post by roswitina » Tue Aug 18, 2020 1:45 pm

Thanks for the information.
I see that the problem is known and can work with the currently installed version.

Rosi

Clodo
OpenVPN User
Posts: 37
Joined: Mon Oct 10, 2011 11:25 pm

Re: [Solved] Testing WinTUN: Failure

Post by Clodo » Sat Sep 19, 2020 9:50 am

I encounter the same error

Code: Select all

ERROR:  Wintun requires SYSTEM privileges and therefore should be used with interactive service. If you want to use openvpn from command line, you need to do SYSTEM elevation yourself (for example with psexec).
if i simply open cmd.exe with "Run as administrator" and use openvpn from commandline, that have SYSTEM privileges.
I'm missing something, or i can try to fill a bug-report?

Clodo
OpenVPN User
Posts: 37
Joined: Mon Oct 10, 2011 11:25 pm

Re: [Solved] Testing WinTUN: Failure

Post by Clodo » Sat Sep 19, 2020 11:10 am

Also throw the same error if i use psexec (as suggested) with elevated -h

Code: Select all

r:\psexec64.exe -h "c:\Program Files\Openvpn\bin\openvpn.exe" r:\x.ovpn
same error.

stipa
OpenVpn Newbie
Posts: 2
Joined: Mon Nov 03, 2014 10:17 am

Re: [Solved] Testing WinTUN: Failure

Post by stipa » Mon Sep 21, 2020 7:04 am

You have two options:

- use openvpn-gui, which takes care of wintun initialization

- under elevated command prompt, run

Code: Select all

psexec -i -s cmd.exe
which creates command prompt under nt authority/system - there you can use openvpn from the command-line.

Post Reply