Kea issueshttps://gitlab.isc.org/isc-projects/kea/-/issues2019-03-27T21:16:52Zhttps://gitlab.isc.org/isc-projects/kea/-/issues/546Parse Reconfig accept option and save client context in leases2019-03-27T21:16:52ZFrancis DupontParse Reconfig accept option and save client context in leasesFrom https://github.com/isc-projects/kea/pull/100From https://github.com/isc-projects/kea/pull/100Kea1.6Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/326Handle Reconfigure Accept Option #872023-05-30T11:04:20ZVicky Riskvicky@isc.orgHandle Reconfigure Accept Option #87Mayya Sunil opened on Github as issue #87 on June 1, 2018
Reconfigure Accept Option : Included in Server's Replies, Advertise message and client's Solicit, Request, Renew, Rebind, Information Request to announce support of Reconfigure f...Mayya Sunil opened on Github as issue #87 on June 1, 2018
Reconfigure Accept Option : Included in Server's Replies, Advertise message and client's Solicit, Request, Renew, Rebind, Information Request to announce support of Reconfigure feature.
This issue involves 2 tasks
Include the option in the server's outgoing message.
2)Parse the option in the client's message and generate and store the keys in the reservation if keys not available.
----------
MayyaSunil pushed a commit to MayyaSunil/kea that referenced this issue on Aug 14
[store_client_context] Stotes client info in user contexts …
a09944dnext-stable-2.62020-02-29https://gitlab.isc.org/isc-projects/kea/-/issues/1739Implement FORCERENEW support (RFC3203)2022-11-02T17:06:58ZTomek MrugalskiImplement FORCERENEW support (RFC3203)This is roughly a v4 equivalent of RECONFIGURE message in v6. This is not a popular feature (due to lack of support among clients), but it is being requested sporadically.
* [asking about forcerenew on kea-users](https://lists.isc.org/p...This is roughly a v4 equivalent of RECONFIGURE message in v6. This is not a popular feature (due to lack of support among clients), but it is being requested sporadically.
* [asking about forcerenew on kea-users](https://lists.isc.org/pipermail/kea-users/2020-October/002910.html)
* [another one from 2017](http://kea-users.7364.n8.nabble.com/Kea-users-FORCERENEW-feature-td435.html)backloghttps://gitlab.isc.org/isc-projects/kea/-/issues/350Ability to send DHCPv6 Reconfigure message2023-09-21T10:10:36ZTomek MrugalskiAbility to send DHCPv6 Reconfigure messageThis is a migration of [issue #84](https://github.com/isc-projects/kea/issues/84) from github.
The goal of this ticket is to implement capability to send reconfigure message. This at the very least requires implementing a "reconfig-send...This is a migration of [issue #84](https://github.com/isc-projects/kea/issues/84) from github.
The goal of this ticket is to implement capability to send reconfigure message. This at the very least requires implementing a "reconfig-send" command, and the actual ability to retrieve lease from db and then send reconfigure message with authentication option.
Here's [one request for it](https://lists.isc.org/pipermail/kea-users/2020-October/002910.html).backlog2020-02-29https://gitlab.isc.org/isc-projects/kea/-/issues/325Implement RDM mechanism (Github#85)2022-11-02T15:08:41ZVicky Riskvicky@isc.orgImplement RDM mechanism (Github#85)<Originally opened by Tomek Mrugalski on Github as issue #85>
The RFC8415 defines Replay Detection Mechanism. We need to have this implemented in Kea.
We'll go with the simplest model possible. The RDM will be a global 64bits counter (...<Originally opened by Tomek Mrugalski on Github as issue #85>
The RFC8415 defines Replay Detection Mechanism. We need to have this implemented in Kea.
We'll go with the simplest model possible. The RDM will be a global 64bits counter (the same value for all subnets and all clients. This value must be retained between server restarts.backlog2020-02-29https://gitlab.isc.org/isc-projects/kea/-/issues/199Integrate DHCPv6 reconfigure message feature2022-11-02T15:08:42ZMayyaSunilIntegrate DHCPv6 reconfigure message featureReconfiguration feature was implemented partially as a part of GSoC 2018 project. This issue is to track the integration of the remaining feature into kea repo.Reconfiguration feature was implemented partially as a part of GSoC 2018 project. This issue is to track the integration of the remaining feature into kea repo.backlogMarcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/1137some configuration related functions should throw exception if called from pa...2021-10-20T11:53:14ZRazvan Becheriusome configuration related functions should throw exception if called from packet processing functions or while processing packets (in MT)outstandingRazvan BecheriuRazvan Becheriuhttps://gitlab.isc.org/isc-projects/kea/-/issues/913Implement OptionAuth for use with DHCPv6 authentication and reconfiguration2019-09-19T09:52:03ZMarcin SiodelskiImplement OptionAuth for use with DHCPv6 authentication and reconfigurationThe Reconfigure mechanism requires that the server sends Authentication Option (11) to the clients to communicate the authentication key during the Solicit/Reply, Request/Reply and Information-request/Reply transactions. It also uses thi...The Reconfigure mechanism requires that the server sends Authentication Option (11) to the clients to communicate the authentication key during the Solicit/Reply, Request/Reply and Information-request/Reply transactions. It also uses this option in the Reconfigure messages. The option comprises a record of fields and can't be represented by any of the existing options. The limitation of the `OptionCustom` class is that the Auth option has the 64-bit field for Replay Detection and `OptionCustom` does not support 64-bit fields. We could extend the `OptionCustom` but in fact it is better (and cleaner) to have a dedicated class to represent Auth Option as it has very specific usage and a few convenience functions could be added to this new class to make it easy to manipulate this option. The `OptionCustom` is very generic.