... | @@ -4,10 +4,10 @@ This page documents status of client classification as of 1.5.0 (January 2019), |
... | @@ -4,10 +4,10 @@ This page documents status of client classification as of 1.5.0 (January 2019), |
|
|
|
|
|
1. Different options order between ISC DHCP and Kea. Kea uses host, pool, subnet, shared network, class, global precedence, while ISC DHCP uses host, class, pool, subnet, shared network, global.
|
|
1. Different options order between ISC DHCP and Kea. Kea uses host, pool, subnet, shared network, class, global precedence, while ISC DHCP uses host, class, pool, subnet, shared network, global.
|
|
1. Address the long lasting #39. This affects the last two failing DHCPv6 tests*
|
|
1. Address the long lasting #39. This affects the last two failing DHCPv6 tests*
|
|
1. We have require-client-classes and only-if-required. Those features are working, but it seems users are not taking advantage of it, because they're either too complex or not explained clearly.
|
|
1. We have require-client-classes and only-if-required. Those features are working, but it seems users are not taking advantage of it, because they're either too complex or not explained clearly. One problem here is that the choice of words is unfortunate. The "required" refers to "required to be evaluated" and not "required to access this subnet/pool".
|
|
1. @sgoldlust reported several doc sections that are unclear and confusing.
|
|
1. @sgoldlust reported several doc sections that are unclear and confusing.
|
|
1. it's tricky to select a subnet based on client classes. You can specify that only clients that belong to a certain client class can use the subnet. This was developed around 2014, years before we had shared networks and we had to support cable modems (and separate cable modems and the devices behind them to different subnets).
|
|
1. it's tricky to select a subnet based on client classes. You can specify that only clients that belong to a certain client class can use the subnet. This was developed around 2014, years before we had shared networks and we had to support cable modems (and separate cable modems and the devices behind them to different subnets).
|
|
1. With the increasing number of classes defined, kea performance drops. This can be mitigated with only-if-required flags.
|
|
1. With the increasing number of classes defined, kea performance drops. This can be mitigated with only-if-required flags. This, however, complicates the setup, because you need to specify in which subnets each class is required.
|
|
1. Kea doesn't have the ability to create classes on the fly. The idea is that 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.
|
|
1. Kea doesn't have the ability to create classes on the fly. The idea is that 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.
|
|
|
|
|
|
# Goals
|
|
# Goals
|
... | | ... | |