So reading your last logs closely, here what I've found: first discover from client 2019-07-11 11:06:16.294 DEBUG [kea-dhcp4.packets/33] DHCP4_QUERY_DATA [hwtype=1 00:50:56:95:5c:e5], cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29]
second discover 2019-07-11 11:06:23.805 DEBUG [kea-dhcp4.packets/33] DHCP4_QUERY_DATA [hwtype=1 00:50:56:95:5c:e5], cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c], according to manual, chapter 8.2.20 However, if the lease contains a "client identifier" which is different from the "client identifier" used by the client, the lease will be assumed to belong to another client and the new lease will be allocated. Default value of option "match-client-id" is "true" so when creating lease for the first DORA it still ctores client-id in lease record. So even if client has the same hwaddr in both requests, but cid is different and server decides that clients are different aswell. Placing in your global config Dhcp4 settings "match-client-id": false, will force the server to store leases without cid and only with hwaddr instead. After first ACK it will store lease and will match it second time because of hwaddr is the same and will offer second time the same IP as the first time. Good luck, hope it helps. -- Sent from: http://kea-users.7364.n8.nabble.com/ _______________________________________________ Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
