Code: Select all
020-08-04 13:07:04 us=384558 open_tun
2020-08-04 13:07:04 us=387556 MANAGEMENT: Client disconnected
2020-08-04 13:07:04 us=387556 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-04 13:07:04 us=387556 Exiting due to fatal errorI've tried installing as user and as administrator -- no difference. I've tried letting openvpn-gui start with windows, and manually (both as user and administrator) -- no difference. A friend of mine, who has basically the same settings in his .ovpn as i do, CAN get it to work if he starts it via openvpn-gui. Here is the top of our .ovpn (cutting off the certs):
Client config
1
client
2
dev tun
3
windows-driver wintun
4
route-method exe
5
route-delay 2
6
proto tcp-client
7
remote xx.xx.xx.xx 443
8
tls-version-min 1.2
9
persist-key
10
persist-tun
11
ca [inline]
12
cert [inline]
13
key [inline]
14
dh [inline]
15
tls-auth [inline]
16
key-direction 1
17
remote-cert-tls server
18
nobind
19
comp-lzo no
20
keepalive 30 120
21
remap-usr1 SIGTERM
22
status openvpn-status.log
Also, eventually i need to get OpenVPN (with wintun) working without a user logged in as our systems are used for M2M monitoring. I built some scripts to allow this on our older systems. But from reading the explanations about OpenVPN Interactive Service and OpenVPN-gui, i am wondering if it will allow this?
Any assistance with this Proof of Concept for v2.5 would be appreciated.