Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Add to GUI DHCP option for configue Failover peer NAME

    Scheduled Pinned Locked Moved DHCP and DNS
    carpdhcpfailoverguihigh availabili
    1 Posts 1 Posters 623 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • lexxaiL
      lexxai
      last edited by lexxai

      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
      

      dhcp_failover_name.jpg

      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.

      Знімок екрану з 2021-02-12 00-39-10ed.png

      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.

      –
      We have what we have. Everything that happens - for the better.

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.