On 05/08/16 03:04, Selva Nair wrote:
On Thu, Aug 4, 2016 at 6:53 PM, debbie10t <debbie...@gmail.com> wrote:
Hi
So windows 10 as a Server.
If you have any specific tests please send me details.
Tasks needing admin access happens early on when the server starts so this
looks good especially since you tested ipv6 as well.
One thing to try:
With the server running, edit the config to change the tunnel network (ip
and pool) and issue a SIGHUP to re-read the config (reconnect from the GUI
status window will do this). The old routes should get torn down (log will
show route deletion via service succeeded) the ip should change to the new
one and new routes get added etc.
This worked no problem.
Although not related to the interactive service, you could also test
running the server on a port < 1024. This being windows I suppose binding
to "privileged" ports doesn't require admin rights.
Have not tried this yet.
However, during my testing the following happened:
I installed the first server in /program files/openvpn/config and running
as standard-user with openvpn GUI & IService, this worked no problem.
Then I tried with the config file in /users/user/openvpn/config and running
as standard-user:user with gui & IService, Starting the server, I was
prompted
to add my user to the openvpn administrators group.
I am not sure if this is intended behaviour, that the group membership is
*only* prompted when using user/openvpn/config/file.ovpn ?
--
