"
The KEA error log explains the address you chose for hifiberryamp is not available, as it's already in use, so instead it's advertised (offered) 192.168.30.101.
Static lease changes from ISC DHCP to KEA:
DHCP reservations must fall within the Interface subnet and must be outside any DHCP scope defined in KEA DHCP server.
This is a more strict configuration requirement than the legacy ISC DHCP Server.
Having static leases defined that fall within a scope does not prevent a DHCP server from offering that IP as a lease, which may (mistakenly) be the expected behaviour.
In your question you don't specify what your DHCP scope(s) [also known as pool(s)] is/are, so I'll assume you've left these as default which matches the interface's subnet.
This is an example of a CORRECT config:
And below is an example of a INCORRECT config:
If this doesn't work, can you confirm the scope(s) set for KEA on this interface
Static lease changes from ISC DHCP to KEA:
DHCP reservations must fall within the Interface subnet and must be outside any DHCP scope defined in KEA DHCP server.
This is a more strict configuration requirement than the legacy ISC DHCP Server.
Having static leases defined that fall within a scope does not prevent a DHCP server from offering that IP as a lease, which may (mistakenly) be the expected behaviour.
In your question you don't specify what your DHCP scope(s) [also known as pool(s)] is/are, so I'll assume you've left these as default which matches the interface's subnet.
This is an example of a CORRECT config:
Code Select
Interface subnet: 192.168.30.0/24
Interface Useable IPs: 192.168.30.1 - 192.168.30.254
Interface IP: 192.168.30.1/24
DHCP Scope: 192.168.30.1 - 192.168.30.180
DHCP static lease for mac address: d8:3a:dd:fc:44:82 192.168.30.182
And below is an example of a INCORRECT config:
Code Select
Interface subnet: 192.168.30.0/24
Interface Useable IPs: 192.168.30.1 - 192.168.30.254
Interface IP: 192.168.30.1/24
DHCP Scope: 192.168.30.1 - 192.168.30.254
DHCP static lease for mac address: d8:3a:dd:fc:44:82 192.168.30.182
If this doesn't work, can you confirm the scope(s) set for KEA on this interface
