Hi,
On Tue, Aug 18, 2020 at 08:23:35AM +0200, Gert Doering wrote:
> This can also happen if you run the GUI with admin privs (because then
> it will not use the iservice *but* openvpn needs *more* privs than
> "just administrator", and wintun can not be used at all).
Continueing this thought: I t
Hi,
On Tue, Aug 18, 2020 at 12:06:18AM -0300, Rafael Gava wrote:
> 2020-08-17 19:15:39 us=424470 ERROR: Wintun requires SYSTEM privileges and
> therefore should be used with interactive service. If you want to use
> openvpn from the command line, you need to do SYSTEM elevation yourself
> (for ex
Hello Everyone
Could you please give me an insight of what is going here... :-)
I'm trying to use and test the openvpn version 2.5_beta1 with the wintun
interface on a windows 10 machine based on a release built from the source
code.
In order to do that, I'm using the openvpn-vagrant with the
ope
Final update:
So, IPv4 not working was my own error .. sorry for the false alarm.
As for the non-admin user trying to install drivers, this does still happen.
However, what I think is happening is this:
1. Login as admin - install openvpn OK
2. logout/login as normal user
3. Openvpn does "Sett
