<div dir="ltr">I added the "host-reservation-identifiers": [ "hw-address" ], just before the subnet declarations like I saw in the Kea documentation and I'm still getting a non-reserved IP address.<div><br></div><div>I then did some digging into the lease file and logs and here's what I'm seeing:</div><div>The /var/lib/kea-leases4.csv before the change and after. The only changes are the subnet_id [from 2 [correct] to 1 [incorrect]] and the hostname:<br><font face="monospace">address,hwaddr,client_id,valid_lifetime,expire,subnet_id,fqdn_fwd,fqdn_rev,hostname,state,user_context,pool_id<br>192.168.11.118,c8:2a:14:45:53:24,01:c8:2a:14:45:53:24,28800,1722765662,2,1,1,<a href="http://mac-ubuntu-laptop-wired.totusmel.com">mac-ubuntu-laptop-wired.totusmel.com</a>,0,,0<br>192.168.10.227,c8:2a:14:45:53:24,01:c8:2a:14:45:53:24,28800,1722765662,1,1,1,<a href="http://ubuntu-system.totusmel.com">ubuntu-system.totusmel.com</a>,0,,0</font><br><br>The relevant lines from 04-dhcp_servers.11.json reservation file:<br><font face="monospace">{<br>  "hostname": "mac-ubuntu-laptop-wired",<br>  "hw-address": "c8:2a:14:45:53:24",<br>  "ip-address": "192.168.11.118"<br>},</font><br><br>Around 19:01 is when the config changed, around 19:06 is when it went back, I then switched back and forth a few times, but the same MAC address is referenced for every entry:<br>dhcp4-packets.log<br><font face="monospace">2024-08-03 19:01:02.461 INFO  [kea-dhcp4.packets/2455551.139122383521472] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xc485128a: DHCPREQUEST (type 3) received from 0.0.0.0 to 255.255.255.255 on interface eno2.11<br>2024-08-03 19:01:02.461 INFO  [kea-dhcp4.packets/2455551.139122394007232] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xc485128a: DHCPREQUEST (type 3) received from 0.0.0.0 to 255.255.255.255 on interface eno2<br>2024-08-03 19:01:02.462 INFO  [kea-dhcp4.packets/2455551.139122383521472] DHCP4_PACKET_SEND [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xc485128a: trying to send packet DHCPACK (type 5) from <a href="http://192.168.11.3:67">192.168.11.3:67</a> to <a href="http://192.168.11.118:68">192.168.11.118:68</a> on interface eno2.11<br>2024-08-03 19:01:02.462 INFO  [kea-dhcp4.packets/2455551.139122373035712] DHCP4_PACKET_SEND [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xc485128a: trying to send packet DHCPNAK (type 6) from <a href="http://192.168.10.3:67">192.168.10.3:67</a> to <a href="http://255.255.255.255:68">255.255.255.255:68</a> on interface eno2<br>2024-08-03 19:01:02.480 INFO  [kea-dhcp4.packets/2455551.139122362549952] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xae543e60: DHCPDISCOVER (type 1) received from 0.0.0.0 to 255.255.255.255 on interface eno2<br>2024-08-03 19:01:02.480 INFO  [kea-dhcp4.packets/2455551.139122394007232] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xae543e60: DHCPDISCOVER (type 1) received from 0.0.0.0 to 255.255.255.255 on interface eno2.11<br>2024-08-03 19:01:02.481 INFO  [kea-dhcp4.packets/2455551.139122362549952] DHCP4_PACKET_SEND [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xae543e60: trying to send packet DHCPOFFER (type 2) from <a href="http://192.168.10.3:67">192.168.10.3:67</a> to <a href="http://192.168.10.227:68">192.168.10.227:68</a> on interface eno2<br>2024-08-03 19:01:02.481 INFO  [kea-dhcp4.packets/2455551.139122383521472] DHCP4_PACKET_SEND [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xae543e60: trying to send packet DHCPOFFER (type 2) from <a href="http://192.168.11.3:67">192.168.11.3:67</a> to <a href="http://192.168.11.118:68">192.168.11.118:68</a> on interface eno2.11<br>2024-08-03 19:01:02.500 INFO  [kea-dhcp4.packets/2455551.139122394007232] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xae543e60: DHCPREQUEST (type 3) received from 0.0.0.0 to 255.255.255.255 on interface eno2.11<br>2024-08-03 19:01:02.500 INFO  [kea-dhcp4.packets/2455551.139122373035712] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xae543e60: DHCPREQUEST (type 3) received from 0.0.0.0 to 255.255.255.255 on interface eno2<br>2024-08-03 19:01:02.501 INFO  [kea-dhcp4.packets/2455551.139122373035712] DHCP4_PACKET_SEND [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xae543e60: trying to send packet DHCPACK (type 5) from <a href="http://192.168.10.3:67">192.168.10.3:67</a> to <a href="http://192.168.10.227:68">192.168.10.227:68</a> on interface eno2<br>2024-08-03 19:06:07.620 INFO  [kea-dhcp4.packets/2456561.131659187881664] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xca2112d4: DHCPREQUEST (type 3) received from 192.168.11.1 to 192.168.11.3 on interface eno2.11<br>2024-08-03 19:06:07.621 INFO  [kea-dhcp4.packets/2456561.131659156424384] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xca2112d4: DHCPREQUEST (type 3) received from 192.168.10.1 to 192.168.10.3 on interface eno2<br>2024-08-03 19:06:07.621 INFO  [kea-dhcp4.packets/2456561.131659177395904] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xca2112d4: DHCPREQUEST (type 3) received from 192.168.12.1 to 192.168.12.3 on interface eno2.12<br>2024-08-03 19:06:07.621 INFO  [kea-dhcp4.packets/2456561.131659187881664] DHCP4_PACKET_SEND [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xca2112d4: trying to send packet DHCPNAK (type 6) from <a href="http://192.168.11.3:67">192.168.11.3:67</a> to <a href="http://192.168.11.1:67">192.168.11.1:67</a> on interface eno2.11<br>2024-08-03 19:06:07.621 INFO  [kea-dhcp4.packets/2456561.131659156424384] DHCP4_PACKET_SEND [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xca2112d4: trying to send packet DHCPNAK (type 6) from <a href="http://192.168.10.3:67">192.168.10.3:67</a> to <a href="http://192.168.11.1:67">192.168.11.1:67</a> on interface eno2<br>2024-08-03 19:06:07.621 INFO  [kea-dhcp4.packets/2456561.131659166910144] DHCP4_PACKET_SEND [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xca2112d4: trying to send packet DHCPNAK (type 6) from <a href="http://192.168.12.3:67">192.168.12.3:67</a> to <a href="http://192.168.11.1:67">192.168.11.1:67</a> on interface eno2.12<br>2024-08-03 19:06:07.661 INFO  [kea-dhcp4.packets/2456561.131659187881664] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xa44870bc: DHCPDISCOVER (type 1) received from 192.168.12.1 to 192.168.12.3 on interface eno2.12<br>2024-08-03 19:06:07.661 INFO  [kea-dhcp4.packets/2456561.131659177395904] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xa44870bc: DHCPDISCOVER (type 1) received from 192.168.10.1 to 192.168.10.3 on interface eno2<br>2024-08-03 19:06:07.661 INFO  [kea-dhcp4.packets/2456561.131659156424384] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xa44870bc: DHCPDISCOVER (type 1) received from 192.168.11.1 to 192.168.11.3 on interface eno2.11<br>2024-08-03 19:06:07.662 INFO  [kea-dhcp4.packets/2456561.131659187881664] DHCP4_PACKET_SEND [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xa44870bc: trying to send packet DHCPOFFER (type 2) from <a href="http://192.168.12.3:67">192.168.12.3:67</a> to <a href="http://192.168.11.1:67">192.168.11.1:67</a> on interface eno2.12<br>2024-08-03 19:06:07.662 INFO  [kea-dhcp4.packets/2456561.131659166910144] DHCP4_PACKET_SEND [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xa44870bc: trying to send packet DHCPOFFER (type 2) from <a href="http://192.168.11.3:67">192.168.11.3:67</a> to <a href="http://192.168.11.1:67">192.168.11.1:67</a> on interface eno2.11<br>2024-08-03 19:06:10.621 INFO  [kea-dhcp4.packets/2456561.131659187881664] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: DHCPDISCOVER (type 1) received from 192.168.11.1 to 192.168.11.3 on interface eno2.11<br>2024-08-03 19:06:10.621 INFO  [kea-dhcp4.packets/2456561.131659156424384] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: DHCPDISCOVER (type 1) received from 192.168.12.1 to 192.168.12.3 on interface eno2.12<br>2024-08-03 19:06:10.621 INFO  [kea-dhcp4.packets/2456561.131659187881664] DHCP4_PACKET_SEND [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: trying to send packet DHCPOFFER (type 2) from <a href="http://192.168.11.3:67">192.168.11.3:67</a> to <a href="http://192.168.11.1:67">192.168.11.1:67</a> on interface eno2.11<br>2024-08-03 19:06:10.622 INFO  [kea-dhcp4.packets/2456561.131659177395904] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: DHCPDISCOVER (type 1) received from 192.168.10.1 to 192.168.10.3 on interface eno2<br>2024-08-03 19:06:10.622 INFO  [kea-dhcp4.packets/2456561.131659166910144] DHCP4_PACKET_SEND [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: trying to send packet DHCPOFFER (type 2) from <a href="http://192.168.12.3:67">192.168.12.3:67</a> to <a href="http://192.168.11.1:67">192.168.11.1:67</a> on interface eno2.12<br>2024-08-03 19:06:10.622 INFO  [kea-dhcp4.packets/2456561.131659156424384] DHCP4_PACKET_SEND [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: trying to send packet DHCPOFFER (type 2) from <a href="http://192.168.10.3:67">192.168.10.3:67</a> to <a href="http://192.168.11.1:67">192.168.11.1:67</a> on interface eno2<br>2024-08-03 19:06:10.661 INFO  [kea-dhcp4.packets/2456561.131659166910144] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: DHCPREQUEST (type 3) received from 192.168.12.1 to 192.168.12.3 on interface eno2.12<br>2024-08-03 19:06:10.661 INFO  [kea-dhcp4.packets/2456561.131659187881664] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: DHCPREQUEST (type 3) received from 192.168.11.1 to 192.168.11.3 on interface eno2.11<br>2024-08-03 19:06:10.661 INFO  [kea-dhcp4.packets/2456561.131659177395904] DHCP4_PACKET_RECEIVED [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: DHCPREQUEST (type 3) received from 192.168.10.1 to 192.168.10.3 on interface eno2<br>2024-08-03 19:06:10.662 INFO  [kea-dhcp4.packets/2456561.131659166910144] DHCP4_PACKET_SEND [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: trying to send packet DHCPACK (type 5) from <a href="http://192.168.12.3:67">192.168.12.3:67</a> to <a href="http://192.168.11.1:67">192.168.11.1:67</a> on interface eno2.12</font><br><br>dhcp4-leases.log<br><font face="monospace">2024-08-03 19:01:02.481 DEBUG [kea-dhcp4.leases/2455551.139122383521472] DHCP4_DISCOVER [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xae543e60: server is processing DHCPDISCOVER with hint=192.168.11.118<br>2024-08-03 19:01:02.481 INFO  [kea-dhcp4.leases/2455551.139122383521472] DHCP4_LEASE_OFFER [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xae543e60: lease 192.168.11.118 will be offered<br>2024-08-03 19:01:02.500 DEBUG [kea-dhcp4.leases/2455551.139122394007232] DHCP4_REQUEST [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xae543e60: server is processing DHCPREQUEST with hint=192.168.10.227<br>2024-08-03 19:01:02.500 DEBUG [kea-dhcp4.leases/2455551.139122373035712] DHCP4_REQUEST [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xae543e60: server is processing DHCPREQUEST with hint=192.168.10.227<br>2024-08-03 19:01:02.500 INFO  [kea-dhcp4.leases/2455551.139122373035712] DHCP4_LEASE_ALLOC [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xae543e60: lease 192.168.10.227 has been allocated for 28800 seconds<br>2024-08-03 19:06:07.620 INFO  [kea-dhcp4.leases/2456561.131659187881664] DHCP4_INIT_REBOOT [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xca2112d4: client is in INIT-REBOOT state and requests address 192.168.10.227<br>2024-08-03 19:06:07.621 INFO  [kea-dhcp4.leases/2456561.131659156424384] DHCP4_INIT_REBOOT [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xca2112d4: client is in INIT-REBOOT state and requests address 192.168.10.227<br>2024-08-03 19:06:07.621 INFO  [kea-dhcp4.leases/2456561.131659166910144] DHCP4_INIT_REBOOT [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xca2112d4: client is in INIT-REBOOT state and requests address 192.168.10.227<br>2024-08-03 19:06:07.661 DEBUG [kea-dhcp4.leases/2456561.131659187881664] DHCP4_DISCOVER [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xa44870bc: server is processing DHCPDISCOVER with hint=192.168.10.227<br>2024-08-03 19:06:07.662 INFO  [kea-dhcp4.leases/2456561.131659187881664] DHCP4_LEASE_OFFER [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xa44870bc: lease 192.168.11.118 will be offered<br>2024-08-03 19:06:07.662 DEBUG [kea-dhcp4.leases/2456561.131659166910144] DHCP4_DISCOVER [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xa44870bc: server is processing DHCPDISCOVER with hint=192.168.10.227<br>2024-08-03 19:06:07.662 INFO  [kea-dhcp4.leases/2456561.131659166910144] DHCP4_LEASE_OFFER [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0xa44870bc: lease 192.168.11.118 will be offered<br>2024-08-03 19:06:10.621 DEBUG [kea-dhcp4.leases/2456561.131659187881664] DHCP4_DISCOVER [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: server is processing DHCPDISCOVER with hint=192.168.10.227<br>2024-08-03 19:06:10.621 INFO  [kea-dhcp4.leases/2456561.131659187881664] DHCP4_LEASE_OFFER [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: lease 192.168.11.118 will be offered<br>2024-08-03 19:06:10.622 DEBUG [kea-dhcp4.leases/2456561.131659166910144] DHCP4_DISCOVER [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: server is processing DHCPDISCOVER with hint=192.168.10.227<br>2024-08-03 19:06:10.622 INFO  [kea-dhcp4.leases/2456561.131659166910144] DHCP4_LEASE_OFFER [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: lease 192.168.11.118 will be offered<br>2024-08-03 19:06:10.622 DEBUG [kea-dhcp4.leases/2456561.131659156424384] DHCP4_DISCOVER [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: server is processing DHCPDISCOVER with hint=192.168.10.227<br>2024-08-03 19:06:10.622 INFO  [kea-dhcp4.leases/2456561.131659156424384] DHCP4_LEASE_OFFER [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: lease 192.168.11.118 will be offered<br>2024-08-03 19:06:10.661 DEBUG [kea-dhcp4.leases/2456561.131659166910144] DHCP4_REQUEST [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: server is processing DHCPREQUEST with hint=192.168.11.118<br>2024-08-03 19:06:10.661 INFO  [kea-dhcp4.leases/2456561.131659166910144] DHCP4_LEASE_ALLOC [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: lease 192.168.11.118 has been allocated for 28800 seconds<br>2024-08-03 19:06:10.662 DEBUG [kea-dhcp4.leases/2456561.131659156424384] DHCP4_REQUEST [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: server is processing DHCPREQUEST with hint=192.168.11.118<br>2024-08-03 19:06:10.662 INFO  [kea-dhcp4.leases/2456561.131659156424384] DHCP4_LEASE_ALLOC [hwtype=1 c8:2a:14:45:53:24], cid=[01:c8:2a:14:45:53:24], tid=0x893a4ca9: lease 192.168.11.118 has been allocated for 28800 seconds</font><br><br>Both the WiFi and ethernet MAC are returning when I arping the system I've been testing with?<br><font face="monospace">root@cube:/var/lib/kea# arping -c 6 <a href="http://mac-ubuntu-laptop-wired.totusmel.com">mac-ubuntu-laptop-wired.totusmel.com</a><br>ARPING 192.168.11.118<br>60 bytes from c8:2a:14:45:53:24 (192.168.11.118): index=0 time=373.545 usec<br>56 bytes from e4:ce:8f:28:9e:24 (192.168.11.118): index=1 time=40.527 msec<br>60 bytes from c8:2a:14:45:53:24 (192.168.11.118): index=2 time=303.398 usec<br>56 bytes from e4:ce:8f:28:9e:24 (192.168.11.118): index=3 time=268.226 msec<br>60 bytes from c8:2a:14:45:53:24 (192.168.11.118): index=4 time=966.349 usec<br>60 bytes from c8:2a:14:45:53:24 (192.168.11.118): index=5 time=509.973 usec<br>56 bytes from e4:ce:8f:28:9e:24 (192.168.11.118): index=6 time=130.663 msec<br>60 bytes from c8:2a:14:45:53:24 (192.168.11.118): index=7 time=241.655 usec<br>56 bytes from e4:ce:8f:28:9e:24 (192.168.11.118): index=8 time=50.869 msec<br>60 bytes from c8:2a:14:45:53:24 (192.168.11.118): index=9 time=532.040 usec<br>56 bytes from e4:ce:8f:28:9e:24 (192.168.11.118): index=10 time=278.733 msec<br><br>--- 192.168.11.118 statistics ---<br>6 packets transmitted, 11 packets received,   0% unanswered (5 extra)<br>rtt min/avg/max/std-dev = 0.242/70.177/278.733/103.031 ms</font><br><br>arping another system but only getting one MAC address back:<br><font face="monospace">root@cube:/etc/kea# arping -c 6 <a href="http://ubence-mini-wired.totusmel.com">ubence-mini-wired.totusmel.com</a><br>ARPING 192.168.11.45<br>60 bytes from 4c:20:b8:ab:1b:eb (192.168.11.45): index=0 time=365.985 usec<br>60 bytes from 4c:20:b8:ab:1b:eb (192.168.11.45): index=1 time=422.983 usec<br>60 bytes from 4c:20:b8:ab:1b:eb (192.168.11.45): index=2 time=369.058 usec<br>60 bytes from 4c:20:b8:ab:1b:eb (192.168.11.45): index=3 time=416.778 usec<br>60 bytes from 4c:20:b8:ab:1b:eb (192.168.11.45): index=4 time=428.881 usec<br>60 bytes from 4c:20:b8:ab:1b:eb (192.168.11.45): index=5 time=310.630 usec<br><br>--- 192.168.11.45 statistics ---<br>6 packets transmitted, 6 packets received,   0% unanswered (0 extra)<br>rtt min/avg/max/std-dev = 0.311/0.386/0.429/0.042 ms</font><br></div><div><br></div><div>I can't seem to arping by MAC address reliably and I'm not sure why.</div><div><br></div><div>Any other suggestions?<br></div><div><br></div><div>-Ubence</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Aug 3, 2024 at 6:55 PM Sonic <<a href="mailto:sonicsmith@gmail.com">sonicsmith@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Looks like you don't really need that, although if the hw-address is<br>
the only thing you use to identify reservations then it's best to have<br>
it and eliminate all other checks.<br>
Are you double checking the logs to verify that the mac addresses of<br>
the devices getting pool addresses match the hw-addresses in your<br>
reservation statements?<br>
Are you sure the reserved addresses in question are not in use (will<br>
not answer an arping)?<br>
-- <br>
ISC funds the development of this software with paid support subscriptions. Contact us at <a href="https://www.isc.org/contact/" rel="noreferrer" target="_blank">https://www.isc.org/contact/</a> for more information.<br>
<br>
To unsubscribe visit <a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a>.<br>
<br>
Kea-users mailing list<br>
<a href="mailto:Kea-users@lists.isc.org" target="_blank">Kea-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a><br>
</blockquote></div>