Manually configuring VLANs and bridges across multiple Proxmox nodes gets complicated fast, especially as your cluster grows and you want consistent network isolation applied uniformly everywhere. Proxmox SDN (Software-Defined Networking) simplifies this considerably, letting you define virtual networks once at the cluster level and have them consistently applied across every node automatically.

What Is Proxmox SDN?

Proxmox SDN is a built-in feature allowing you to define virtual networks — zones, VNets, and subnets — through the Proxmox web interface, abstracting away the need to manually configure matching VLAN tags or bridge interfaces on every individual cluster node separately. Once defined, VMs across your entire cluster can use these virtual networks consistently, regardless of which physical node they’re actually running on.

Why SDN Matters Beyond Basic VLANs

Standard VLAN configuration () works well for a single node or a small, static cluster, but requires manually replicating consistent VLAN configuration across every node individually. SDN centralizes this: define a network once at the Datacenter level, and Proxmox handles ensuring it’s consistently available wherever a VM using that network happens to run — including automatically following a VM during live migration between nodes.

Understanding SDN’s Core Concepts

• Zones – the top-level container defining how a particular networking technology behaves (Simple, VLAN, QinQ, VXLAN, or EVPN, each suited to different scale and isolation needs)
• VNets – virtual networks within a zone, roughly analogous to individual VLANs, that VMs actually connect to
• Subnets – IP addressing definitions within a VNet, optionally including DHCP configuration for that virtual network

Choosing a Zone Type

• Simple – the most basic option, essentially an isolated bridge without VLAN tagging, suitable for simple, single-node isolation needs
• VLAN – maps directly onto traditional 802.1Q VLAN tagging , requiring compatible switch-side configuration
• VXLAN – enables Layer 2 networks that span across nodes even without direct switch-level VLAN support, useful for more flexible network topologies
• EVPN – a more advanced, BGP-based option suited to larger, more complex multi-node deployments needing dynamic routing between virtual networks

For most homelab clusters, VLAN or Simple zones cover the practical need without the added complexity of VXLAN or EVPN, which are more relevant for larger, more elaborate deployments.

Setting Up a VLAN Zone

1. Go to Datacenter → SDN → Zones.
2. Click Create → VLAN.
3. Name the zone and specify the bridge interface it should use on each node (typically your existing vmbr0).
4. Apply the configuration.

Creating a VNet

1. Go to Datacenter → SDN → VNets.
2. Click Create.
3. Name the VNet and select the zone you just created.
4. Specify the VLAN tag this VNet corresponds to.

Defining a Subnet

1. Within the VNet’s configuration, add a Subnet.
2. Define the IP range and gateway for this virtual network.
3. Optionally enable Proxmox’s built-in DHCP server for this subnet, letting VMs connected to it receive IP addresses automatically without needing an external DHCP server.

Applying SDN Configuration

After defining zones, VNets, and subnets, apply the configuration across your cluster:

1. Go to Datacenter → SDN.
2. Click Apply.

This pushes the network configuration out to every node in your cluster, ensuring consistency without needing to manually touch each node’s individual network configuration files.

Assigning a VM to an SDN VNet

When configuring a VM’s network device, select your newly created VNet from the bridge dropdown instead of a traditional physical bridge, connecting that VM to the isolated virtual network you’ve defined.

SDN and Live Migration

Because SDN definitions apply cluster-wide rather than per-node, a VM connected to an SDN VNet retains full network connectivity automatically when live-migrated () between nodes, without any manual network reconfiguration needed on the destination node.

When Basic VLANs Are Still the Right Choice

For a small, single-node homelab, or one that isn’t expected to grow into a multi-node cluster, manually configured VLANs remain simpler to understand and troubleshoot than the additional abstraction layer SDN introduces. SDN’s real value emerges specifically as cluster size and network complexity grow.

Final Thoughts

Proxmox SDN brings genuinely enterprise-grade network management to a growing Proxmox cluster, centralizing virtual network definitions that would otherwise require careful manual replication across every node. For homelab users running multi-node clusters with meaningful network segmentation needs, SDN significantly reduces the ongoing maintenance burden compared to manually keeping VLAN configuration consistent everywhere.

Related Posts

• How to Set Up Automatic Proxmox Backups
• How to Set Up GPU Passthrough in Proxmox
• How to Migrate a Physical Server to Proxmox (P2V Migration)