A practical overview of networking concepts in Proxmox VE, covering VLANs, Linux bridges, and network bonding. Focuses on native Linux implementations (not Open vSwitch or VXLAN). Key considerations include traffic planning for the Proxmox management interface, storage networks (NFS/SMB/iSCSI), VM connectivity, VLAN trunk access for VMs, and high-availability bonding strategies. Demonstrates bonding between identical and mixed-speed interfaces.
Questions this post answers
What networking questions should I answer before designing my Proxmox VE network topology?
Before designing a Proxmox VE network, consider: how much traffic hits Proxmox itself (web UI, API, SPICE sessions); how much storage traffic flows over NFS, SMB, or iSCSI and whether it needs a dedicated physical or VLAN-separated network; which VLANs your VMs need; whether any VMs require trunk port access; and whether you need bonded failover for high availability. Proxmox homelab builders share topology decisions and trade-offs like these on daily.dev.