Overview
Bridged networking is a fundamental virtualization networking configuration that creates a direct connection between a virtual machine (VM) and the host computer's physical network adapter. In this mode, the VM functions as an independent network participant, with its own MAC address and IP address assigned by the network's DHCP server or manually configured. This approach essentially treats the VM as another physical machine on the same network segment as the host.
How Bridged Networking Works
Bridged networking operates by creating a network bridge, which is a software construct that connects the VM's virtual network interface to the host's physical network adapter. The bridge acts as a transparent switch, forwarding network traffic between the VM and the physical network without modification or translation.
When a VM is configured in bridged mode:
- The hypervisor creates a virtual network interface card (vNIC) for the VM
- This vNIC is logically connected to the host's physical NIC through a bridge device
- The VM sends and receives packets directly on the physical network segment
- Network switches and routers on the physical network see the VM as a regular network node with its own MAC address
- The VM can communicate with any device on the physical network without NAT translation
Key Components and Architecture
Network Bridge: The software component running on the host that connects the VM's virtual network interface to the physical adapter. Common implementations include Linux bridges (br0, br1) and Windows Hyper-V virtual switches in bridged mode.
Virtual NIC: Each bridged VM has its own virtual network interface card with a unique MAC address. This MAC address may be either inherited from the host or automatically generated, depending on hypervisor settings.
Physical Network Adapter: The host's actual network interface card (Ethernet, Wi-Fi) that connects to the physical network infrastructure.
DHCP Integration: Bridged VMs typically receive IP addresses from the network's DHCP server, making them indistinguishable from physical machines to the DHCP infrastructure.
Comparison with Other Networking Modes
NAT (Network Address Translation) Mode: In NAT mode, the host acts as a router, and the VM communicates through the host's IP address. The VM is hidden from the physical network and typically cannot be accessed directly from external machines. Bridged mode differs by giving the VM direct visibility on the network.
Host-Only Mode: Host-only networking creates an isolated network between the host and VMs only, with no access to the physical network. Bridged mode, by contrast, provides full external network connectivity.
Configuration Considerations
When implementing bridged networking, administrators must consider several factors:
- Network Adapter Selection: Choosing which physical adapter to bridge to, especially important on multi-NIC systems
- MAC Address Assignment: Deciding whether to use the host's MAC or generate unique MAC addresses for each VM
- IP Address Management: Ensuring DHCP scope is sufficient or manually assigning addresses to avoid conflicts
- Network Permissions: Verifying that physical switch configurations allow bridging; some network security policies may restrict bridged VMs
- Performance Implications: Bridged mode typically has lower network latency than NAT since packets don't require address translation
Common Use Cases
Server Hosting: Bridged networking is ideal for VMs acting as production servers that need direct, unrestricted access to the corporate network and require inbound connections from external clients.
Network Testing and Development: When testing network-dependent applications or simulating multi-machine environments, bridged VMs can participate as legitimate network nodes, receiving real IP addresses and responding to network services like DNS and DHCP.
Datacenter Virtualization: In data centers, bridged networking enables VMs to integrate seamlessly into existing network infrastructure without additional routing or NAT rules.
Legacy Application Migration: Applications designed to run on physical machines and expecting direct network access benefit from bridged configurations, as the VM behaves identically to a physical machine from a networking perspective.
Advantages and Disadvantages
Advantages:
- VM appears as a legitimate device on the physical network with its own IP address
- Inbound connections from external machines are possible without port forwarding
- Lower network latency and overhead compared to NAT
- Seamless integration with existing network services (DNS, DHCP, Active Directory)
- Ideal for production server deployments
Disadvantages:
- Requires network administrator permissions on many systems
- IP address exhaustion if too many bridged VMs are deployed
- Potential security exposure if VMs are compromised (direct access to physical network)
- May not work reliably on wireless connections due to MAC address filtering
- Requires careful network planning to avoid address conflicts
Practical Implementation Examples
Linux KVM/QEMU: A bridge is created using brctl addbr br0, then the physical adapter is added with brctl addif br0 eth0. The VM's vNIC is then attached to br0.
VMware ESXi: Virtual switches are configured in the vSphere client, with physical adapters assigned to the switch and VMs connected to port groups configured for bridged connectivity.
Hyper-V: A virtual switch of type "External" is created and bound to a physical adapter, allowing connected VMs to bridge directly to the physical network.
VirtualBox: In the VM network settings, selecting "Bridged Adapter" and specifying the host's physical adapter (eth0, en0, etc.) automatically bridges the VM to that interface.
Best Practices
Security: Use network segmentation (VLANs) to isolate bridged VMs from sensitive network segments. Implement firewall rules at the network edge to control which machines can connect to bridged VMs.
IP Management: Maintain detailed records of IP addresses assigned to bridged VMs to prevent DHCP conflicts. Consider using static IP assignments for critical VMs.
Monitoring: Monitor bridged VM network traffic separately to identify bandwidth hogs or suspicious network behavior.
Redundancy: On systems with multiple physical adapters, consider bonding or multi-NIC configurations to provide failover capability for bridged VMs.
Documentation: Clearly document which VMs use bridged networking and why, as this affects network planning and troubleshooting efforts.
Troubleshooting Common Issues
No Network Connectivity: Verify the bridge is properly configured, the physical adapter is active, and DHCP is available on the network segment.
IP Address Not Assigned: Check DHCP server logs, ensure the VM's MAC address is recognized, and verify there are available addresses in the DHCP pool.
MAC Address Conflicts: Ensure the VM's MAC address is unique on the network and doesn't conflict with the host's physical adapter MAC.
Intermittent Connectivity: On wireless networks, verify that bridging is supported by the wireless driver; many wireless drivers don't support bridging effectively.