If you’ve been following along, in our last video we got Proxmox up and running and explored the different components to help us get familiar with the GUI. Today, we’re going to go a little deeper into the world of Proxmox networking. This time, we’re rolling up our sleeves and diving into how to set up bridges, bonds, VLANs, and even touch on SDN.
How Proxmox Handles Networking
Before we start setting things up, it’s important we understand how Proxmox handles networking overall. Proxmox divides networking into two main layers — and it’s super helpful to think about it this way:
Node-Level Networking
At this layer, each Proxmox server (or node) manages its own physical and virtual network interfaces. This is where we configure things like Linux bridges, network bonds, and virtual interfaces (VIFs) — all the essentials to connect our VMs to the outside world.
Data Center-Level Networking (SDN)
On the other side, we have Software Defined Networking (SDN). It’s a newer feature that lets us design network setups that span across multiple nodes. We’re talking about zones, virtual networks (Vnets), and controllers — powerful stuff that comes in handy once we’re managing more than one node. We’ll get to SDN a bit later, but let’s start at the ground level: node networking.
Setting Up Linux Bridges
Think of a Linux bridge like a virtual switch sitting inside our Proxmox server. It allows our VMs to connect to the external network through the physical network ports (NICs) on the machine.
When we set up Proxmox for the first time, it automatically creates a default bridge called vmbr0. This bridge hooks up to the main NIC on the server, so any VM connected to vmbr0 joins the same LAN as our physical machines — kind of like plugging a laptop straight into the network.
Let’s Create a New Bridge
- Here’s what we’ll do:
- Click on our node.
- Head over to Network.
- We’ll see our physical NICs — they’re usually named something like eno1 or enp3s0.
- Click Create > Linux Bridge.
- Give it a name (Proxmox will suggest vmbr1 if vmbr0 already exists).
- Tie it to an unused NIC.
- (Optional) Fill in IP settings if we want this bridge to have an IP.
Once we hit Apply Configuration, we’ll have a fresh new bridge ready to go!
Network Bonding: Better Redundancy and Speed
Now, let’s step it up a notch and talk about bonding. Network bonding lets us combine two (or more) physical NICs into one logical interface. The benefits? Redundancy in case one NIC fails and potentially more bandwidth by load-balancing the traffic.
Proxmox supports a few bonding modes:
- Balance-rr: Load balance traffic across all interfaces.
- Active-backup: One active NIC with another on standby.
- LACP (802.3ad): Dynamic link aggregation for high availability.
How We Set Up a Bond
Stay in Network.
- Click Create > Linux Bond.
- Pick two available NICs.
- Choose a bond mode — balance-rr is a solid choice for home labs.
- Save and Apply Configuration.
Heads up: We can’t attach a VM directly to a bond. Instead, we’ll need to create a bridge, attach the bond to the bridge, and then connect our VMs to that bridge. A couple of extra steps, but totally worth it for the extra reliability.
VLANs: Segmentation Without Extra Hardware
VLANs (Virtual LANs) let us split up a single physical network into multiple virtual networks — keeping traffic separated without the need for extra switches. Perfect for things like isolating test environments, IoT devices, or guest networks.
Setting Up VLANs in Proxmox
Here’s the catch: VLANs need to be set up on our network equipment (firewall and switches) before Proxmox can tag traffic. I’m working on a full end-to-end VLAN setup guide, but for now, here’s the short version inside Proxmox:
- Enable VLAN aware on our bridge.
- On the VM’s Network Device, set a VLAN Tag (like 10 or 20).
- Attach it to the VLAN-aware bridge.
Now, whenever that VM sends traffic, it will be tagged properly and routed based on our VLAN setup.
VLANs with SDN (The Cleaner Way)
If we’re using SDN, VLANs can be even cleaner:
- Create a VLAN Zone in SDN.
- Create a vNet in that zone.
- Assign the VLAN tag at the vNet level.
This way, any VM attached to that vNet gets the correct VLAN tag automatically — no need to manually set tags for each VM. It’s a nice touch, especially if we’re managing a bunch of VMs.
A Quick Note About Linux VLAN Interfaces
Sometimes, we might want the Proxmox host itself to sit on a VLAN — for management traffic or storage, for example. In that case, we’d create a Linux VLAN interface on the host. For smaller labs, it’s usually not necessary, but it’s good to have in our toolkit for more advanced setups.
A Look at SDN: Software Defined Networking
Alright, now let’s take a peek at SDN — one of Proxmox’s more powerful features. SDN lets us manage networking centrally across multiple nodes instead of configuring each node separately.
Here’s what SDN introduces:
- Zones: Containers for our SDN network configurations — they define the network’s behavior (local or multi-node).
- vNets: Virtual networks (like virtual switches) where our VMs connect.
- IPAM: IP address management — keeping track of which IPs are assigned where.
Proxmox doesn’t come with DHCP for SDN networks by default. We’ll need to install dnsmasq if we want automatic IP assignment.
Setting Up SDN Together
- Head to Datacenter > SDN.
- Create a Zone (Simple Zone works for most setups).
- Create a vNet inside that Zone.
- Create a Subnet inside the vNet — define our IP range and default gateway.
- Enable DHCP if we want automatic IP assignments.
Once we apply all the changes, we can start attaching our VMs to the vNet. It’s super powerful, especially when we want to keep things clean and contained — or if we’re planning to scale out.
Final Thoughts
And there we have it! We’ve walked through Proxmox networking step-by-step:
- Linux Bridges for connecting VMs to the LAN
- Network Bonding for redundancy and performance
- VLAN tagging for segmentation
- Dive into SDN for central management
Hopefully, this makes networking in Proxmox feel a lot less overwhelming. Once we get hands-on a few times, it really starts to click.
If you found this helpful, feel free to leave a comment or share your setup — I love hearing how others are building out their labs. Until next time, stay geeking. Peace
