From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Joachim Lindenberg <wireguard@lindenberg.one>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Hyper-V 2019: unable to create wintun device: no interfaces found
Date: Sun, 25 Aug 2019 12:35:30 -0600 [thread overview]
Message-ID: <CAHmME9o7PrETcRuLdO7DnpUiKNyO1AyL0qY4Xa1XFT4FPVsVvQ@mail.gmail.com> (raw)
In-Reply-To: <014e01d55b69$d19256e0$74b704a0$@lindenberg.one>
On Sun, Aug 25, 2019 at 11:23 AM Joachim Lindenberg
<wireguard@lindenberg.one> wrote:
> my experiments were actually roughly three weeks ago with versions .18 and .19, and that mail was somehow stuck..
> Just retried with .22, and the good news is that I was able to set up a tunnel between a Hyper-V as a server and a windows client. The old error on wintun is gone.
Good to hear.
> trick wireguard to work around the dynamic IP issue most Germans face. With the Ubuntu vms I can ping the server from the client, and if it is unreachable I am pulling down the interface and then up again.
Not sure I understand exactly. Is the goal to simply
change/re-randomize your listen-port due to some weird quirks of your
router's NAT table, in which case `wg set wg0 listen-port 0` will
probably work better than down/up? Or is this actually a case where
adding PersistentKeepalive=25 could fix things? Both of these options,
anyhow, are available in the Windows client. wg.exe is installed into
system32 and works as expected.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-08-25 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 12:15 Joachim Lindenberg
2019-08-25 15:54 ` Jason A. Donenfeld
2019-08-25 17:23 ` AW: " Joachim Lindenberg
2019-08-25 18:35 ` Jason A. Donenfeld [this message]
2019-08-25 18:52 ` 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=CAHmME9o7PrETcRuLdO7DnpUiKNyO1AyL0qY4Xa1XFT4FPVsVvQ@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=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).