WireGuard Archive on lore.kernel.org
 help / color / Atom feed
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
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 --]

<div dir="auto"><div>@Edward I&#39;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&#39;m rather bullish on the windows on arm platform and hope to see go on arm64 to enable it. <div dir="auto"><br></div><div dir="auto">@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. </div><div dir="auto"><br></div><div dir="auto">Regards, </div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jan 3, 2020, 7:57 AM Jason A. Donenfeld &lt;<a href="mailto:Jason@zx2c4.com" rel="noreferrer noreferrer" target="_blank">Jason@zx2c4.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Wintun supports the arm64 kernel. Go supports an arm userland. Ideally<br>
these should match, but they don&#39;t right now. It should be possible to<br>
get arm userland talking to the arm64 kernel with some careful struct<br>
poking, but it doesn&#39;t sound too pleasant. The best thing to do would<br>
be to get Microsoft and/or Google to port Go to arm64.<br>
_______________________________________________<br>
WireGuard mailing list<br>
<a href="mailto:WireGuard@lists.zx2c4.com" rel="noreferrer noreferrer noreferrer" target="_blank">WireGuard@lists.zx2c4.com</a><br>
<a href="https://lists.zx2c4.com/mailman/listinfo/wireguard" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">https://lists.zx2c4.com/mailman/listinfo/wireguard</a><br>
</blockquote></div>
</div></div>

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

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

      reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-01  3:38 Edward Vielmetti
2020-01-03 15:56 ` Jason A. Donenfeld
2020-01-03 18:05   ` Justin Guiao [this message]

Reply instructions:

You may reply publically 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

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com
	public-inbox-index wireguard

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git