Hi,
In Delft we talked about issues with Windows version of OpenVPN quite a
lot. Of the top of my hat I can recall the following isuses:
- The tap-windows/tap-windows6 drivers have fairly bad performance
- In Windows 10 there are DNS leaks
- The service wrapper (openvpnserv.exe) is effectively broken for
Windows 8 and later
- The service wrapper has very limited functionality
- The OpenVPN-GUI we bundle has several major issues, most related to
having to run it as an admin
- Suspend/hibernate seems to break OpenVPN tunnels quite often
- Building for Windows is and has always been a pain
In a nutshell, Windows development a timesink and nobody wants to do it
and/or does not have the required skills. Moreover, nobody wants to be
tagged as the "Windows guy", because that would mean being the go-to
person for all Windows problems.
I'm thinking it might make sense to create a dedicated Windows team that
could share the burden of Windows issues amongst themselves, without any
one person gettings tagged the "Windows guy". I would naturally be part
of the team, because I already build the official OpenVPN installers and
tap-windows drivers, plus I've worked with openvpn-gui quite a lot and
am working on a replacement for openvpnserv.exe.
The Windows team could have a separate board on OpenVPN forums and maybe
even a separate IRC channel. This is fairly typical arrangement in Linux
distributions, which have topic- and language-specific groups. We could
then point people with Windows issues/patches/development questions etc.
to the Windows team.
Thoughts?
--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
