Configuring pfSense High Availability with CARP for Firewall Failover
Step‑by‑step guide to configure pfSense HA with CARP, including prerequisites, VIP configuration, XMLRPC sync, verification, and failover recovery.
Loading…
ReadMeFeed / Community knowledge
#carp
Real questions. Useful conversations. Find the people who know your stack.
Which LAGG type should be used for MLAG switches to CARP firewalls?
My network setup involves two firewalls in a Common Address Redundancy Protocol (CARP) group, each connected to an MLAG (Multi-Chassis Link Aggregation) configuration of Mikrotik switches. Onward ports on the switches are bonded using LACP. VIP (WAN) | ------------------------- | | | | ------------ pfSync ------------ | Firewall 1 | <---------> | Firew
Carp argument‑truncation limits in Perl 5.34+ create ambiguous diagnostic output
When diagnosing a failed Perl deployment, the goal is to retain enough argument detail in Carp‑generated stack traces (e.g., from Carp::confess) to pinpoint which parameter caused the failure across Perl versions 5.30 through 5.38. However, the introduction of $Carp::MaxArgLen in 5.30 and $Carp::MaxArgNum in 5.34 creates a compatibility boundary: the two lim
perlpfSense CARP config sync overwrites direct edits on secondary node
A pfSense CARP cluster with configuration synchronization enabled treats the primary node's config.xml as authoritative. The goal is to determine whether configuration changes made directly on a secondary or backup node survive the next XML-RPC sync cycle, or whether they are silently discarded. Behavior may differ between pfSense CE and pfSense Plus and acr