n2n Add windows package

Add windows package

Open emanuele-f opened this issue 5 years ago • 6 comments

Providing pre-built executables to download will be nice. I'd avoid making an installer since the only requirement is to install the tap driver (a simple link can be enough), whereas the AES support can be provided with a static OpenSSL linkage (see https://github.com/ntop/n2n/blob/dev/doc/Windows.md)

Mar 03 '19 21:03 emanuele-f

Very well, thank you very much!

Mar 06 '19 10:03 lucktu

Regarding deploying n2n on Windows once it's on e.g Github releases.

I've tested n2n-gui and can confirm it still works if you replace edge binary with one build from latest dev. There seems to be several other projects as well.

It's a very good idea to use the newest NDIS6 tap-windows driver in the package as at least the one bundled in sourceforge version is the old XP one, likely buggy or poorly supported on newer Windows 10 versions.

Builds for tap-windows are on openvpn's server: http://build.openvpn.net/downloads/releases

Sadly the right driver that installs is a bit annoying to get as the drivers in .zip archives are not fully signed, only the installers have the newest signatures. e.g At time of writing that would be: tap-windows-9.23.3-I601.exe

Whether the windows package has UI or not, I'd suggest using chocolatey as tap-windows and dependent libs like openssl and available so n2n could just depend on them.

By chocolatey's conventions the command-line version might be n2n.portable and installable/gui version n2n.install.