How to Set Up Wi-Fi on a Virtual Machine: 3 Methods + Troubleshooting

Connecting a virtual machine (VM) to Wi-Fi is a challenge faced by both novice and experienced users. Unlike a physical PC, where the adapter is connected directly, in a VM, the network operates through virtualization layers, which often causes confusion. The main problem is: The virtual machine does not see the host's Wi-Fi adapter. as a separate device, but uses it indirectly through the network settings in the hypervisor.

In this article we will look at how to properly set up a wireless connection in VirtualBox, VMware Workstation And Hyper-V, including rare cases where VM is required Direct access to the host's Wi-Fi adapter for tasks such as network monitoring or security testingWe'll also look at common errors (such as no internet connection after setup) and how to fix them without reinstalling the system.

Why a virtual machine can't see Wi-Fi: key reasons

Before setting up, it's important to understand how networking works in a VM. In 90% of cases, the problem lies in one of three factors:

• 🔌 Network mode in hypervisor chosen incorrectly (for example, Host-Only instead of NAT or Bridged).
• 🖥️ Virtual network adapter drivers are not installed in the guest OS (especially relevant for Linux).
• 📡 The host's Wi-Fi adapter is disabled. or blocked by antivirus/firewall.

Most hypervisors use it by default. NAT — a mode in which the VM "accesses" the Internet via the host's IP address. This is convenient for security, but is not suitable if you need the VM to be visible on the local network as a separate device (for example, for configuring a router). In such cases, you need Bridged (bridge mode).

⚠️ Attention: If you're using a corporate laptop, your Wi-Fi adapter may be blocked by domain policies. Check this in Device Manager host - If the adapter is displayed with an exclamation mark, contact your IT service.

Method 1: Setting up Wi-Fi via NAT (for Internet access)

Mode NAT — the simplest and most secure option for most tasks (surfing, updates, development). The VM accesses the internet via the host's IP but remains invisible to other devices on the network.

Instructions for VirtualBox:

1. Shut down the virtual machine.
2. Open Settings → Network.
3. In the field Connection type select NAT.
4. In the section Additionally install Adapter type — PCnet-FAST III (for Linux) or Intel PRO/1000 MT (for Windows).
5. Start the VM and check the connection (for example, with the command ping 8.8.8.8 in the terminal).

For VMware Workstation the steps are similar, but in the network settings you need to select NAT: Used to share the host's IP address.

Select NAT mode in the VM network settings | Make sure Wi-Fi is enabled on the host | Check the network adapter drivers in the guest OS | Ping to 8.8.8.8 or google.com -->

Method 2: Bridged mode for accessing the local network

If you need the VM to be visible on the local network as a separate device (for example, to configure a router or connect to network printers), use Bridged (bridged mode). In this case, the VM receives its own IP address from the router.

Step-by-step setup in VirtualBox:

1. Turn off the VM and open Settings → Network.
2. Select Connection type: Network bridge (Bridged).
3. In the field Name Please specify your Wi-Fi adapter (for example, Intel(R) Wi-Fi 6 AX200).
4. Start the VM and check the IP address (in Windows - ipconfig, in Linux - ifconfig or ip a).

IN VMware Bridge mode is configured via Bridged: Connected directly to the physical networkAfter applying the settings, the VM should receive an IP from the DHCP router (for example, 192.168.1.x).

⚠️ Attention: In bridge mode, some antiviruses (for example, Kaspersky or ESET) may block VM network activity, considering it suspicious. Add the VM's IP address to the firewall exceptions.

VirtualBox|VMware Workstation|Hyper-V|Parallels Desktop|Other-->

Method 3: Direct access to a Wi-Fi adapter (USB passthrough)

In rare cases it is required that the VM has direct access to the Wi-Fi adapter — for example, for:

• 🔍 Network security testing (like Kali Linux).
• 📡 Settings for specialized protocols (e.g. 802.11ac in monitor mode).
• 🖥️ Working with devices that require low-level access (like ESP32 or Raspberry Pi).

For this, technology is used USB-passthrough, which "transmits" a USB device (in this case, a Wi-Fi adapter) directly to the VM. Instructions for VirtualBox:

1. Connect the Wi-Fi adapter to the host (if it is an external adapter, for example, TP-Link TL-WN722N).
2. In the VM settings, go to USB → Add New USB Filter.
3. Select your adapter from the list (e.g. Realtek RTL8188EU).
4. Start the VM and install the drivers for the adapter in the guest OS.

IN VMware a similar function is called USB Compatibility and is configured in VM → Removable Devices.

Troubleshooting common Wi-Fi connection errors in VMs

Even after proper setup, problems may still arise. Here are the most common ones and how to fix them:

netsh int ip reset
netsh winsock reset

If the problem persists, check the hypervisor logs. VirtualBox they are in %USERPROFILE%\.VirtualBox\Machines\<VM_Name>\Logs. IN VMware - V C:\ProgramData\VMware\VMware Workstation\vmware.log.

Wi-Fi setup in Hyper-V

Hyper-V (the built-in Windows hypervisor) has its own nuances when working with Wi-Fi. The main difficulty is the lack of direct support for wireless adapters in External Virtual SwitchThis can be solved in two ways:

1. Creating a Wi-Fi-based virtual switch:

   New-VMSwitch -SwitchName "WiFiSwitch" -SwitchType External -NetAdapterName "Wi-Fi"

   Then connect the VM to this switch in the network settings.

2. Using NAT via PowerShell:

   New-NetIPAddress -IPAddress 192.168.100.1 -PrefixLength 24 -InterfaceAlias "vEthernet (WiFiSwitch)"
   New-NetNAT -Name "VMSwitchNAT" -InternalIPInterfaceAddressPrefix 192.168.100.0/24

   This will allow the VM to access the Internet through the host, even if the Wi-Fi adapter does not support it. Bridged.

IN Hyper-V can also be used Default Switch — it automatically creates a NAT network, but with limited functionality (for example, it is impossible to configure port forwarding).

⚠️ Attention: In Windows 11 Hyper-V may conflict with Windows Sandbox or WSL2If after setting up Wi-Fi in the VM the Internet on the host is lost, disable these functions in Turn Windows features on or off.

Security: Risks of Connecting a VM to Wi-Fi

Connecting a VM to a wireless network carries several risks that are often ignored:

• 🛡️ Data Leak: If a VM is infected with a virus, it can spread to the host or other devices on the network (especially in bridged mode).
• 🔍 Traffic interception: On public Wi-Fi networks, VM traffic can be intercepted (for example, if you are testing vulnerabilities in Kali Linux).
• 🔄 IP Conflicts: Manually setting up a static IP may cause conflicts with other devices on the network.

Safety recommendations:

• Use NAT For most tasks, this isolates the VM from the local network.
• Enable the firewall in the guest OS (e.g. ufw in Linux or Windows Defender).
• To test networks, use isolated environments (e.g. Host-Only + second adapter in NAT).

FAQ: Frequently asked questions about Wi-Fi in virtual machines