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

    Dhcpd carp - recover peer unknown state

    Scheduled Pinned Locked Moved DHCP and DNS
    3 Posts 2 Posters 2.3k 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.
    • I
      instabin
      last edited by

      master config files

      http://pastebin.com/WJgWtH6J

      backup dhcpd.config

      option domain-name "fultonprecision.local";
      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 192.168.0.3;
        port 520;
        peer address 192.168.0.2;
        peer port 519;
        max-response-delay 10;
        max-unacked-updates 10;
        mclt 600;

      load balance max seconds 3;
      }
      subnet 192.168.0.0 netmask 255.255.255.0 {
      pool {
      option domain-name-servers 192.168.0.10,192.168.0.11;
      deny dynamic bootp clients;
      failover peer "dhcp0";
      range 192.168.0.160 192.168.0.199;
      }
      option routers 192.168.0.3;
      option domain-name "fultonprecision.local";
      option domain-name-servers 192.168.0.10,192.168.0.11;
      option netbios-name-servers 192.168.0.10,192.168.0.11;
      option netbios-node-type 8;

      }
      host s_lan_0 {
      hardware ethernet 00:23:eb:b0:c8:23;
      fixed-address 192.168.0.5;
      }
      host s_lan_1 {
      hardware ethernet 00:23:eb:b1:57:5a;
      fixed-address 192.168.0.6;
      }
      host s_lan_2 {
      hardware ethernet 00:07:e9:4f:9c:4d;
      fixed-address 192.168.0.9;
      }
      host s_lan_3 {
      hardware ethernet 00:0c:f1:d1:94:33;
      fixed-address 192.168.0.10;
      }
      host s_lan_4 {
      hardware ethernet 00:19:b9:ce:13:b5;
      fixed-address 192.168.0.11;
      }
      host s_lan_5 {
      hardware ethernet 00:1f:c6:1a:7d:21;
      fixed-address 192.168.0.12;
      }
      host s_lan_6 {
      hardware ethernet 00:0c:f1:89:bc:5c;
      fixed-address 192.168.0.100;
      }
      host s_lan_7 {
      hardware ethernet 00:11:43:19:74:96;
      fixed-address 192.168.0.101;
      }
      host s_lan_8 {
      hardware ethernet 00:0d:56:64:b4:ae;
      fixed-address 192.168.0.102;
      }
      host s_lan_9 {
      hardware ethernet 00:11:43:a3:42:95;
      fixed-address 192.168.0.103;
      }
      host s_lan_10 {
      hardware ethernet 00:11:43:19:73:70;
      fixed-address 192.168.0.104;
      }
      host s_lan_11 {
      hardware ethernet 00:11:43:19:71:dd;
      fixed-address 192.168.0.105;
      }
      host s_lan_12 {
      hardware ethernet 00:19:d1:03:65:95;
      fixed-address 192.168.0.106;
      }
      host s_lan_13 {
      hardware ethernet 00:19:d1:03:1f:a5;
      fixed-address 192.168.0.107;
      }
      host s_lan_14 {
      hardware ethernet 00:11:11:b6:4f:13;
      fixed-address 192.168.0.108;
      }
      host s_lan_15 {
      hardware ethernet 00:0d:56:1c:69:5f;
      fixed-address 192.168.0.109;
      }
      host s_lan_16 {
      hardware ethernet 00:0d:56:64:b1:d8;
      fixed-address 192.168.0.110;
      }
      host s_lan_17 {
      hardware ethernet 00:0c:1f:ea:84:6a;
      fixed-address 192.168.0.111;
      }
      host s_lan_18 {
      hardware ethernet 00:04:e2:35:18:ae;
      fixed-address 192.168.0.112;
      }
      host s_lan_19 {
      hardware ethernet 00:19:d1:22:8b:36;
      fixed-address 192.168.0.114;
      }
      host s_lan_20 {
      hardware ethernet 00:0c:f1:9b:84:8a;
      fixed-address 192.168.0.115;
      }
      host s_lan_21 {
      hardware ethernet 00:22:15:98:37:e0;
      fixed-address 192.168.0.116;
      }
      host s_lan_22 {
      hardware ethernet 00:0c:f1:dd:cb:a3;
      fixed-address 192.168.0.117;
      }
      host s_lan_23 {
      hardware ethernet 00:90:4b:71:d1:de;
      fixed-address 192.168.0.118;
      }
      host s_lan_24 {
      hardware ethernet 00:1f:3c:a0:8d:8b;
      fixed-address 192.168.0.119;
      }
      host s_lan_25 {
      hardware ethernet 00:01:23:05:c2:b6;
      fixed-address 192.168.0.150;
      }
      host s_lan_26 {
      hardware ethernet 00:c0:a8:7e:f7:60;
      fixed-address 192.168.0.151;
      }
      host s_lan_27 {
      hardware ethernet 00:01:23:05:be:dd;
      fixed-address 192.168.0.152;
      }
      host s_lan_28 {
      hardware ethernet 00:01:23:05:bf:64;
      fixed-address 192.168.0.153;
      }
      host s_lan_29 {
      hardware ethernet 00:e0:4c:e5:81:19;
      fixed-address 192.168.0.154;
      }
      host s_lan_30 {
      hardware ethernet 00:0c:46:00:31:2d;
      fixed-address 192.168.0.155;
      }
      host s_lan_31 {
      hardware ethernet 00:1a:a0:62:f0:14;
      fixed-address 192.168.0.156;
      }
      host s_lan_32 {
      hardware ethernet 00:01:23:05:df:ca;
      fixed-address 192.168.0.157;
      }
      host s_lan_33 {
      hardware ethernet 00:01:23:05:dc:31;
      fixed-address 192.168.0.158;
      }
      host s_lan_34 {
      hardware ethernet 00:01:23:05:e4:ef;
      fixed-address 192.168.0.159;
      }
      host s_lan_35 {
      hardware ethernet 00:c0:ee:1a:69:06;
      fixed-address 192.168.0.201;
      }
      host s_lan_36 {
      hardware ethernet 00:c0:ee:71:60:1b;
      fixed-address 192.168.0.202;
      }
      host s_lan_37 {
      hardware ethernet 00:c0:ee:1d:20:73;
      fixed-address 192.168.0.203;
      }
      host s_lan_38 {
      hardware ethernet 00:c0:ee:1d:65:55;
      fixed-address 192.168.0.204;
      }
      host s_lan_39 {
      hardware ethernet 00:23:69:6d:c1:81;
      fixed-address 192.168.0.250;
      }
      host s_lan_40 {
      hardware ethernet 00:1d:7e:0a:ca:b4;
      fixed-address 192.168.0.251;
      }
      host s_lan_41 {
      hardware ethernet 00:1d:7e:0a:cd:34;
      fixed-address 192.168.0.252;
      }
      host s_lan_42 {
      hardware ethernet 00:1d:7e:0a:c2:24;
      fixed-address 192.168.0.253;
      }
      host s_lan_43 {
      hardware ethernet 6c:50:4d:c1:6b:3c;
      fixed-address 192.168.0.254;
      }

      backup config.xml

      <virtualip><vip><mode>carp</mode>
      <interface>lan</interface>
      <vhid>1</vhid>
      <advskew>100</advskew>
      <password>lanpass</password>

      <type>single</type>
      <subnet_bits>24</subnet_bits>
      <subnet>192.168.0.1</subnet></vip>
      <vip><mode>carp</mode>
      <interface>wan</interface>
      <vhid>2</vhid>
      <advskew>100</advskew>
      <password>wanpass</password>

      <type>single</type>
      <subnet_bits>8</subnet_bits>
      <subnet>10.1.10.2</subnet></vip>
      <vip><mode>other</mode>
      <interface>wan</interface>

      <type>single</type>
      <subnet_bits>31</subnet_bits>
      <subnet>75.147.101.5</subnet></vip></virtualip>

      1 Reply Last reply Reply Quote 0
      • I
        instabin
        last edited by

        I fixed it after finding this post
        http://www.mail-archive.com/support@pfsense.com/msg14464.html

        I created a rule to allow ports 519 and 520 with a source and destination of lan subnet

        1 Reply Last reply Reply Quote 0
        • jimpJ
          jimp Rebel Alliance Developer Netgate
          last edited by

          FYI- on 2.0 when setting that up the rules are added for 519/520 automatically.

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

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