wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Joachim Lindenberg" <wireguard@lindenberg.one>
To: <wireguard@lists.zx2c4.com>
Subject: Hyper-V 2019: unable to create wintun device: no interfaces found
Date: Sun, 4 Aug 2019 14:15:25 +0200	[thread overview]
Message-ID: <036a01d54abe$4c049cb0$e40dd610$@lindenberg.one> (raw)


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

Hello,

I am using Wireguard for quite some time on Ubuntu, and am now trying to use
it on Hyper-V 2019 as well. My goal is to set up a VPN between two Hyper-V
systems and allow connections between the virtual machines hosted (including
Samba AD DCs).

I downloaded and installed Wireguard for Windows, and created a tunnel
configuration on server and client. However when I try to activate any of
these, I get the message “Unable to create Wintun device: no interfaces
found” on both sides.

To me it doesn´t look  like an issue with the configuration but more likely
WinTun is missing (tried to download separately, but as it is a .msm I
assume that is included in wireguard installation) or does not work with
Hyper-V 2019.

Any suggestion?

Thanks, Joachim


[-- Attachment #1.2: Type: text/html, Size: 2933 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:[~2019-08-25 15:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-04 12:15 Joachim Lindenberg [this message]
2019-08-25 15:54 ` Hyper-V 2019: unable to create wintun device: no interfaces found Jason A. Donenfeld
2019-08-25 17:23   ` AW: " Joachim Lindenberg
2019-08-25 18:35     ` Jason A. Donenfeld
2019-08-25 18:52       ` AW: " news
2019-08-25 18:54         ` Jason A. Donenfeld
2019-08-25 19:04           ` AW: " news

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='036a01d54abe$4c049cb0$e40dd610$@lindenberg.one' \
    --to=wireguard@lindenberg.one \
    --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).