Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Kea
Kea
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 445
    • Issues 445
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 71
    • Merge Requests 71
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #266

Closed
Open
Opened Nov 09, 2018 by Francis Dupont@fdupontDeveloper

ISC DHCP release on roam flag

          release-on-roam flag;

          When enabled and the dhcpd server detects that a  DHCPv6  client
          (IAID+DUID)  has  roamed  to  a new network, it will release the
          pre-existing leases on the old network and emit a log  statement
          similiar to the following:

                "Client:  <id>  roamed  to  new  network, releasing lease:
          <address>"

          The server will carry out all of the same steps that would  nor-
          mally  occur  when  a  client explicitly releases a lease.  When
          release-on-roam is disabled (the default) the server makes  such
          leases unavailable until they expire or the server is restarted.
          Clients that need leases in  multiple  networks  must  supply  a
          unique IAID in each IA.  This parameter may only be specified at
          the global level.

Make sense for a moving client which for some reasons does not release its address at the previous location. Can be implemented in Kea if there is an easy and fast way to get leases by IAID+DUID only.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
ISC DHCP Migration
Milestone
ISC DHCP Migration
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/kea#266