Installing Wireguard on Windows 10 on Arm; "wintun" device

Installing Wireguard on Windows 10 on Arm; "wintun" device

[Edward Vielmetti]

[-- Attachment #1.1: Type: text/plain, Size: 943 bytes --]

I have a Windows 10 on Arm laptop (Lenovo Yoga C630) that I'm
looking to install Wireguard on.

Generally speaking, Windows 10 on Arm runs either arm64 or win32
binaries, but not win64, so I installed the 32-bit x86 version of Wireguard
and the software came up fine.

I created a config to point at my existing Wireguard server, but was stymied
by the need to install a "Wintun" device. Apparently this doesn't work,
with the error message as follows

2019-12-31 22:30:55.300: [TUN] [wg0] Unable to create Wintun interface:
Error creating interface: No driver for device "Wintun" installed

I do see this commit

https://git.zx2c4.com/wintun/commit/?id=f48b0b2883e849a2c91ccbfa72fa0691461c7cda


which makes me think there's some arm64 work going on somewhere, and it's
possible
that I botched the install at some point, so I'd welcome any guidance or
expectations.

thanks

Ed
-- 
Edward Vielmetti +1 734 330 2465
edward.vielmetti@gmail.com

[-- Attachment #1.2: Type: text/html, Size: 1531 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

Re: Installing Wireguard on Windows 10 on Arm; "wintun" device

[Jason A. Donenfeld]

Wintun supports the arm64 kernel. Go supports an arm userland. Ideally
these should match, but they don't right now. It should be possible to
get arm userland talking to the arm64 kernel with some careful struct
poking, but it doesn't sound too pleasant. The best thing to do would
be to get Microsoft and/or Google to port Go to arm64.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

Re: Installing Wireguard on Windows 10 on Arm; "wintun" device

[Justin Guiao]

[-- Attachment #1.1: Type: text/plain, Size: 1279 bytes --]

@Edward I've compiled wintun to arm64 and installed it on my Surface Pro X
without issue, although the driver is unsigned as it was just for testing.
However, as Jason mentioned the 32-bit WireGuard client cannot communicate
with it. I'm rather bullish on the windows on arm platform and hope to see
go on arm64 to enable it.

@Jason is go on arm64 to compile a 64-bit gui to communicate with the arm64
wintun drive a necessity? I know OpenVPN uses a 64bit win-tap driver with a
32-bit client (most likely x86 but could be arm32), although that is
probably comparing apples to oranges. The official Cisco AnyConnect client
for windows on arm also mixes an arm64 driver with a 32-bit gui.

Regards,


On Fri, Jan 3, 2020, 7:57 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> Wintun supports the arm64 kernel. Go supports an arm userland. Ideally
> these should match, but they don't right now. It should be possible to
> get arm userland talking to the arm64 kernel with some careful struct
> poking, but it doesn't sound too pleasant. The best thing to do would
> be to get Microsoft and/or Google to port Go to arm64.
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>

[-- Attachment #1.2: Type: text/html, Size: 1968 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard