Can each Proxmox VM have its own public IPv4 address?

Yes. A routed address can be assigned as a /32 on the virtual machine while the Proxmox host holds a route for that /32 across a private bridge. The host forwards the address to the VM and sends replies through the tunnel. Each VM then has its own reachable IPv4 address without NAT or port sharing.

Do Proxmox VMs need a public bridge for public IPv4?

No. A routed design uses an internal bridge with no physical port. The Proxmox host routes the public /32 address through that bridge to the VM. This is useful when a tunnel provider delivers individual public addresses to the host, or when the upstream does not allow multiple guest MAC addresses on its physical network.

Why does a Proxmox VM receive traffic but cannot reply through its public IPv4?

The usual cause is a missing source-specific route on the Proxmox host. The host needs a policy rule that selects the tunnel routing table for traffic sourced from the routed public address or prefix. Check the return route with ip route get 1.1.1.1 from the public IPv4 address.

Can routed IPv4 addresses move to another Proxmox server?

A provider-routed address can remain unchanged when its tunnel endpoint moves, provided the provider supports repointing the tunnel. The new Proxmox host still needs the address route, private bridge, guest configuration and return-path policy before traffic is switched.

How to Add Public IPv4 Addresses to Proxmox VMs

A Proxmox host can run several VPS instances while each one keeps a distinct public IPv4 address. The clean route is a tunnel that carries the public addresses to the host, an internal Linux bridge, and one route per VM. Customers receive ordinary reachability on SSH, HTTPS, game ports, VPN ports and any service they install.

This guide uses a routed design. It avoids NAT, port allocations and dependence on guest MAC addresses being accepted by the datacenter network. The commands illustrate one Debian-based Proxmox host and one guest. Addresses from RFC 5737 are used throughout, so none of them exist on the public Internet.

Three documentation IPv4 addresses routed from Taipan Transit through one tunnel to separate Proxmox virtual machines. — One tunnel can deliver several routed addresses. The Proxmox host forwards each public /32 to the VM assigned to it.

Choose the routed model before editing Proxmox

There are two common ways to put public addresses on Proxmox guests. A bridged arrangement puts the guest directly on an upstream Ethernet segment. The provider sees each guest MAC address. It is simple when the provider explicitly permits it.

A routed arrangement gives the Proxmox host a route for every guest address. Guests attach to a private bridge, and the host forwards their traffic. This is the suitable model for individually routed IPv4 addresses delivered through a GRE, IPsec or WireGuard tunnel. It also works when a dedicated-server provider allows only one MAC address on the physical port.

Scope

This article covers routed IPv4 addresses. Do not combine these commands with an existing public bridge until the provider's network model is understood. A conflicting gateway or route can disconnect the Proxmox management interface.

Virtualization

Routed IPv4

Write down the address map

Keep the tunnel address, public address, private bridge address and VM identifier in one place. The public IPv4 is a host route, written as /32. The private addresses exist only between the Proxmox host and its guests.

Item	Example	Purpose
Tunnel	`wg0`	Delivers addresses to the Proxmox host.
Private bridge	`vmbr1`	Connects the host and routed guests. It has no physical port.
Host bridge IP	`10.42.0.1/24`	Default gateway inside the private guest network.
VM 101	`10.42.0.10/24`	Private next hop for the guest.
VM 101 public IP	`203.0.113.42/32`	Public address routed through the tunnel.

How to add public IPv4 addresses to Proxmox VMs

Choose the routed model before editing Proxmox

Write down the address map