Currently, when adding a reservation, it must be part of the address range for the scope.
This seems like an unnecessary limitation.
I understand that it needs to be in the same subnet, but OpenWRT (for example) allows the reservation to be any IP.
In my case, I now have Technitium DNS/DHCP servers running on two Raspberry Pi 4's and would like to have non-overlapping DHCP scopes but with shared reservations for some systems (e.g. printer) on my network.
While I'm here. For the user-interface, I think the reservation entries should "lock" the subnet part of the IP address - although I realise that could get tricky if someone is using an 'odd' subnet boundary.
Currently, when adding a reservation, it must be part of the address range for the scope.
This seems like an unnecessary limitation.
I understand that it needs to be in the same subnet, but OpenWRT (for example) allows the reservation to be any IP.
In my case, I now have Technitium DNS/DHCP servers running on two Raspberry Pi 4's and would like to have non-overlapping DHCP scopes but with shared reservations for some systems (e.g. printer) on my network.
While I'm here. For the user-interface, I think the reservation entries should "lock" the subnet part of the IP address - although I realise that could get tricky if someone is using an 'odd' subnet boundary.