Hello Jason, all, 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. I didn´t have the opportunity to check with two Hyper-Vs yet, and I am also unsure whether I actually want to change the workaround (using an Ubuntu vm on either side as routers) now with the windows version in that early stage, in particular as I also had to 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. This can probably also be done with the application on Windows by activating and deactivating the interface, but I definitely need this to be automated somehow, be it a script or preferably wireguard supporting dynamic ip addresses out of the box. Thanks, Joachim
-----Ursprüngliche Nachricht----- Von: Jason A. Donenfeld <[email protected]> Gesendet: Sunday, 25 August 2019 17:54 An: Joachim Lindenberg <[email protected]>; Simon Rozman <[email protected]> Cc: WireGuard mailing list <[email protected]> Betreff: Re: Hyper-V 2019: unable to create wintun device: no interfaces found On Sun, Aug 25, 2019 at 9:34 AM Joachim Lindenberg <[email protected]> wrote: > > 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 Interesting. We just reworked the Wintun installation process, to hopefully make it more reliable. Could you try again, and perhaps provide a bit of logging too? Try running this: msiexec /log send-to-jason-please.txt /i https://download.wireguard.com/windows-client/wireguard-amd64-0.0.22.msi _______________________________________________ WireGuard mailing list [email protected] https://lists.zx2c4.com/mailman/listinfo/wireguard
