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

    [2.0.1] [DHCP CARP Problem] Hostnames not syncing

    Scheduled Pinned Locked Moved DHCP and DNS
    1 Posts 1 Posters 1.6k 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.
    • J
      Jonher937
      last edited by

      Hi!

      So I had DHCP failover fully working a couple of weeks ago, everything was syncing just fine.
      Then this Tuesday we removed a interface from the pfSense and not disabling the DHCP before we did that.
      Which resulted in the CARP going wild with DHCP. The DHCP.conf had changed addresses like a maniac.

      We had to add the interface again on the same vlan and fill in the DHCP information, then disable the DHCP and after that, the interface.

      But now it's not syncing ALL hostnames. Just some of them.
      Any ideas?

      CARP 1:

      
      option domain-name "test.lab";
      option ldap-server code 95 = text;
      option domain-search-list code 119 = text;
      
      default-lease-time 7200;
      max-lease-time 86400;
      log-facility local7;
      ddns-update-style none;
      one-lease-per-client true;
      deny duplicates;
      ping-check true;
      authoritative;
      failover peer "dhcp0" {
        primary;
        address 172.16.0.2;
        port 519;
        peer address 172.16.0.3;
        peer port 520;
        max-response-delay 10;
        max-unacked-updates 10;
        split 128;
        mclt 600;
      
        load balance max seconds 3;
      }
      subnet 172.16.0.0 netmask 255.255.0.0 {
      	pool {
      		option domain-name-servers 172.16.0.1;
      		deny dynamic bootp clients;
      		failover peer "dhcp0";
      		range 172.16.1.20 172.16.2.254;
      	}
      	option routers 172.16.0.1;
      	option domain-name-servers 172.16.0.1;
      	default-lease-time 7200;
      	max-lease-time 86400;
      
      }
      
      

      CARP 2:

      
      option domain-name "test.lab";
      option ldap-server code 95 = text;
      option domain-search-list code 119 = text;
      
      default-lease-time 7200;
      max-lease-time 86400;
      log-facility local7;
      ddns-update-style none;
      one-lease-per-client true;
      deny duplicates;
      ping-check true;
      authoritative;
      failover peer "dhcp0" {
        secondary;
        address 172.16.0.3;
        port 520;
        peer address 172.16.0.2;
        peer port 519;
        max-response-delay 10;
        max-unacked-updates 10;
        mclt 600;
      
        load balance max seconds 3;
      }
      subnet 172.16.0.0 netmask 255.255.0.0 {
      	pool {
      		option domain-name-servers 172.16.0.1;
      		deny dynamic bootp clients;
      		failover peer "dhcp0";
      		range 172.16.1.20 172.16.2.254;
      	}
      	option routers 172.16.0.1;
      	option domain-name-servers 172.16.0.1;
      	default-lease-time 7200;
      	max-lease-time 86400;
      
      }
      
      

      And another question, not completely related to this error, but why is the peer port/port different on the pfSense boxes?

      Thanks in advance!

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