... | ... | @@ -24,7 +24,7 @@ This page documents status of client classification as of 1.5.0 (January 2019), |
|
|
|
|
|
# Possible actions
|
|
|
|
|
|
**Action A**: We could change the order to match ISC DHCP
|
|
|
**Action A1**: We could change the order to match ISC DHCP
|
|
|
|
|
|
There are arguments in favor of going the way ISC DHCP with options precedence:
|
|
|
1. PRO: some people perceive client classes as more generic host reservations, almost like reservations with wildcards. ("I don't mean this Arris AG561 modem with MAC 01:02:03:04:05:06, I mean all all Arris AG561 modems").
|
... | ... | @@ -33,12 +33,19 @@ There are arguments in favor of going the way ISC DHCP with options precedence: |
|
|
|
|
|
1. CON: The obvious drawback is a change for Kea users. Although we warned them in 1.4 release notes that the precedence may change.
|
|
|
|
|
|
**Action B**: We could make the order configurable.
|
|
|
**Action A2**: We could keep the order as is.
|
|
|
|
|
|
1. PRO: No surprises when upgrading from existing Kea deployment.
|
|
|
|
|
|
2. CON: Unsolved problem of client classes options not being able to override shared network/subnet options.
|
|
|
|
|
|
**Action A3**: We could make the order configurable.
|
|
|
|
|
|
1. PRO: This would allow us to solve all the "but I want the class/pool/subnet options to be sent" requests.
|
|
|
|
|
|
1. CON: If misconfigured, there's a huge potential to shoot your own foot.
|
|
|
|
|
|
|
|
|
**Action C**: Develop a new hook with classes templates or dynamic classes. Kea doesn't have the ability to create classes on the fly. The idea is that user would define one or more templates, similar to flex-id expressions. It would be for classes what flex-id is for host identifiers. You take a fixed prefix and add a value of some option, e.g. you configure a DEVICE_VENDOR_ prefix and value of first 3 bytes of MAC address. A client sends a packet with MAC address 01:02:03:04:05:06, so the packet is assigned to class DEVICE_VENDOR_01_02_03. There would be one such definition and it would work for all 16 millions of possible values. This would be a rough equivalent to spawn client classes in isc dhcp, except we wouldn't create any long lasting objects in memory. This would be a great subscriber hook material.
|
|
|
|
|
|
**Action D**: _add your proposal here_
|
... | ... | |