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

    After 24.11 update KEA DHCP static mapping ignored

    Scheduled Pinned Locked Moved DHCP and DNS
    2 Posts 2 Posters 226 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.
    • C
      Cabledude
      last edited by Cabledude

      Hi All,

      I recently installed 24.11 on SG-2100. When my Synology NAS connected to the router, it received a new IP (10.x.x.107) from the DHCP pool (10.x.x.100 - 200), even though there is a static mapping (10.x.x.8). This static mapping has always worked correctly until last week.

      Are there any known KEA issues under 24.11 that may account for this behaviour?

      Steps taken:

      • restarted NAS, no change
      • double checked the NAS MAC address: the MAC in the new 10.x.x.107 lease is exactly the same as the MAC in the static mapping
      • removed the static mapping
      • restarted NAS
      • created new static mapping
      • restarted NAS, but even the new static mapping is not used, the device still gets 10.x.x.107

      Also peculiar: the lease issued by DHCP is 10.x.x.107, which is not the first available number. I would expect 10.x.x.100. This client has the only dynamic lease at this time because all other clients have static mappings, so 10.x.x.100 ~ 106 should be available.

      Thanks!

      Pete
      Home: SG-2100 + UniFi + Synology. SG-1100 retired
      Parents: SG-1100 + UniFi + Synology
      Testing: SG-1100 w/ 120GB SSD via ext USB (eMMC dead). Works great

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

        @Cabledude See thread https://forum.netgate.com/post/1206282, may be similar.

        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
        • C Cabledude referenced this topic on
        • S SteveITS referenced this topic on
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.