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

    dhcp failing to report online

    Scheduled Pinned Locked Moved DHCP and DNS
    3 Posts 2 Posters 425 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.
    • H
      Halfhidden
      last edited by

      Not sure if anyone has experienced this or knows what may be wrong as I have no idea where to start.
      Basically I have Pfsense installed on a server running PPoe with a router in bridge mode. Now I have two more servers that run containers and VM's. I've set up DHCP with Pfsense and it is giving out ip's from its pool. But the problem is that when I check DHCP lease I can see that some of the containers are offline, yet when I ping them they respond. I can direct access them through the ip address but Pfsense insists that the container is offline.
      I've checked cables and run packet tests and everything seems to be working fine.

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan @Halfhidden
        last edited by

        @Halfhidden said in dhcp failing to report online:

        are offline

        The "idle/offline" or "active" indication reflects the presence of the MAC in the pfSense arp cache.
        The arp cache doesn't have a duration of the DHCP lease, it's OS depended and far smaller.
        See Diagnostics > ARP Table
        Ping, from pfSense, an IP that has a lease.
        Check Diagnostics > ARP Table again : now the IP + MAC of that device is present in the ARP table.

        .... and back again on the DHCP lese page : the lease is now marked 'green and active'.

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        H 1 Reply Last reply Reply Quote 1
        • H
          Halfhidden @Gertjan
          last edited by

          @Gertjan
          That's great information. I'll follow your guidance.
          That also make perfect sense as I have cloned a container that has been allocated the same IP address as the predecessor. Obviously a new Mac would have been created by the hypervisor.
          Thanks again for fantastic information

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