I am not sure if I read the screenshot well (the resolution or quality of lossy compression is low) and if I understand what you tried to report. However, you set DHCP pool beginning to 10.0.0.3 and the size to 256 addresses. This is really not possible in a network with /24 (255.255.255.0) mask and thus with 254 usable addresses.
I am not sure, however it is possible checks in Foris have been improved. Pool beginning at ...3 and pool size 255 leases does not make sense in /24 subnet.
The UI applies the whole page, not what you’ve changed, so if some settings were bad already, you can’t simply change others before fixing what’s wrong. There actually is a bug in Foris DHCP-range checks, but it is not affecting cases where netmask ends in zero (i.e. the bug affects almost noone).
Thank you @commar for testing this release in RC. Even in this time, we should help each other and I think I might be able to send you some small surprise as we appreciate any user who is trying to provide feedback about RC releases. I will send you PM and we will solve the rest there.
@commar I am sorry if my response sounds mean. I just wanted to point out what’s wrong and that it’s not an issue of the new release (and it turned out rather a fix in the new release).