VMware ESXi and vSphere Cluster Management
Configure Bridged Networking in Oracle VirtualBox
Learn how to configure a VirtualBox guest with a Bridged Adapter so it receives network access directly from the same physical LAN as the host.
Bridged networking connects an existing VirtualBox guest virtual machine (VM) to the same physical network used by the host computer. The guest appears as a separate device on that network instead of hiding behind the host through NAT.
This configuration is useful when a guest must receive an address from the local router, contact other LAN systems, provide a test service, or use network services such as DNS and NTP directly. Because the guest is exposed to the LAN like another computer, apply normal firewall and security controls.
Prerequisites
- The host is the physical computer running Oracle VM VirtualBox.
- The guest VM is the virtual machine whose network connection you will configure.
- The host has a working physical network adapter, such as Ethernet or Wi-Fi.
- The host is connected to the intended LAN or other physical network.
- The network can accept an additional device, normally through DHCP or an administrator-approved static IP configuration.
- You understand basic IP addressing, subnets, default gateways, and DNS.
When practical, power off the VM before changing its virtual hardware settings. Some network changes can be made while a VM is running, but a powered-off VM makes the configuration state easier to verify.
What bridged networking means
Bridged Adapter is a VirtualBox attachment mode that places a guest VM on the host's physical network. The guest has its own virtual network adapter and normally its own MAC address, which is the link-layer identifier used by that adapter. It also normally receives its own IP address.
In bridged mode, the guest behaves as a separate networked device. A router or DHCP server can see the guest and assign it an address just as it would assign an address to another physical computer. This differs from NAT, where guest traffic is translated through the host and the guest is generally not directly visible as a peer on the physical LAN.
How VirtualBox bridging works
VirtualBox uses a host-side network filter driver, commonly called the net filter. The filter works with the physical host adapter selected in the VM settings.
- The guest sends a frame through its virtual network adapter.
- The VirtualBox net filter processes and injects that traffic through the selected host adapter.
- Frames received by the physical adapter can be delivered back to the guest's virtual adapter.
- The resulting virtual interface carries traffic between the guest and the external network.
The relationship is therefore: guest virtual network adapter, VirtualBox net filter, selected host physical adapter, and physical LAN or router. The host remains connected to the network, while the guest participates as an additional device.
What a bridged guest can access
A correctly configured guest can access the physical LAN similarly to the host, subject to routing, firewall rules, and network policy. It may use external services such as DNS for hostname lookups and NTP for time synchronization. It may also communicate with other LAN systems when the guest, destination system, and network permit that traffic.
| Mode | Guest visibility on physical LAN | Typical IP source | Typical use case |
|---|---|---|---|
| Bridged Adapter | Appears as a separate device on the physical LAN | LAN DHCP or approved static configuration | Testing LAN services, receiving direct LAN access, or making a guest available to other permitted systems |
| NAT | Usually hidden behind the host's translated connection | VirtualBox NAT service | Simple outbound guest access without adding a directly visible LAN device |
| Internal Network | Not connected to the physical LAN | Guest configuration or an internal DHCP service | Isolated guest-to-guest networking |
Choose the correct host adapter
The adapter selected in VirtualBox must be the host interface that currently carries the connection to the target network.
- Choose the active wired Ethernet adapter when the host is connected by cable.
- Choose the active Wi-Fi adapter when the host is connected wirelessly.
- Do not normally choose a VPN, loopback, host-only, virtual, or disconnected adapter for access to the physical LAN.
Selecting the wrong interface can leave the guest without connectivity or connect it to a different network. If the host changes from Ethernet to Wi-Fi, or if a VPN becomes active, review the bridged adapter selection.
Configure Bridged Adapter in VirtualBox Manager
- Open Oracle VM VirtualBox Manager.
- Select the existing virtual machine.
- Open the VM's Settings dialog.
- Open the Network section.
- Choose the adapter to configure, commonly Adapter 1.
- Select Enable Network Adapter.
- Set Attached to to Bridged Adapter.
- In the adapter-name field, select the host's active Ethernet or Wi-Fi adapter connected to the intended network.
- Select OK to save the setting.
- Start or restart the guest if required.
| VirtualBox setting | Recommended value or action | Purpose |
|---|---|---|
| Enable Network Adapter | Selected | Connects the guest's virtual network adapter |
| Attached to | Bridged Adapter | Places the guest on the host's physical network |
| Host adapter selection | Active Ethernet or Wi-Fi adapter for the target LAN | Determines which physical network carries guest traffic |
| Guest DHCP or static configuration | Use DHCP unless the network administrator provides valid static settings | Supplies the guest's IP address, route, and DNS configuration |
| Post-configuration testing | Check address, route, DNS, gateway, LAN, and external access | Confirms each part of the connection |
Configure the guest's IP addressing
In the common case, the guest operating system uses DHCP. The LAN's DHCP service assigns an IP address from the same network as the host, along with a subnet or prefix, default gateway, and DNS servers.
Use a static address only when the network requires it or an administrator has assigned one. The address must be unused and valid for the subnet. The guest also needs the correct prefix or subnet mask, gateway, and DNS servers. A static address must not be guessed or copied from the host.
Verify a Linux guest
ip addr
ip route
ping -c 4 <default-gateway-ip>
getent hosts <hostname>Use ip addr to find the guest address, ip route to check the default route, and getent hosts to test hostname resolution. The gateway ping tests local reachability, while the hostname lookup tests DNS.
Verify a Windows guest
ipconfig /all
ping <default-gateway-ip>
nslookup <hostname>ipconfig /all displays the address, gateway, DHCP state, and DNS servers. Use ping for gateway reachability and nslookup for DNS testing.
Validate connectivity in stages
- Confirm that the guest's network adapter is enabled and has an address appropriate for the target LAN.
- Verify the default route and test the local gateway.
- Test access to another permitted device on the same LAN.
- Test DNS by resolving a known hostname.
- Test external connectivity if the network policy permits it.
- Check that required services, such as NTP, can communicate if the guest depends on them.
Testing in this order helps identify the failure layer. A gateway failure suggests an adapter, link, addressing, or local network problem. Successful IP access with failed hostname resolution usually indicates a DNS problem. Successful internet access with failed LAN access can indicate firewalls, client isolation, segmentation, or a service that is not listening on the expected interface.
Optional VBoxManage configuration
You can configure the first virtual network adapter from the command line instead of using VirtualBox Manager:
VBoxManage modifyvm "<vm-name>" --nic1 bridged --bridgeadapter1 "<host-adapter-name>"Replace both placeholders with the actual VM name and the host adapter name reported by VirtualBox. The adapter number must match the adapter being configured: use the corresponding --nicN and --bridgeadapterN options for another adapter.
Security and network considerations
A bridged VM is exposed to the same network environment as a separate physical machine. Services running in the guest may be reachable by other systems if routing and firewall rules allow them.
- Enable and correctly configure the guest operating-system firewall.
- Keep the guest operating system and installed services updated.
- Expose only the services required for the task.
- Remember that the guest MAC address may appear in switch, wireless, DHCP, or access-control systems.
- Follow organizational network rules and obtain approval for registered devices or static addresses.
Troubleshooting bridged networking
The guest has no network connection
- Verify that Enable Network Adapter is selected.
- Confirm that Attached to is set to Bridged Adapter.
- Select the host interface that is actively connected to the target network.
- Restart the guest network connection or reboot the guest.
The guest does not receive an IP address
DHCP may be unavailable or blocked, the network may reject an additional MAC address, or the wireless or managed network may restrict bridged clients. Inspect the guest's address and route configuration, confirm DHCP availability, and check whether device registration or MAC limits apply. Use a static configuration only when valid settings are supplied by the network administrator.
The guest reaches IP addresses but not hostnames
Check the DNS servers received or configured in the guest. Use getent hosts on Linux or nslookup on Windows. Correct the DHCP or static DNS configuration if the lookup fails.
The guest reaches the internet but not another LAN device
Test the gateway and target device separately. Review guest and destination firewalls, check for client isolation or network segmentation, and verify that the target service is listening on the expected network interface.
Bridged Adapter or the expected host interface is unavailable
VirtualBox networking components or permissions may be missing, the host adapter driver may be disabled or unsupported, or the host may have no active compatible adapter. Check the host adapter status and VirtualBox network driver installation. Restart VirtualBox or the host after correcting driver issues, then select an active supported physical adapter.
Practical examples
Give a Linux guest a LAN address
If the host is connected to a home or office router through Ethernet, select that Ethernet adapter for Bridged Adapter mode. After the guest starts, DHCP normally provides an address from the same router. The guest can then use permitted DNS and NTP services and communicate with other permitted LAN systems.
Connect a Windows guest to a local test server
If the host can reach a test server on the same physical LAN, bridge the Windows guest to the host adapter carrying that LAN connection. The guest appears as another LAN device and can connect to the server when routing and firewall rules allow it.
Use an administrator-assigned static address
Enter the unused IP address, subnet mask or prefix, gateway, and DNS servers supplied by the network administrator in the guest. After bridged mode is enabled, test the gateway, the intended LAN service, DNS resolution, and any approved external access.
Exam-relevant notes
- Bridged networking connects a guest to the host's physical network and gives the guest a separate network identity.
- The VirtualBox net filter processes traffic through the selected physical host adapter.
- The selected adapter must be the active Ethernet or Wi-Fi interface for the intended network, not a VPN, loopback, or unrelated virtual adapter.
- DHCP commonly supplies the guest's address, gateway, and DNS settings.
- Bridged mode provides direct LAN presence but also exposes the guest to LAN security risks.
- NAT translates traffic through the host, while Internal Networking isolates guests from the physical LAN.
For the configuration sequence, select the VM, open Settings > Network, enable the adapter, choose Bridged Adapter, select the active host adapter, save with OK, and validate the guest's address, route, DNS, and connectivity.