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

    Kea DHCP Server config changes not applied until reboot

    Scheduled Pinned Locked Moved DHCP and DNS
    15 Posts 5 Posters 475 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.
    • K
      KB8DOA @patient0
      last edited by

      @patient0

      Now - go and change that client's reserved IP address and watch as the client will not pick up the change after you save it...

      Default DHCP time.

      Reboot of client, it just gets issued the old IP address.

      Yes - the reservation is outside the Static Pool.

      Patches? Really?
      I keep running update - and all seems updated.

      If there is something specific to KEA DHCP in the patches, I am willing to apply the patches.

      Best Practice is to keep the updates current and not to apply patches unless specific fix is needed.

      However this is common DHCP operation, which I would expect has been fixed in an update - not a "patch"...

      R patient0P 2 Replies Last reply Reply Quote 0
      • R
        Ramosel @KB8DOA
        last edited by

        @KB8DOA There was one patch related to KEA and I applied that weeks ago. It had no impact on the problem I had this weekend or the issue you are working on.

        Rick

        1 Reply Last reply Reply Quote 0
        • patient0P
          patient0 @KB8DOA
          last edited by

          @KB8DOA said in Kea DHCP Server config changes not applied until reboot:

          Now - go and change that client's reserved IP address and watch as the client will not pick up the change after you save it..

          Did change the reservation and the client picket it up, it does work for me.
          From dynamic (.102, range .100 - .199) to static mapping (.78) to another static mapping (.40). For the last change it took a minute or so after the link up on the client.

          K 1 Reply Last reply Reply Quote 0
          • K
            KB8DOA @patient0
            last edited by

            @patient0

            I will try applying the patches tonight when I reboot the pfsense.

            K 1 Reply Last reply Reply Quote 0
            • K
              KB8DOA @KB8DOA
              last edited by

              @KB8DOA

              No patches avail:
              24_11_NoPatches.png

              R S 2 Replies Last reply Reply Quote 0
              • R
                Ramosel @KB8DOA
                last edited by

                @KB8DOA
                The one patch I found for Kea was for the plus version 24.11. I had applied it a week or so back. Made no difference in my issues last night and today.

                Fix Kea failure with per-pool settings for Default or Maximum Lease Time (If this patch offers both Apply and Revert actions, do not Revert, Redmine #15332)

                Bill Meeks left an informative note on my issue about significant differences between the Kea versions for CE and Plus. But even those differences didn't make Kea work for my problem. Thanks for posting on the reboot. That is the only thing I could do to fix my issue.

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

                  @KB8DOA There should be a lot. Did you update the patches package?

                  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
                  • GertjanG
                    Gertjan @KB8DOA
                    last edited by Gertjan

                    @KB8DOA said in Kea DHCP Server config changes not applied until reboot:

                    Restarting the DHCP Service does not help - a reboot is the only way the changes will take effect.

                    8e93577f-4174-46b4-9340-2a19e0855865-image.png

                    cat  /usr/local/etc/kea/kea-dhcp4.conf
                    

                    and hit execute.

                    Keep te screen open, and open another pfSense GUI, and go to the DHCPv4 settings pages.

                    Now : compare.

                    Most, if not all, what is shown in the file is easy to understand.

                    The (your) question : what setting is present in the GUI that you can't find in the config file ?

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

                    K 1 Reply Last reply Reply Quote 0
                    • K
                      KB8DOA @Gertjan
                      last edited by KB8DOA

                      @Gertjan

                      I am not saying that the conf file and GUI are different.
                      What I am saying is that the GUI/conf changes do not get applied until I reboot pfSense.

                      I have verified, and the changes I made are already in the conf file.
                      Also - just to clarify - I am using the default DHCP Lease time.

                      2 examples:

                      Change DNS Servers for an interface:

                      • the devices on that interface keep renewing for weeks and are still using the old DNS Servers...
                      • upon rebooting, all the devices will start using the new DNS Servers.

                      Assign Static Mapping of IP:

                      • the device will continue to keep renewing and using the default ip address assigned from the Pool for weeks...
                      • upon rebooting, the device will start using the Static IP Address that has been assigned to it.
                      1 Reply Last reply Reply Quote 0
                      • K
                        KB8DOA
                        last edited by

                        Had it happen again.

                        After rebooting pfSense+, the DHCP server finally issued the correct IP Address to the DHCP Client.

                        Does anyone else want me to try something?

                        GertjanG 1 Reply Last reply Reply Quote 0
                        • K
                          KB8DOA @Ramosel
                          last edited by

                          @Ramosel

                          You are welcome.

                          I am going to start looking into going back to ISC DHCP.

                          Even though it is EOL, at least it is not Beta...

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

                            @KB8DOA said in Kea DHCP Server config changes not applied until reboot:

                            Had it happen again.

                            If you have some spare moments, run this while using ISC, and Kea :

                            7526decc-6b7f-44a0-a722-bc7d827070b1-image.png

                            and hit the start button.

                            You'll see the DHCP "client" requests in real time, the ones reaching your pfSense DHCP server, and the DHCP server answers.

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

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