Kea issueshttps://gitlab.isc.org/isc-projects/kea/-/issues2022-11-02T15:08:42Zhttps://gitlab.isc.org/isc-projects/kea/-/issues/46Please add circuit-ID to result of get lease-42022-11-02T15:08:42ZGhost UserPlease add circuit-ID to result of get lease-4We want to identify leases with circuit ID, how can we get the circuit ID with the lease4-get?
I want to search for a lease with the circuit ID with lease-get.
Vennlig hilsen / Best regards
Frode SætreWe want to identify leases with circuit ID, how can we get the circuit ID with the lease4-get?
I want to search for a lease with the circuit ID with lease-get.
Vennlig hilsen / Best regards
Frode Sætrebackloghttps://gitlab.isc.org/isc-projects/kea/-/issues/580Add support for associating a subnet with shared network via remote-subnet4-set2019-06-13T07:35:07ZMarcin SiodelskiAdd support for associating a subnet with shared network via remote-subnet4-setThe cb_cmds hooks library supports remote-subnet4-set command which can be used to add or update a subnet in the config backend. There is currently no way to add a subnet to an existing shared network, nor update the subnet being in a sh...The cb_cmds hooks library supports remote-subnet4-set command which can be used to add or update a subnet in the config backend. There is currently no way to add a subnet to an existing shared network, nor update the subnet being in a shared network. The only way to add a subnet within a shared network is by issuing remote-network4-set, but that's an overkill if the shared network contains many subnets.
The following is the relevant part of the design: https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuration-in-db-design#remote-subnet4-set
It proposes an optional parameter `shared-network-name` within a subnet definition which would specify that the added/updated subnet should be placed within a shared network having a given name. This issue is about implementing this functionality.Kea1.6Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/365Automatically calculate the values for options 58 and 592019-04-26T15:37:42ZCathy AlmondAutomatically calculate the values for options 58 and 59---
name: Automatically calculate the values for options 58 and 59
about: This is a request to have it be possible for Kea to calculate and send the values for renew-timer and rebind-timer (T1 and T2) using 0.5 * duration_of_lease, and ...---
name: Automatically calculate the values for options 58 and 59
about: This is a request to have it be possible for Kea to calculate and send the values for renew-timer and rebind-timer (T1 and T2) using 0.5 * duration_of_lease, and 0.875 * duration_of_lease, respectively
---
**Some initial questions**
This is a request from a customer, per ticket [#13977](https://support.isc.org/Ticket/Display.html?id=13977)
At the moment, ISC Kea defaults to not sending T1 and T2, although they can be specified explicitly using optional renew-timer and rebind-timer. What is being requested is another option in which we ask Kea to automate this - i.e. to calculate them based on the lease time being offered using the default behaviour that clients should be adopting as noted above.
The reason for requesting this is that:
a) Other DHCP servers (e.g. Nominum) do this by default (even though ISC DHCP does not)
b) It is a potential mitigation for clients that are not fully RFC-compliant
**Describe the solution you'd like**
In it's simplest form, a blanket option to request that Kea calculate the timers and send them for any lease offer, calculations being appropriate to that specific offer.
More flexibility might be appreciated however - for example being able to set this per subnet, pool or shared-network to override a global setting which might be different.
For full flexibility, the option could perhaps also have an alternative syntax in which it accepts the percentages as an override to the default of .5 and .875 - although this might be overkill - would anyone want these to be different? (Perhaps leading up to a pool/servers migration maybe?)
**Describe alternatives you've considered**
Currently, the only way to ensure that ISC Kea sends the values of T1 and T2 that are wanted is to configure them explicitly, it's not possible to have them sent automatically
**Additional context**
Note that this may be regarded as a compatibility issue by anyone migrating to ISC Kea from another DHCP server implementation that does automatically send T1 and T2.Kea1.6Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/kea/-/issues/226ISC DHCP server config option adaptive-lease-time-threshold2022-11-02T15:08:42ZFrancis DupontISC DHCP server config option adaptive-lease-time-threshold>>>
The adaptive-lease-time-threshold statement
**adaptive-lease-time-threshold** percentage;
When the number of allocated leases within a pool rises above the
percentage given in this statement, the DHCP server decreases the
lease len...>>>
The adaptive-lease-time-threshold statement
**adaptive-lease-time-threshold** percentage;
When the number of allocated leases within a pool rises above the
percentage given in this statement, the DHCP server decreases the
lease length for new clients within this pool to min-lease-time sec-
onds. Clients renewing an already valid (long) leases get at least
the remaining time from the current lease. Since the leases expire
faster, the server may either recover more quickly or avoid pool
exhaustion entirely. Once the number of allocated leases drop below
the threshold, the server reverts back to normal lease times. Valid
percentages are between 1 and 99.
>>>
A good idea for a lease allocation hook library.backloghttps://gitlab.isc.org/isc-projects/kea/-/issues/219allow an option value to be set from an expression2019-10-25T09:31:24ZFrancis Dupontallow an option value to be set from an expressionISC DHCP has two ways to set an option value: the static one and the dynamic one where an expression is evaluated to give the value to use. Kea has the basic mechanism for expression evaluation so this feature should be implementable wit...ISC DHCP has two ways to set an option value: the static one and the dynamic one where an expression is evaluated to give the value to use. Kea has the basic mechanism for expression evaluation so this feature should be implementable without a large work.kea1.7.1Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/203sysrepo/netconf documentation improvements2018-12-12T23:14:46ZWlodzimierz Wencelsysrepo/netconf documentation improvementsSome of yang models have to be installed by hand and some of them are installed automatically as dependencies of those manually installed. So it would be nice that users guide would list every model that have to be installed by hand. I t...Some of yang models have to be installed by hand and some of them are installed automatically as dependencies of those manually installed. So it would be nice that users guide would list every model that have to be installed by hand. I think those models are: ietf-dhcpv6-server.yang
kea-dhcp4-server.yang
kea-dhcp6-server.yang
kea-dhcp-ddns.yang
kea-ctrl-agent.yang
ietf-inet-types.yang
ietf-yang-types.yang
for testing:
keatest-module.yang
Also docs is missing simple example how to start kea using sysrepocfg, it says ```Such changes can be done using sysrepocfg tool or remotely using any NETCONF client. For details, please see Sysrepo documentation``` and I really don't like the fact we are sending user to different documentation instead of having couple lines like:
```
sudo sysrepocfg -l 4 -d startup -f xml -i startup-4.xml kea-dhcp4-server
sudo sysrepocfg -l 4 -d running -f xml -i twopools-4.xml kea-dhcp4-server
```
with couple sentences explaining what "running" and "startup" datastores really are.Kea1.5-finalhttps://gitlab.isc.org/isc-projects/kea/-/issues/999Add option(s) to make use of an additional Kea backup server (with HA) non-bl...2020-05-18T11:42:10ZCathy AlmondAdd option(s) to make use of an additional Kea backup server (with HA) non-blockingThis is from [Support ticket #15378](https://support.isc.org/Ticket/Display.html?id=15378) and is a follow-up feature request to make a Kea HA pair's operation more independent of any backup Kea server that they're also sending lease upd...This is from [Support ticket #15378](https://support.isc.org/Ticket/Display.html?id=15378) and is a follow-up feature request to make a Kea HA pair's operation more independent of any backup Kea server that they're also sending lease updates to.
The question of whether or not this would be a good idea arose during the investigation of #964 - although this request is orthogonal to the work on that issue.
The question asked was, how important is it that the active server(s) in the HA configuration, wait for an acknowledgement to their lease updates from the backup server?
Notably, the backup server does not participate in any HA monitoring - so the HA pair will not know if it becomes unreachable or goes down - they will just end up waiting indefinitely (or possibly failing on a network send) in that case. This could significantly affect the production environment.
Therefore, this is a proposal that we add a configuration 'knob' to make waiting on the acknowledgement of the lease updates to the backup server, an optional thing. (IF the system administrator prefers for the HA pair to wait, then the onus is on them to ensure the availability and reachability of the backup servers, or else...)
---
Ahem, but that then leads to another 'what if?'. What if some of the lease updates go astray? This probably doesn't matter too much - 'almost right' is going to be a better bet for recovery using a backup server (in case both of the HA pair for some reason disappear entirely), than 'nothing at all'. As part of this feature request therefore, could we also consider implementing (on the backup server) a period lease sync (as if it had just been rebooted and was coming online and starting to participate afresh)?
--- And finally, specifically for backup servers where the main HA pair are *not* waiting on acknowledgements on lease updates, should/could we also add an option to batch lease updates every x seconds (or so), to optimise the process for keeping the backup server up to date?kea1.7.8Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/850Unable to set "interface" for a subnet via remote-subnet4-set when such inter...2019-11-25T16:44:05ZMarcin SiodelskiUnable to set "interface" for a subnet via remote-subnet4-set when such interface is not present in the systemThe cb_cmds uses Kea parsers to parse the subnet information received via commands. The parsers were initially designed to parse local Kea configuration files. The subnet parser, for example, checks whether the interface set for a subnet...The cb_cmds uses Kea parsers to parse the subnet information received via commands. The parsers were initially designed to parse local Kea configuration files. The subnet parser, for example, checks whether the interface set for a subnet is present in the system. If it is not, it spits out an error similar to this:
```
[ { "result": 1, "text": "subnet configuration failed: Specified network interface name vboxnet0 for subnet 192.168.50.0/24 is not present in the system (:0:0)" } ]
```
This shouldn't be the case when setting the configuration via the CB, because a given server should be able to set the configuration for any DHCP server, not necessarily for itself.kea1.7.2Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/849Kea MySQL CB accepts an option for non-existing subnet2022-11-02T15:10:18ZMarcin SiodelskiKea MySQL CB accepts an option for non-existing subnetIt is possible to set a DHCP option with the `remote-option4-subnet-set` for non-existing subnet. It is possible that the same issue is present for other similar commands.It is possible to set a DHCP option with the `remote-option4-subnet-set` for non-existing subnet. It is possible that the same issue is present for other similar commands.backloghttps://gitlab.isc.org/isc-projects/kea/-/issues/747include kea test module in distributions2019-08-02T12:26:15ZFrancis Dupontinclude kea test module in distributionsDetected in 1.6-beta2 sanity checks: src/share/yang/modules/keatest-module*.yang is not included in distributions so a fresh sysrepo tester could be in trouble.Detected in 1.6-beta2 sanity checks: src/share/yang/modules/keatest-module*.yang is not included in distributions so a fresh sysrepo tester could be in trouble.Kea1.6-finalFrancis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/727Reservation client-classes too late/later as documented for depending classes2019-08-15T15:09:28ZChrisReservation client-classes too late/later as documented for depending classes**Describe the bug**
Client classes that are applied from a reservation are added too late to `test` against except for `only-if-required` classes, even when also depending on `KNOWN` (despite of what the NOTE in [Kea Guide 8.3.6](https...**Describe the bug**
Client classes that are applied from a reservation are added too late to `test` against except for `only-if-required` classes, even when also depending on `KNOWN` (despite of what the NOTE in [Kea Guide 8.3.6](https://ftp.isc.org/isc/kea/1.5.0/doc/kea-guide.html#reservation4-client-classes) says).
**To Reproduce**
Steps to reproduce the behavior:
1. Run Kea dhcpv4 with config:
```json[kea-reservation.log](/uploads/282012d6ad4a49c58157219f47d511c7/kea-reservation.log)[kea-reservation.log](/uploads/8b88984ba62689b6768b146dd13dbb7f/kea-reservation.log)
"client-classes": [
{
"name": "pxe"
},
{
"name": "ipxe",
"test": "member('KNOWN') and (option[77].hex == 'iPXE') and member('pxe')",
"boot-file-name": "http://ipxe.example.com/menu.php"
},
{
"name": "not_ipxe",
"next-server": "192.168.100.6",
"boot-file-name": "undionly.kpxe"
}
]
```
MySQL hosts reservation:
```
+--------------+----------+----------------------+
| ipv4_address | hostname | dhcp4_client_classes |
+--------------+----------+----------------------+
| 167837702 | pxetest | pxe,testing |
+--------------+----------+----------------------+
```
2. Logging set kea-dhcp4 to DEBUG, debuglevel 55
3. Client "pxetest" is booted with iPXE
4. Client "pxetest" does not get boot-file-name/added to class `pxe` in time to eval true on `ipxe`
5. See kea-reservation.log for details
(6. See extremely little logging for reservation classes - only reason I know they were applied at all (not even the final list mentions `pxe`!) was the warning about `testing` after lease assignment)
**Expected behavior**
The server is supposed to add client-classes at reservation lookup together with `KNOWN`, so classes that depend on `KNOWN` and a reserved class are evaluated as true, as described in mentioned documentation.
**Environment:**
- Kea version: 1.5.0 from Ubuntu 19.04 repositories (manually downloaded)
- OS: Ubuntu 18.04 x64
- Which features were compiled in:
- MySQL 7.0, library 5.7.26
- PostgreSQL backend 5.0, library 100009 (not used)
- Memfile backend 2.1 (not used)
- If/which hooks where loaded in:
- lease commands
- HA
**Additional Information**
Current workaround is to load classes depending on reserved classes only-if-required, which means adding a `require-client-classes` to all subnets/shared networks as appropriate (in my case 97% of subnets) adding a lot of configuration overhead with the possibility of very long lists in complicating setups, which kinda defeats the purpose of client classes in my mind.
**Log Debuglevel 55**
```
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.dhcpsrv/7390] DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 192.168.100.0/24 for packet received by matching address 192.168.100.1
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.packets/7390] DHCP4_SUBNET_SELECTED [hwtype=1 52:c6:25:f5:34:ac], cid=[01:52:c6:25:f5:34:ac], tid=0xdc575936: the subnet with ID 16 was selected for client assignments
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.packets/7390] DHCP4_SUBNET_DATA [hwtype=1 52:c6:25:f5:34:ac], cid=[01:52:c6:25:f5:34:ac], tid=0xdc575936: the selected subnet details: 192.168.100.0/24
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.hosts/7390] HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using identifier: hwaddr=52C625F534AC
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.hosts/7390] HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=52C625F534AC, found 0 host(s)
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.dhcp4/7390] DHCP4_CLASS_ASSIGNED [hwtype=1 52:c6:25:f5:34:ac], cid=[01:52:c6:25:f5:34:ac], tid=0xdc575936: client packet has been assigned to the following class(es): KNOWN
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.eval/7390] EVAL_DEBUG_MEMBER Checking membership of 'KNOWN', pushing result 'true'
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.eval/7390] EVAL_DEBUG_OPTION Pushing option 77 with value 0x69505845
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.eval/7390] EVAL_DEBUG_STRING Pushing text string 'iPXE'
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.eval/7390] EVAL_DEBUG_EQUAL Popping 0x69505845 and 0x69505845 pushing result 'true'
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.eval/7390] EVAL_DEBUG_AND Popping 'true' and 'true' pushing 'true'
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.eval/7390] EVAL_DEBUG_MEMBER Checking membership of 'pxe', pushing result 'false'
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.eval/7390] EVAL_DEBUG_AND Popping 'false' and 'true' pushing 'false'
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.options/7390] EVAL_RESULT Expression ipxe evaluated to 0
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.eval/7390] EVAL_DEBUG_OPTION Pushing option 77 with value 0x69505845
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.eval/7390] EVAL_DEBUG_STRING Pushing text string 'iPXE'
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.eval/7390] EVAL_DEBUG_EQUAL Popping 0x69505845 and 0x69505845 pushing result 'true'
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.eval/7390] EVAL_DEBUG_NOT Popping 'true' pushing 'false'
2019-07-08 12:15:54.796 DEBUG [kea-dhcp4.eval/7390] EVAL_DEBUG_MEMBER Checking membership of 'pxe', pushing result 'false'
2019-07-08 12:15:54.797 DEBUG [kea-dhcp4.eval/7390] EVAL_DEBUG_AND Popping 'false' and 'false' pushing 'false'
2019-07-08 12:15:54.797 DEBUG [kea-dhcp4.eval/7390] EVAL_DEBUG_MEMBER Checking membership of 'KNOWN', pushing result 'true'
2019-07-08 12:15:54.797 DEBUG [kea-dhcp4.eval/7390] EVAL_DEBUG_AND Popping 'true' and 'false' pushing 'false'
2019-07-08 12:15:54.797 DEBUG [kea-dhcp4.options/7390] EVAL_RESULT Expression not_ipxe evaluated to 0
2019-07-08 12:15:54.797 DEBUG [kea-dhcp4.dhcp4/7390] DHCP4_CLASS_ASSIGNED [hwtype=1 52:c6:25:f5:34:ac], cid=[01:52:c6:25:f5:34:ac], tid=0xdc575936: client packet has been assigned to the following class(es): HA_ns1-kea, ALL, VENDOR_CLASS_PXEClient:Arch:00000:UNDI:002001, deny_snom_dap_pap2t, KNOWN
2019-07-08 12:15:54.797 DEBUG [kea-dhcp4.ddns/7390] DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 52:c6:25:f5:34:ac], cid=[01:52:c6:25:f5:34:ac], tid=0xdc575936: processing client's Hostname option
2019-07-08 12:15:54.797 DEBUG [kea-dhcp4.dhcpsrv/7390] DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID 01:52:c6:25:f5:34:ac
2019-07-08 12:15:54.797 DEBUG [kea-dhcp4.hosts/7390] HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4 get one host with reservation for subnet id 162 and IPv4 address 10.1.0.6
2019-07-08 12:15:54.797 DEBUG [kea-dhcp4.hosts/7390] HOSTS_CFG_GET_ALL_ADDRESS4 get all hosts with reservations for IPv4 address 10.1.0.6
2019-07-08 12:15:54.797 DEBUG [kea-dhcp4.hosts/7390] HOSTS_CFG_GET_ALL_ADDRESS4_COUNT using address 10.1.0.6, found 0 host(s)
2019-07-08 12:15:54.797 DEBUG [kea-dhcp4.hosts/7390] HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4_NULL host not found using subnet id 162 and address 10.1.0.6
2019-07-08 12:15:54.797 DEBUG [kea-dhcp4.hosts/7390] HOSTS_MGR_ALTERNATE_GET4_SUBNET_ID_ADDRESS4 trying alternate sources for host using subnet id 162 and address 10.1.0.6
2019-07-08 12:15:54.797 DEBUG [kea-dhcp4.dhcpsrv/7390] DHCPSRV_MYSQL_GET_ADDR4 obtaining IPv4 lease for address 10.1.0.6
2019-07-08 12:15:54.798 DEBUG [kea-dhcp4.alloc-engine/7390] ALLOC_ENGINE_V4_REQUEST_EXTEND_LEASE [hwtype=1 52:c6:25:f5:34:ac], cid=[01:52:c6:25:f5:34:ac], tid=0xdc575936: extending lifetime of the lease for address 10.1.0.6
2019-07-08 12:15:54.798 DEBUG [kea-dhcp4.dhcpsrv/7390] DHCPSRV_MYSQL_UPDATE_ADDR4 updating IPv4 lease for address 10.1.0.6
2019-07-08 12:15:54.861 DEBUG [kea-dhcp4.packets/7390] DHCP4_SUBNET_DYNAMICALLY_CHANGED [hwtype=1 52:c6:25:f5:34:ac], cid=[01:52:c6:25:f5:34:ac], tid=0xdc575936: changed selected subnet 192.168.100.0/24 to subnet 10.1.0.0/20 from shared network servers for client assignments
2019-07-08 12:15:54.861 INFO [kea-dhcp4.leases/7390] DHCP4_LEASE_ALLOC [hwtype=1 52:c6:25:f5:34:ac], cid=[01:52:c6:25:f5:34:ac], tid=0xdc575936: lease 10.1.0.6 has been allocated
2019-07-08 12:15:54.861 DEBUG [kea-dhcp4.dhcp4/7390] DHCP4_CLASS_UNCONFIGURED [hwtype=1 52:c6:25:f5:34:ac], cid=[01:52:c6:25:f5:34:ac], tid=0xdc575936: client packet belongs to an unconfigured class: testing
2019-07-08 12:15:54.861 DEBUG [kea-dhcp4.callouts/7390] HOOKS_CALLOUTS_BEGIN begin all callouts for hook leases4_committed
2019-07-08 12:15:54.861 DEBUG [kea-dhcp4.callouts/7390] HOOKS_CALLOUT_CALLED hooks library with index 2 has called a callout on hook leases4_committed that has address 0x7efe0edcb150 (callout duration: 0.123 ms)
2019-07-08 12:15:54.861 DEBUG [kea-dhcp4.callouts/7390] HOOKS_CALLOUTS_COMPLETE completed callouts for hook leases4_committed (total callouts duration: 0.123 ms)
2019-07-08 12:15:54.861 DEBUG [kea-dhcp4.hooks/7390] DHCP4_HOOK_LEASES4_COMMITTED_PARK [hwtype=1 52:c6:25:f5:34:ac], cid=[01:52:c6:25:f5:34:ac], tid=0xdc575936: packet is parked, because a callout set the next step to PARK
```
**Contacting you**
Gitlab/hubKea1.6-finalFrancis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/717mysql_cb: extend the backend with the ability to associate the subnets with t...2019-07-12T17:23:10ZMarcin Siodelskimysql_cb: extend the backend with the ability to associate the subnets with the server tagsSimilar to what has been done in #676, we need to extend the existing commands, such as `remote-subnet4-set` and other, to interpret the specified server tags and associate the shared networks with these tags.
This ticket covers both DH...Similar to what has been done in #676, we need to extend the existing commands, such as `remote-subnet4-set` and other, to interpret the specified server tags and associate the shared networks with these tags.
This ticket covers both DHCPv4 and DHCPv6.Kea1.6-beta2Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/716mysql_cb: extend the backend with the ability to associate the shared network...2019-07-09T18:43:51ZMarcin Siodelskimysql_cb: extend the backend with the ability to associate the shared networks with the server tagsSimilar to what has been done in #676, we need to extend the existing commands, such as `remote-network4-set` and other, to interpret the specified server tags and associate the shared networks with these tags.
This ticket covers both D...Similar to what has been done in #676, we need to extend the existing commands, such as `remote-network4-set` and other, to interpret the specified server tags and associate the shared networks with these tags.
This ticket covers both DHCPv4 and DHCPv6.Kea1.6-beta2Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/715mysql_cb: extend the backend with the ability to associate the option definit...2019-07-06T18:31:23ZMarcin Siodelskimysql_cb: extend the backend with the ability to associate the option definitions with the server tagsSimilar to what has been done in #676, we need to extend the existing commands, such as `remote-option-def4-set` and other, to interpret the specified server tags and associate the option definitions with these tags.
This ticket covers ...Similar to what has been done in #676, we need to extend the existing commands, such as `remote-option-def4-set` and other, to interpret the specified server tags and associate the option definitions with these tags.
This ticket covers both DHCPv4 and DHCPv6.Kea1.6-beta2Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/714mysql_cb: extend the backend with the ability to associate the global options...2019-07-04T20:29:19ZMarcin Siodelskimysql_cb: extend the backend with the ability to associate the global options with the server tagsSimilar to what has been done in #676, we need to extend the existing commands, such as `remote-option4-global-set` and other, to interpret the specified server tags and associate the options with these tags.
This ticket covers both DHC...Similar to what has been done in #676, we need to extend the existing commands, such as `remote-option4-global-set` and other, to interpret the specified server tags and associate the options with these tags.
This ticket covers both DHCPv4 and DHCPv6.Kea1.6-beta2Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/713cb_cmds: add support for the server tags in the subnets2019-07-16T15:51:39ZMarcin Siodelskicb_cmds: add support for the server tags in the subnetsWe need to extend the cb_cmds to facilitate associating the subnets with the server tags. See the following link for command examples: https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuration-in-db-design#remote-subnet4-del-by...We need to extend the cb_cmds to facilitate associating the subnets with the server tags. See the following link for command examples: https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuration-in-db-design#remote-subnet4-del-by-id.
This ticket covers both DHCPv4 and DHCPv6.Kea1.6-beta2Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/712cb_cmds: add support for server tags in the shared networks2019-07-12T20:58:31ZMarcin Siodelskicb_cmds: add support for server tags in the shared networksExtend cb_cmds to facilitate associating the shared networks being added with the server tags. See the following link for the examples: https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuration-in-db-design#remote-network4-set....Extend cb_cmds to facilitate associating the shared networks being added with the server tags. See the following link for the examples: https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuration-in-db-design#remote-network4-set.
This ticket covers both DHCPv4 and DHCPv6.Kea1.6-beta2Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/711cb_cmds: add support for server tags in option definitions2019-07-10T07:43:03ZMarcin Siodelskicb_cmds: add support for server tags in option definitionsExtend the cb_cmds to support associating option definitions with the server tags, similar to what has been done in #676. See the design: https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuration-in-db-design#remote-option-def4...Extend the cb_cmds to support associating option definitions with the server tags, similar to what has been done in #676. See the design: https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuration-in-db-design#remote-option-def4-del.
This ticket covers both DHCPv4 and DHCPv6.Kea1.6-beta2Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/710cb_cmds: add support for server tags in global options2019-07-09T08:02:32ZMarcin Siodelskicb_cmds: add support for server tags in global optionsSimilar to #676, we need to extend the cb_cmds: remote-option4-global-X commands and appropriate unit tests to facilitate the server tags. See the examples in the design: https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuratio...Similar to #676, we need to extend the cb_cmds: remote-option4-global-X commands and appropriate unit tests to facilitate the server tags. See the examples in the design: https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuration-in-db-design#remote-option4-global-del.
This ticket covers both DHCPv4 and DHCPv6.Kea1.6-beta2Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/709cb_cmds: add support for commands to manage the servers2019-07-04T11:49:15ZMarcin Siodelskicb_cmds: add support for commands to manage the serversExtended cb_cmds hooks library with the new commands: `remote-serverX-del`, `remote-serverX-get`, `remote-serverX-get-all` and `remote-serverX-set`. See the design: https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuration-in-d...Extended cb_cmds hooks library with the new commands: `remote-serverX-del`, `remote-serverX-get`, `remote-serverX-get-all` and `remote-serverX-set`. See the design: https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuration-in-db-design#remote-server4-delKea1.6-beta2Francis DupontFrancis Dupont