Failover Network

The Network tab of a mission describes the networks that your guests use today. Only a failover uses this plan; a restore test always starts the guests in an isolated network.

A restored guest keeps its IP settings, because we do not change your guest operating system. So the failover rebuilds your networks around the guests instead. Every guest keeps its address and its gateway, our router answers on the gateway address of each subnet, and you reach everything through WireGuard.

Subnets

The mission fills the network plan by itself. It reads the network settings of containers and of cloud-init VMs from the backups, and the addresses that the guests used in the last restore test. Click Detect from backups to read them again, for example after you add guests or after a test.

Each subnet has a name, a network in CIDR form (for example 192.168.10.0/24) and the gateway that your guests use (for example 192.168.10.1). The line below the name shows the bridge and VLAN of your Proxmox VE that the subnet came from. When guests asked for a different gateway in the last restore test, the subnet offers that address with a Use it button. Every network interface of a guest must belong to a subnet, and the check list names those that do not.

Internet access and public guests

With Internet access for all guests turned on, the guests reach the internet through one shared public address.

To reach a guest from the internet, mark it as public in its settings and list the ports to publish, for example 443/tcp. The guest then gets its own public address from our pool. Only the published ports reach it from outside, and it also sends its own outbound traffic from that address. A restore test checks that the published TCP ports open, and the guest settings show the result.