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

    Kea DHCP does not give new IP addresses

    Scheduled Pinned Locked Moved DHCP and DNS
    4 Posts 2 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.
    • P
      pfsense57352
      last edited by pfsense57352

      Hello,

      I'm very new to pfsense. Started to using it a month ago or so. Installed on Protectli hardware. It was running fine all month, but today, i've noticed that new devices don't get IP address, but those who are in static IP table, works fine.

      Removed cable that goes to the main switch and connected new laptop directly to the same port, new laptop and old phone still did not got IP address. By the way the same new laptop yesterday was working fine. Old phone was working fine a few days ago.

      Restarted pfsense - same story. Also noticed that all IP's that still have active lease time, got back it's IP's and working. Only new devices doesn't get IP.

      Then added new laptop mac address to static leases table and it started work immediately. But all other new devices, that are not in static lease table does not work, they don't get a IP address.

      Checked pool size, there are plenty of available IP's, pool utilization 38%.

      In the dhcp look i see many of these errors:

      WARN [kea-dhcp4.alloc-engine.0x2b8356c15f00] ALLOC_ENGINE_V4_ALLOC_FAIL_CLASSES [hwtype=1 xx:xx:xx:xx:xx:xx], cid=[no info], tid=0xabcd01a9: Failed to allocate an IPv4 address for client with classes: ALL, pool_lan_0, pool_opt3_0, UNKNOWN

      Any idea how to solve it? Where could be a problem?

      T.Y.

      S 1 Reply Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @pfsense57352
        last edited by

        @pfsense57352 I don’t have a direct answer and I didn’t have that experience briefly test Kea but Kea is still a feature preview so if you have issues just switch back to the default DHCP server.

        Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
        Upvote 👍 helpful posts!

        P 1 Reply Last reply Reply Quote 0
        • P
          pfsense57352 @SteveITS
          last edited by

          @SteveITS thank you for your message.
          I'm quite new to pfsense. I only started to use it couple of months ago. And once i've installed it told me, that standard DHCP will be removed as out dated, and there is suggestion to use kea dhcp. As i've seen this recommendation i started from kea, but it's failing :(
          It is strange, that pfsense suggesting to use such a buggy item.

          S 1 Reply Last reply Reply Quote 1
          • S
            SteveITS Galactic Empire @pfsense57352
            last edited by

            @pfsense57352 I agree the wording could have been different. It is labeled as a feature preview in the release notes:
            https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#kea-dhcp-server-feature-preview-now-available

            Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
            When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
            Upvote 👍 helpful posts!

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