I'm setting up a new virtual owrt instance 24.10, by basically comparing it to the UI of my active R2S, which runs 23.05.
Where you set DHCP/static leases, if you enter an IP address that is outside of the dhcp pools, 24.10 complains "The ip address is outside of any DHCP pool address range". On my R2S this is/was no problem ?
Note this older discussion where the consensus appeared to endorse the 23.05 reasoning :
Am I overlooking something ? Otherwise I'll have to visit all my IoT and configure them manually again..
I think the error message appears when the static IP is outside of the subnets that dnsmasq manages, and not the "pools" that are used for automatic assignment (x.100-x.250 by default). For example, trying to set a static IP 10.0.4.1, when you only have a 10.0.3.0/24 subnet. All my static IPs are outside of those dynamic pools, but within the subnets.
Well then humor me : you probably did an inline upgrade to 24.10 or at least can you confirm you are on 24.10 ? Then kindly declare a static lease outside of one of your pools, but obviously within its subnet. We're just trying to make the UI trip, it doesn't have to be a real mac/ip map. Thanks
I have a device being upgrade since LEDE to 24.10.0 and one with a clean 24.10.0 and both exhibit the behavior I described. All of my static leases are outside of the dynamic pool, but within the subnets.
Perhaps you can share your configs, so we can see what's up.
I agree, though, the wording is a bit ambiguous, it is not immediately obvious what "DHCP pool address range" refers to. And even the DHCP options page could be a bit more clear that "Start" and "Limit" refers to the dynamic address pool.
Using that evidence I had a new look. On the new owrt I had disabled the dhcp server on that particulare vlan as I need the R2S to continu working and serve smartphones. In the iot vlan though I left it on because hell nobody will chase me there. And so those static leases DID work.
