From: Justin Guiao <justing6@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Installing Wireguard on Windows 10 on Arm; "wintun" device
Date: Fri, 3 Jan 2020 10:05:13 -0800 [thread overview]
Message-ID: <CAG7uUwKoafqVCvkX4uoC1k=G66k4HU=m=WmOc0Z1PV=287t7wA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pNoKwUpWg1QhH9+EKYGXBT7MODbP-nD22cV3Nd7kZMjw@mail.gmail.com>
[-- 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
prev parent reply other threads:[~2020-01-09 6:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 3:38 Installing Wireguard on Windows 10 on Arm; "wintun" device Edward Vielmetti
2020-01-03 15:56 ` Jason A. Donenfeld
2020-01-03 18:05 ` Justin Guiao [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAG7uUwKoafqVCvkX4uoC1k=G66k4HU=m=WmOc0Z1PV=287t7wA@mail.gmail.com' \
--to=justing6@gmail.com \
--cc=Jason@zx2c4.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).