Open vielmetti opened 5 years ago
EDIT: mattock's reply below is more accurate about what includes what and has MUCH better links.
"This tool" -- I assume to be the tap-windows6 driver and the program that installs it.
It looks like the OpenVPN project hosts its releasesbuild outputs here:
https://build.openvpn.net/downloads/releases
There was a mailing list discussion about some of the recent builds there, but it links to a slightly older build and the links have some cruft at the end. The trick is to understand the projects' composition model: OpenVPN's installer simply embeds and runs the EXE that tap-windows6 produces. The tap-windows-*-Win10.exe
that is 9.23.3-I601
(and, most likely, greater) includes and successfully installs the ARM64 driver (for me). As I understand it, openvpn-install-2.4.7-I607-Win10.exe
is still using the older tap-windows6 release to avoid breaking certain things; work to surmount this is underway.
If you wish to try this combination, you can run the OpenVPN installer and uncheck the "Install TAP Driver" checkbox, then run the tap-windows6 installer (one with ARM64 included) yourself. (This installs the x86 system tray tool which, when I tested it a year ago, works quite well with the ARM64 driver.) just use mattock's OpenVPN-install Win10 link below.
I can confirm that the latest tap-windows6 installs and doesn't crash my ARM64 system.
A more literal interpretation of your question is about the tap-windows6 installer. This is an EXE that is emitted by NSIS, and, last I heard, they do not have plans to add ARM64 EXE support--but it doesn't need to, since the x86 installers it produces work magnificently just like they do on x64.
Some clarifications which hopefully don't just confuse things further :smile:. The latest OpenVPN installers embed tap-windows6 installers that include arm64 tap-windows6 drivers:
The only difference between these two is the code signature in the tap-windows6 driver itself:
While there is a perfectly functional arm64 driver in the Win7 version, the fact that it is cross-signed prevents it from loading on actual Windows arm64 devices, which are all Windows 10-based.
The above two OpenVPN installers bundle the following tap-windows6 installers:
At the moment we don't have an updated version of tap-windows6 driver available for Windows Server 2016/2019. But that probably does not affect you.
@mattock, I just tried the full OpenVPN installer you linked and it works wonderfully. (I don't currently have a VPN to hook it up to, so I'll have to try that another day.)
@vielmetti, does the tap-windows
installer mattock linked work for you?
Hi,
On Thu, May 02, 2019 at 10:36:26PM +0000, Jon Kunkee wrote:
@mattock, I just tried the full OpenVPN installer you linked and it works wonderfully. (I don't currently have a VPN to hook it up to, so I'll have to try that another day.)
This sounds quite promising :-) - if you need a VPN profile to have something to test "actually moving packets", just let me know (mail, not here).
gert -- "If was one thing all people took for granted, was conviction that if you feed honest figures into a computer, honest figures come out. Never doubted it myself till I met a computer with a sense of humor." Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany gert@greenie.muc.de
Mostly for fun, I installed Win 10 Pro on a Raspberry Pi (using the tool at https://github.com/WOA-Project/WOA-Deployer-Rpi). I then followed the instructions above, installing OVPN (w/o TAP) then TAP. The installs ran fine, and I was able to drop in a config and connect to a server.
Just wanted to mention that it works!
@thomas-taylor, I love hearing about unsupported Windows 10 on ARM configurations working. It means the product is solid :)
I'm even happier knowing that this driver worked for you!
Please note that if you use @mattock's links, you should not need my 'w/o TAP' work--it should just work out of the box, no tweaks needed.
EDIT: I edited my earlier comment to use strikethrough on those instructions. I don't think thomas-taylor will be the only one visiting this page. :)
Hi,
On Wed, May 22, 2019 at 11:20:10AM -0700, Jon Kunkee wrote:
I'm even happier knowing that this driver worked for you!
Well, thank you, Jon, for all your work on ARM building and such :-)
Took insanely far too long, but we're getting there!
gert -- "If was one thing all people took for granted, was conviction that if you feed honest figures into a computer, honest figures come out. Never doubted it myself till I met a computer with a sense of humor." Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany gert@greenie.muc.de
@jkunkee, Thanks, I read that too fast. I uninstalled and then just ran the regular Win 10 install (@mattock's link) with default options (including TAP), and it worked fine, as you indicated it would.
Also, thanks to you and all involved for the work getting it to ARM. I want one of the Snapdragon laptops, but lack of OpenVPN was a deal-breaker. Now I'm just wondering how long I might have to wait for one with the 8cx processor.
Release 2.5.3 is available for arm64 platform. https://swupdate.openvpn.org/community/releases/OpenVPN-2.5.3-I601-arm64.msi
You could download arm64 openvpn artifacts from Github Actions: https://github.com/OpenVPN/openvpn/suites/3027135495/artifacts/68636358
tap-windows6 arm64 msm: http://build.openvpn.net/downloads/releases/tap-windows-9.24.6-I601-arm64.msm
Is it possible to download an arm64 version of this tool from somewhere, or do I have to build from source?