wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Edward Vielmetti <edward.vielmetti@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Installing Wireguard on Windows 10 on Arm; "wintun" device
Date: Tue, 31 Dec 2019 22:38:00 -0500	[thread overview]
Message-ID: <CAPRZce0Ruqyrei0OykZ-d-gK97TGTq4wMPy2OrrVeUEbvm=sjA@mail.gmail.com> (raw)


[-- 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

             reply	other threads:[~2020-01-03 15:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-01  3:38 Edward Vielmetti [this message]
2020-01-03 15:56 ` Installing Wireguard on Windows 10 on Arm; "wintun" device Jason A. Donenfeld
2020-01-03 18:05   ` Justin Guiao

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='CAPRZce0Ruqyrei0OykZ-d-gK97TGTq4wMPy2OrrVeUEbvm=sjA@mail.gmail.com' \
    --to=edward.vielmetti@gmail.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).