Update:
Im using the Circuit_ID as the client_id with the Flex Hook,
Sometimes, when a device requests a new IP address (different Mac, same
circuit_id) instead of handing out the address thats already in the lease
database, it hands a new one.
In the legal logging I can see the HW address and the circuit ID for the IP
address, however, it doesn’t enter either of those into the lease database..
So kea is handing out a lease with no MAC or Client ID associated to it in the
database..
Here’s what the lease looks like:
[
{
"arguments": {
"cltt": 1639150521,
"fqdn-fwd": false,
"fqdn-rev": false,
"hostname": "",
"hw-address": "",
"ip-address": “192.168.1.22",
"state": 1,
"subnet-id": 2,
"valid-lft": 86400
},
"result": 0,
"text": "IPv4 lease found."
}
]
But this is what I have in the legal logging table:
"Address: 192.168.1.22 has been assigned for 1 days 0 hrs 0 mins 0 secs to a
device with hardware address: hwtype=1 dc:4a:3e:93:16:a1, client-id:
00:37:38:38:61:32:30:66:63:33:62:62:38:2f:32:2f:62:34:66:62:65:34:65:62:62:33:30:31:2f:31:3a:31:32:31:32”
And when I look up the lease for that client-id:
[
{
"arguments": {
"leases": [
{
"client-id":
"00:37:38:38:61:32:30:66:63:33:62:62:38:2f:32:2f:62:34:66:62:65:34:65:62:62:33:30:31:2f:31:3a:31:32:31:32",
"cltt": 1639150531,
"fqdn-fwd": false,
"fqdn-rev": false,
"hostname": "desktop-lrv6t8s.",
"hw-address": "dc:4a:3e:93:16:a1",
"ip-address": “192.168.1.52",
"state": 0,
"subnet-id": 2,
"valid-lft": 86400
}
]
},
"result": 0,
"text": "1 IPv4 lease(s) found."
}
]
Its almost like kea hands out the IP address before it looks up if the
client-id already has a current lease..
Anyone have any ideas as to why this is happening or what I can do to fix it?
Thanks!
- Allan
> On Dec 10, 2021, at 8:58 AM, Allan Tinker <[email protected]> wrote:
>
> This morning I woke up to a whole /22 subnet with all the leases claimed,
> when I run get leases in the API,
> I have many leases with no hardware addresses or client ids.. (592 of them )
> Nothing to tell the server who gets what..
>
> Is there a way to A) not let clients with no MAC or Client ID to obtain a
> lease, and
> B) bulk remove these leases in IPv4?
>
> Currently Im removing them one by one.
> I still dont know the cause of this, but I want to prevent it by not allowing
> leases without client data at all.
>
> I am using the flex_id hook to swap circuit ID with client ID as well.
>
> Thank you
>
> - Allan
> _______________________________________________
> ISC funds the development of this software with paid support subscriptions.
> Contact us at https://www.isc.org/contact/ for more information.
>
> To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
>
> Kea-users mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/kea-users
_______________________________________________
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
