Proxmox VE networking: configure bridges and VLANs for your VMs and containers.Getting your virtual machines and containers onto the right networks is essential for security, segmentation, and matching your physical network layout. Proxmox VE uses Linux bridges and optional VLAN and Open vSwitch support so you can connect VMs to your LAN, isolate traffic, or align with existing VLANs. This guide covers Proxmox VE networking from bridge basics to VLAN-aware bridges and assigning VLAN tags to VMs and LXC containers. For an overview of the platform, see our Proxmox VE Guide; for protecting your hosts and VMs, use our Proxmox backup guide and Proxmox monitoring guide.
Related video
How Proxmox VE Networking Works
By default, Proxmox VE creates a single Linux bridge (usually vmbr0) tied to one physical network interface. All VMs and containers that use that bridge share the same layer-2 segment—like plugging into one switch. The bridge acts as a virtual switch: traffic from VMs goes through the bridge to the physical NIC and out to your network. You manage networking in the Proxmox web UI under Node → System → Network, or by editing /etc/network/interfaces on the host.
Adding VLANs lets you segment that traffic: you make the bridge VLAN-aware, tag traffic from the physical switch, and assign VLAN tags to individual VMs or containers so they sit on the correct VLAN without needing multiple physical NICs.
Linux Bridge Basics
In Node → System → Network you’ll see your bridges (e.g. vmbr0) and physical interfaces. Each bridge has a name, a list of ports (physical NICs or bonds), and options such as VLAN awareness. To give VMs connectivity, at least one bridge must be attached to a physical interface that’s connected to your network.
You can add more bridges (e.g. vmbr1) and bind them to other NICs for separate networks, or use a single VLAN-aware bridge and differentiate traffic with VLAN tags. After changing the configuration, use Apply Configuration in the GUI (Proxmox VE 7+ uses ifupdown2, so changes can apply without a reboot) or run ifreload -a after manual edits.
VLAN-Aware Bridge Setup
To use VLANs with a single bridge:
- Make the bridge VLAN-aware: In the bridge’s options in the Proxmox GUI, enable VLAN-aware (or equivalent). The bridge will then pass through VLAN-tagged frames instead of stripping tags.
- Configure your physical switch: Set the port connected to the Proxmox host as a trunk (tagged) port and allow the VLANs you need (e.g. 10, 20, 50).
- Assign VLAN tags to VMs/containers: When adding or editing a network device for a VM or LXC, set the VLAN tag (e.g. 50) so that guest traffic is tagged with that VLAN ID.
VLAN interface names on the host often follow the form device.vlan-number (e.g. eno1.50). In the GUI you typically set the tag on the VM/container’s network device rather than creating host-side VLAN interfaces for each ID.
Assigning VLANs to VMs and Containers
VMs: Edit the VM → Hardware → select the network device → set VLAN Tag to the desired ID (e.g. 50). The VM’s guest OS will see untagged traffic on its virtual NIC; Proxmox tags and untags at the bridge.
LXC containers: Edit the container → Network → set the VLAN tag on the container’s network device. Same idea: traffic to/from the container is tagged with that VLAN at the bridge.
For multiple VLANs on one VM or container, add multiple network devices and assign a different VLAN tag to each.
Open vSwitch (Optional)
For more advanced setups—LACP bonds, VXLANs, or complex topologies—Proxmox supports Open vSwitch (OVS). You install openvswitch-switch and use ifupdown2; then in the Proxmox GUI you can create an OVS bridge and attach physical interfaces or bonds. OVS configuration is more involved; back up /etc/network/interfaces and follow the Proxmox network documentation or community guides for OVS and LACP.
Troubleshooting and Tips
VM or container has no connectivity: Confirm the bridge is up and attached to the correct physical NIC; if using VLANs, check that the VLAN tag on the VM/container matches the switch and that the bridge is VLAN-aware.
Changes not applied: Use the GUI’s Apply Configuration or run ifreload -a after editing /etc/network/interfaces. Avoid rebooting if you can; ifupdown2 applies changes live.
Backup before big changes: Copy /etc/network/interfaces to a safe place before adding OVS or reworking bridges so you can revert if needed.
FAQ
What is a Proxmox Linux bridge?
A Linux bridge is a virtual switch that connects VMs and containers to a physical network interface. Proxmox uses bridges (e.g. vmbr0) so that guest traffic is forwarded to and from the NIC.
How do I add a VLAN to a Proxmox VM?
Edit the VM → Hardware → select the network device → set the VLAN Tag to the desired VLAN ID. The bridge must be VLAN-aware, and the physical switch must send tagged traffic for that VLAN to the host.
Can I use Proxmox without VLANs?
Yes. The default single bridge is enough for a flat network. VLANs are optional for segmenting or matching existing VLANs.
Does Proxmox support Open vSwitch?
Yes. Install the openvswitch-switch package and create an OVS bridge in the Proxmox GUI. Use it when you need LACP, VXLAN, or other advanced features.
Where is Proxmox network config stored?
In /etc/network/interfaces. The web UI reads and writes this file; use Apply Configuration to apply changes.
How do I add a VLAN to an LXC container?
Edit the container → Network → select the container’s network device and set the VLAN Tag to the desired ID. The bridge must be VLAN-aware, and your physical switch must trunk that VLAN to the Proxmox host.
What is vmbr0?
vmbr0 is the default Linux bridge Proxmox VE creates, usually bound to your first physical NIC. All VMs and containers that use it share the same layer-2 segment unless you enable VLAN awareness and assign VLAN tags.
Do I need to reboot Proxmox after changing network settings?
No. Proxmox VE 7+ uses ifupdown2, so you can apply network changes with Apply Configuration in the GUI or ifreload -a from the shell without rebooting.
Can I use multiple bridges on one Proxmox host?
Yes. Add more bridges (e.g. vmbr1, vmbr2) in Node → System → Network and attach each to a physical NIC or bond. Use them to separate VM traffic, management, or storage onto different networks.
Why does my VM have no network after setting a VLAN tag?
Check that the bridge is VLAN-aware, the VLAN tag on the VM matches a VLAN allowed on your switch’s trunk port, and the switch port to the host is configured as a trunk (tagged) for that VLAN.
Conclusion
Proxmox VE networking relies on Linux bridges for VM and container connectivity; enabling VLAN awareness and assigning VLAN tags lets you segment traffic without extra NICs. For most homelabs and small clusters, a single VLAN-aware bridge and tagged VMs are enough. Use Open vSwitch when you need bonds or overlay networks. After configuring networking, keep your hosts and VMs protected with backups and monitoring—see our Proxmox backup and monitoring guides for setup.
