On Thu, Aug 4, 2016 at 6:53 PM, debbie10t <debbie...@gmail.com> wrote:
> Hi > > So windows 10 as a Server. > > === > > General details: > Non admin Win10 unmodified user > Using OVPN GUI > OVPN Interactive service started and used > Win10 Tun Server (auto + manual) > IPv4 + IPv6 In average constant use > ~20 Clients virtual, local and remote > win xp/7/10 +linux > > (Todo: --server-bridge/tap .. maybe) > > Tested using: > cfg 1. --server & --server-ipv6 *no* CCD files in use > cfg 2. --ifconfig & --ifconfig-ipv6 CCD files in use > > Reminder: --keep6alive --ping6 etc > See: > https://forums.openvpn.net/viewtopic.php?f=4&t=22119#p63274 > > === > > > 24 hours now with Zero hiccups. > Glad to know.. > > Selva, > > 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. 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. Thanks, Selva
