Add to GUI DHCP option for configue Failover peer NAME
-
HA for pfsense documents describe the situation only when the second pfsense node coincides with the main one.
My situation is when HA uses CARP not to fully synchronize the configuration between nodes.
Used for different pfsense server settings, but one DHCP task per segment. Other tasks on each server are different.
To balance failures for a DHCP server in pfsence, the dhcpd.conf file uses an automatically generated failover peer name, such as: 'dhcp_opt5' for a network interface such as WiFi-GUEST.
If you do not use the full HA-cluster mode for pfsense nodes, then the second pfsense may have a different order or number of network interfaces.
Then in the second pfsense server DHCP will have another automatically generated failover peer name, for example: 'dhcp_opt1' for the same logical network interface as WiFi -GUEST.
And DHCP replication will be rejected between the two peer.Feb 11 14:52:19 gw1 dhcpd: Failover CONNECT from dhcp_opt1: unknown failover relationship name Feb 11 15:52:19 gw1 dhcpd: failover: disconnect: unknown failover relationship name
To resolve a situation where incomplete synchronization of HA pfsence servers is used, you can add a failover peer name field to the DHCP server GUI to change the default generated name based on the local interface number, to another, for example: dhcp_wifiguest.
I tested using a manually configured dhcpd.conf file with its own "failover peer name" without the pfsense GUI, as a result DHCP replication works fine between CARP-based servers with skew 0 and 100.