The need: distribute networks while separating workloads
Workloads spread across several hosts need access to their virtual network while environments remain separated. Proxmox SDN describes zones, VNets and subnets; the design maps these objects to VXLAN segments and routing domains. The intended isolation covers both communication between machines and their access to external networks.
The architecture: IP transport and VXLAN segments
VTEPs terminate VXLAN tunnels on participating hosts. A VNI identifies a layer 2 segment, while the IP transport network provides reachability between VTEPs. Addressing, routes and MTU must accommodate encapsulated packets. VXLAN carries frames but does not encrypt them: protecting transport requires a separate mechanism when the underlying network demands it.
BGP EVPN, bgpd and Zebra: complementary roles
BGP EVPN distributes reachability information rather than relying solely on flooding-based learning. Within FRR, bgpd exchanges EVPN routes, including MAC/IP associations; prefix advertisements depend on the routing model. Zebra interfaces with Linux kernel interfaces, routing tables and forwarding entries. Diagnosis therefore compares BGP advertisements with their actual installation in the system, rather than treating an established session as proof of end-to-end connectivity.
Separate routing domains with VRFs
VRFs maintain separate routing tables. Within Proxmox SDN, EVPN zones and VNets are scoped to match this separation: creating multiple VNets does not necessarily create multiple routing domains. EVPN import and export settings must preserve the intended boundaries. Gateways and external exits belong to the appropriate domain; communication between domains requires an explicit path and suitable filtering. A VRF does not replace a firewall.
Validate mobility, external access and convergence
Acceptance checks cover permitted and prohibited communication, forward and return paths, and moving a machine between hosts. Loss of a BGP session, VTEP or gateway reveals route withdrawal and convergence behaviour for the chosen topology. Operations monitor sessions, EVPN routes, VRF tables and MAC entries. Changes are managed through Proxmox SDN configuration to avoid local FRR adjustments being overwritten by a later configuration apply.
Key considerations
- Proxmox SDN and EVPN zones
- VXLAN, VTEPs and VNIs
- BGP EVPN with FRR
- VRF-separated routing domains
- Mobility and convergence checks