How jose20035/pfsense-alta-disponivilidad works
Project type and purpose
• This is an infrastructure-as-code/virtualization project that builds a high-availability firewall cluster using pfSense under libvirt/KVM.
• Two pfSense VMs (master & slave) provide HA and firewall/NAT services for two Debian test guests (web & db).
• Four virtual networks are defined in XML (default/NAT, exter, intra, net-pfsense).
File structure
• Top level
• README.md – project description and steps
• imagenes/… – screenshots of configuration steps
• xml/
– maquinas/ (web.xml, db.xml): VM definitions for Debian guests
– redes/ (default is implicit, plus exter.xml, intra.xml, net-pfsense.xml): libvirt network definitions
• There are no application source code folders; all “source” is libvirt XML descriptors and docs.
README for additional insights
• Four libvirt networks with distinct roles (Internet NAT, external LAN, internal LAN, HA sync).
• Two Debian VMs (web & db) built with virt-builder, attached to exter & intra.
• Two pfSense VMs installed via virt-install, each with four NICs, implementing WAN, DMZ, LAN, and sync networks.
• pfSense configuration: interface assignment, firewall rules, DHCP, CARP VIPs, HA sync via pfsync.
• Use clear labels: VM names, network names, IP ranges (/24).
• From web/db through pfSense to default (Internet)
• Between pfSense nodes on net-pfsense (two-way)
• Clouds for networks (blue=WAN, orange=DMZ, green=LAN, purple=HA sync)
• CARP VIPs next to pfSense link and VIP IPs on WAN/LAN.