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

    DHCP Peer not receiving all info

    DHCP and DNS
    2
    3
    1.0k
    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
      jasonlitka
      last edited by

      I was having some issues with DHCP on my network a while back (turned out to be my core L3 switches) so I had disabled DHCP on my second pfSense box.

      Having resolved that core issue, and having upgraded to pfSense 2.1, I just reenabled the DHCP peering but I'm seeing some odd results.

      On box #1 I see hostnames for clients I assume received an IP from that box and all clients are marked as "Online".  On box #2 I see hostnames for clients which received an IP from that box and only those clients are marked as "online".  Why does box #2 show the systems which received an IP from box #1 as "offline" and why does neither box show all the host names?

      EDIT:  A small percentage of clients (maybe 5%) show their hostnames on both boxes.

      I can break anything.

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

        The online indicator only tells you if that MAC address is in the firewall's ARP table. It 100% accurate to tell you if a system is actually turned on and using the IP locally.

        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
        • J
          jasonlitka
          last edited by

          @jimp:

          The online indicator only tells you if that MAC address is in the firewall's ARP table. It 100% accurate to tell you if a system is actually turned on and using the IP locally.

          Ah, ok, that explains it.  The secondary system wouldn't see the other boxes unless the first system failed and all the CARP addresses moved over.

          How about the issue with the hostnames?

          I can break anything.

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