Network, Bridge & IP on Proxmox
Configure vmbr0, assign IPv4 to your VM, DNS, MTU and best network practices on Proxmox hypervisor.
Ready to start your service? Check offers and order online.
View offers and orderNetwork, Bridge & IP on Proxmox
The Proxmox network is based on Linux bridges (vmbr0) that connect your VMs to the public IPv4 or internal network. This guide explains bridge configuration, IP attribution to VM, DNS, MTU and connectivity issues.
Typical architecture
On your VDS Anthony IT Solutions, a physical interface is set to vmbr0. Each VM receives a virtual MAC; the IPv4 can be routed directly or via DHCP according to your offer.
View the network configuration
- Proxmox → Node → Network
- Check
vmbr0: bridge ports, IP address node, gateway - Customer space panel → Network section : IPv4, DNS, MTU
Configure a VM
- VirtIO interface connected to vmbr0 (standard)
- IP static in the OS guest: IP, mask, gateway, DNS
- IP additional: command via IP additional, configure alias or second interface
Do not change the Proxmox node IP without a support statement, risk of total cut-off.
DNS & MTU
- Recommended DNS: those displayed in the network panel (often solvers datacenter)
- default MTU 1500; 1450 if tunnel overlay (WireGuard, some VLAN)
- Reverse DNS (PTR): request via customer space for main IP
Firewall & insulation
Proxmox VE Firewall can filter at datacenter, node or VM level, see proxmoxfirewall. To isolate VMs from each other, use VLAN or private Linux networks (internal vmbr1).
Troubleshooting
- VM without Internet, wrong gateway, duplicate IP, firewall guest
- Ping node OK, not VM, bridge down, wrong VM interface
- High latency, check MTU, NCI overload