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 error
I'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
client
dev tun
#dev-node TAP_Win32
windows-driver wintun
route-method exe
route-delay 2
proto tcp-client
remote xx.xx.xx.xx 443
tls-version-min 1.2
persist-key
persist-tun
ca [inline]
cert [inline]
key [inline]
dh [inline]
tls-auth [inline]
key-direction 1
remote-cert-tls server
nobind
comp-lzo no
keepalive 30 120
remap-usr1 SIGTERM
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.