Macrium Support Forum

WLAN on Virtual Machine created by viBoot with Windows10 Hyper-V

https://forum.macrium.com/Topic23537.aspx

By Vulpus - 22 May 2018 8:46 AM

Hello,

I want to use Wi-Fi on the virtual machines I created with ViBoot. I have read neither in the manual, nor in the forum articles about it.

I need advice. Can someone answer this question to me or name sources and instructions?

Thanks in advance!
By JamieW - 22 May 2018 9:11 AM

Hi Vulpus,

The networks available to the virtual machines are configured via Hyper-V.

Please see the following link for information on creating virtual networks with Hyper-V:
https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/connect-to-network

Kind Regards,
Macrium Support
By Vulpus - 22 May 2018 10:17 AM

[quote]
JamieW - 22 May 2018 9:11 AM
Hi Vulpus,

The networks available to the virtual machines are configured via Hyper-V.

Please see the following link for information on creating virtual networks with Hyper-V:
https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/connect-to-network Mit

freundlichen Grüßen,
Macrium Support
[/Zitat]

Thank you, JamieW
By jphughan - 22 May 2018 12:03 PM

Building on Jamie’s answer, starting with Win10 1709, Hyper-V has a “Default Switch” that works basically like the NAT function on other hypervisors. It is often the most convenient option if you just want your VMs to be able to access the actual network that your PC is on, since unlike an external switch you might create for this purpose, you do not have to map the default switch to a specific physical network interface, which means that you do not have to keep updating that mapping if the network interface that gives your PC connectivity changes, such as switching between wired and Wi-Fi. An external network mapped to a Wi-Fi adapter can also cause both your host and VMs to start having DHCP problems in some cases (especially if you have a DHCP reservation for your host’s Wi-Fi MAC address), while the default switch would not. The catch is that with the default switch, the VMs are behind a NAT interface, so other devices on your network would not be able to initiate inbound connections to your VM, which can be a problem if your VM wants to host something for other devices on the network. In that case, you would need an external switch instead, which would give your VM an IP on the real network’s subnet. Otherwise, the default switch is the way to go.

Finally, if you like all of the default switch benefits I just described but aren’t running Win10 1709, then if you’re running at least Win10 1607, you can achieve almost the same thing by creating an INTERNAL network, adding a NAT rule on your host with a single PowerShell command, and then configuring static IPs in the VM and the internal network interface on your host. I can elaborate on that if needed.