The need: separate compute hosts from WAN exits

Proxmox hosts run workloads while external nodes provide access to WAN networks. The WireGuard fabric delivers private, encrypted IP connectivity between participants. External nodes act as network gateways here; participating in the fabric does not make them Proxmox cluster members or extend its quorum.

The architecture: connect the fabric to external gateways

Each participant has a WireGuard identity, tunnel addressing and the parameters needed to reach its peers. External nodes connect this private network to their WAN interfaces and perform IP forwarding. Their configuration must remain consistent with the fabric: public keys, endpoints, allowed prefixes and routes. Managing a node outside the cluster also requires tracking its configuration and update lifecycle.

Route traffic and provide a return path

Routing determines which prefixes or default routes use the gateways. WireGuard AllowedIPs participate in peer selection and source address validation, but do not constitute a complete routing policy by themselves. Return routes must reach internal networks; address translation may be necessary where WAN access requires it. Forwarding and filtering rules distinguish application traffic from host and gateway administration.

Control MTU, endpoints and filtering

WireGuard encapsulation reduces the size available for carried packets. MTU is sized for the actual path, accounting for any additional encapsulation, and then checked with representative traffic. Endpoints must remain reachable independently of the routes they carry to avoid a circular dependency. When a peer sits behind NAT, a keepalive may be useful depending on which side initiates traffic and how long mappings remain active.

Monitor WAN exits and exercise gateway failure

A recent WireGuard handshake does not prove that the WAN behind the gateway is working. Monitoring combines peer state, counters, routes and probes to external destinations. Multiple gateways alone do not guarantee automatic failover: route selection and withdrawal must be defined and tested. Exercises cover tunnel loss, WAN access loss and path recovery; session continuity depends in particular on routing and NAT or firewall state.

Key considerations

  • Encrypted WireGuard fabric
  • External nodes as WAN gateways
  • Explicit routes and return paths
  • Controlled MTU and filtering
  • Monitoring from tunnel to WAN
Discuss your architecture ↗