<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div><div>I've got this in my config file for the DHCPv4 server (using Kea 2.4.0:<br></div><div><br></div><div> "Dhcp4": {<br></div></div><div> "authoritative": true,<br></div><div> "valid-lifetime": 86400,<br></div><div> "reservations-global": false,<br></div><div> "reservations-in-subnet": true,<br></div><div> "reservations-out-of-pool": true,<br></div><div> "ip-reservations-unique": false,<br></div><div>...<br></div><div> "subnet4": [<br></div><div> {<br></div><div> "id": 88,<br></div><div> "subnet": "192.168.88.0/24",<br></div><div> "pools": [<br></div><div> {<br></div><div> "pool": "192.168.88.64/26"<br></div><div> },<br></div><div> {<br></div><div> "pool": "192.168.88.128/26"<br></div><div> }<br></div><div> ],<br></div><div> "reservations": [<br></div><div> {<br></div><div> "hw-address": "90:2e:16:d6:a4:1e",<br></div><div> "ip-address": "192.168.88.192",<br></div><div> "hostname": "balrog22",<br></div><div> "user-context": {<br></div><div> "name": "balrog22"<br></div><div> }<br></div><div> },<br></div><div> {<br></div><div> "hw-address": "a8:64:f1:30:88:0b",<br></div><div> "ip-address": "192.168.88.192",<br></div><div> "hostname": "balrog22",<br></div><div> "user-context": {<br></div><div> "name": "balrog22"<br></div><div> }<br></div><div> },<br></div><div>...<br></div><div><br></div><div>In theory this should result in my laptop getting the same IPv4 address whether it is connected to the wired or wireless networks (which are the same VLAN/subnet).<br></div><div><br></div><div>However, I see this in the log:<br></div><div><br></div><div>Oct 22 08:29:55 core23-a kea-dhcp4[1650]: WARN ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT [hwtype=1 90:2e:16:d6:a4:1e], cid=[00:81:74:fa:e6:94:98:99:8d:79:c0:a3:9c:87:27:72], tid=0x262eb546: conflicting reservation for address 192.168.88.192 with existing lease Address: 192.168.88.192<br></div><div>Oct 22 08:29:55 core23-a kea-dhcp4[1650]: Valid life: 86400<br></div><div>Oct 22 08:29:55 core23-a kea-dhcp4[1650]: Cltt: 1697977751<br></div><div>Oct 22 08:29:55 core23-a kea-dhcp4[1650]: Hardware addr: a8:64:f1:30:88:0b<br></div><div>Oct 22 08:29:55 core23-a kea-dhcp4[1650]: Client id: 01:a8:64:f1:30:88:0b<br></div><div>Oct 22 08:29:55 core23-a kea-dhcp4[1650]: Subnet ID: 88<br></div><div>Oct 22 08:29:55 core23-a kea-dhcp4[1650]: Pool ID: 0<br></div><div>Oct 22 08:29:55 core23-a kea-dhcp4[1650]: State: default<br></div><div>Oct 22 08:29:55 core23-a kea-dhcp4[1650]: Relay ID: (none)<br></div><div>Oct 22 08:29:55 core23-a kea-dhcp4[1650]: Remote ID: (none)<br></div><div>Oct 22 08:29:55 core23-a kea-dhcp4[1650]: INFO DHCP4_LEASE_ADVERT [hwtype=1 90:2e:16:d6:a4:1e], cid=[00:81:74:fa:e6:94:98:99:8d:79:c0:a3:9c:87:27:72], tid=0x262eb546: lease 192.168.88.64 will be advertised<br></div><div>Oct 22 08:29:55 core23-a kea-dhcp4[1650]: INFO DHCP4_LEASE_ALLOC [hwtype=1 90:2e:16:d6:a4:1e], cid=[00:81:74:fa:e6:94:98:99:8d:79:c0:a3:9c:87:27:72], tid=0x262eb546: lease 192.168.88.64 has been allocated for 86400 seconds<br></div><div><br></div><div>I'm running in the default multithreaded mode, so 'reservations-lookup-first' should be enabled (its default).<br></div><div><br></div><div>I must be missing something, as I believe I'm doing exactly what the ARM says I should do to have multiple reservations for the same IP address, but it's not working.<br></div><div><br></div></body></html>