Skip to content
Amol Dighe
Go back

Proxmox Networking

Edit page
Proxmox Networking
Image generated with Google Gemini

In Proxmox VE, networking is all about connecting virtual machines (VMs) and Linux Containers (LXCs) to each other and to the outside world. Because Proxmox sits directly on the physical server, it uses standard Linux networking concepts abstracted into a web interface.

We will look at seven core networking components operate specifically within the context of a Proxmox node.

               [ Public Internet ]
                       │
               [ Physical Router / Internet Gateway ]
                       │
         ┌─────────────▼────────────────────────────────┐
         │ Proxmox Physical Host                        │
         │   Physical NIC (enp3s0)                      │
         │         │                                    │
         │   ┌─────▼──────────────────────────────┐     │
         │   │ Linux Bridge (vmbr0)               │     │
         │   └─────┬──────────────┬──────────────┬┘     │
         │         │              │              │      │
         │   ┌─────▼─────┐  ┌─────▼─────┐  ┌─────▼──┐   │
         │   │ tap101i0  │  │ tap102i0  │  │ vnet1  │   │ (Virtual Interfaces)
         │   └─────┬─────┘  └─────┬─────┘  └─────┬──┘   │
         │         │              │              │      │
         │     [ VLAN 10 ]    [ VLAN 20 ]    [ VXLAN ]  │ (Traffic Isolation)
         │         │              │              │      │
         │     ┌───▼───┐       ┌──▼────┐       ┌─▼────┐ │
         │     │ VM 101│       │ VM 102│       │VM 103│ │ (Guest Instances)
         │     └───────┘       └───────┘       └──────┘ │
         └──────────────────────────────────────────────┘

Bridge Interface (vmbr)

A Bridge Interface (typically named vmbr0, vmbr1, etc.) acts as a virtual network switch running inside your Proxmox host.

VLAN (Virtual Local Area Network)

A VLAN splits a single physical bridge or switch into multiple, isolated logical networks using numerical tags (VLAN IDs from 1 to 4094).

VXLAN (Virtual Extensible LAN)

A VXLAN is an advanced overlay protocol that encapsulates layer 2 ethernet frames inside layer 4 UDP packets. It allows you to stretch a virtual network across completely different physical networks or distinct Proxmox hosts.

Router

A Router directs traffic between different IP networks or subnets (e.g., sending data from your 192.168.10.x VLAN to your 192.168.20.x VLAN).

Internet Gateway

An Internet Gateway (or Default Gateway) is a specific type of router configuration that acts as the exit point for any traffic leaving the local network destined for the public internet.

Virtual Interface (vnet / tap / fwbr)

A Virtual Interface is the software-defined endpoint created dynamically by Proxmox to link individual VMs to the host’s networking architecture.

Subnet

A subnet is a logical subdivision of an IP network (written in CIDR notation like 192.168.10.0/24) that defines which IP addresses belong together in the same local broadcast domain. While VLANs and bridges act as the physical or virtual “wires” and “switches,” subnets are the Layer 3 IP addressing rules that let your Proxmox hosts, VMs, and containers communicate and route traffic properly.

Where Subnets Are Defined in Proxmox

You encounter and configure subnets in three main places inside a Proxmox deployment:

Common Subnet Patterns in Proxmox Setups

Setup PatternExample SubnetsHow It Works in Proxmox
Flat Network (Default)192.168.1.0/24 (Shared by everything)Your Proxmox host (192.168.1.10) and all VMs (192.168.1.100+) sit on vmbr0 and pull IPs from your existing home or office router.
VLAN-Segmented SubnetsManagement: 10.0.1.0/24 (VLAN 1)
Servers: 10.0.10.0/24 (VLAN 10)
DMZ: 10.0.20.0/24 (VLAN 20)
You use a VLAN-aware vmbr0. Each VLAN gets its own dedicated IP subnet, and a firewall or router (physical or virtual like OPNsense) controls traffic moving between them.
NAT / Private Internal Subnet10.10.50.0/24 (Host-only bridge vmbr1)Used when you only have one public IP (common on rented dedicated servers). VMs sit on a private subnet (10.10.50.x) and use the Proxmox host as a NAT gateway to reach the internet.
Cluster & Storage SubnetsCorosync: 172.16.1.0/24
Ceph/Storage: 172.16.2.0/24
In multi-node clusters, best practice isolates cluster heartbeat traffic and heavy storage replication onto separate physical NICs with dedicated non-routed subnets.

Key Subnet Rules to Remember


Edit page
Share this post:

Previous Post
Back-of-the-Envelope Framework Simplified
Next Post
NVIDIA Computex 2026 Keynote Highlights