Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 561
    • Issues 561
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 69
    • Merge requests 69
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • KeaKea
  • Issues
  • #287
Closed
Open
Issue created Nov 27, 2018 by Hreidar Joelsson@hreidar

Design flaw in the allocation engine ?

Hi, I think I found a design flaw in KEAs allocation engine. I've developed a hook that lets me choose from which subnet a client gets a lease from. This subnet is one of several subnets in a shared network configured in KEA. All this works well until I need to choose another subnet for this same client. Then KEA ignores my choice and logs out that it has "a better one" with the DHCP4_SUBNET_DYNAMICALLY_CHANGED message. This design beats the purpose of letting a hook code choose a subnet if it can not be suppressed somehow. I have managed to change this behavior in my usecase by commenting out some lines of code using my build script like so: sed -i '3585,3595 {s/^/\/\//}' ./src/lib/dhcpsrv/alloc_engine.cc I think this can be fixed by letting users turn this "feature" off using a flag or something which could be passed into KEA in the subnet4_select hook. I'm currently working with KEA 1.4.0-P1 so these ten lines I'm commenting out (from 3585 ot 3595) are based on that codebase.

Best regards, Hreidar.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking