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

    High availability DHCP issues

    Scheduled Pinned Locked Moved DHCP and DNS
    1 Posts 1 Posters 635 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.
    • B
      blanham
      last edited by

      Hi,

      I was hoping someone may have a clue as to how to explain the dhcp fail-over issue i'm having?

      Some background:

      I have two pfsense 2.2.6-amd64 machines configured with High availability/CARP.
      Due to Bug https://redmine.pfsense.org/issues/4061 causing havoc in our network I had disabled the dhcp fail-over and was serving exclusively from the primary cluster member.
      However I have reconsidered that approach after some issues caused by this in the office.

      So to my issue at hand.

      I have 5 VLANs defined (all bound to a lagg parent interface). Systematically I have re-enabled the dhcp fail-over configuration for each interface. All bar one interface have come online and are working as expected.

      When attempting to apply the configuration to the troublesome interface (specifically by setting the "Failover peer IP") the reciprocal setting on the backup cluster member is assigned the wrong ip address.

      e.g

      I have a GUEST VLAN/interface.
      The CARP ip is 10.92.20.1/24
      The primary member ip is 10.92.20.2/24
      The backup member ip is 10.92.20.3/24

      When setting the "Failover peer ip" on the primary member to 10.92.20.3 I would then expect the corresponding config on the backup member to have 10.92.20.2 in this field.
      Instead on the backup member I am seeing the ip address of the WAN interface being inserted?? How is this possible? It only occurs on this interface.

      Any ideas anyone?

      Thanks,
      Brad.

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