I configure my network with an IP Subnet Mask of 255.255.254.0 (NOT 255.255.255.0) as I have enough devices to merit the 512-IP space.
If I want to use the Router as a DHCP server, it does not respect my subnet, only allows me to provide a starting and ending IP with the final field blank.
My is 192.168.86.1, so the UI only allows DHCP of 192.168.86.x to 192.168.86.y, no allowing me to specify 87.
I even tried 255.255.0.0 for kicks, no dice.
Looks like the UI is hardcoded to only allow the 256-value range, not Subnet Mask-driven range.
Can anyone else confirm this bug?
Can anyone from Netgear confirm it's either a bug or functioning as (poorly) designed?
> [...] I have enough devices to merit the 512-IP space.
Perhaps, but you may not have enough router to handle that many.
> If I want to use the Router as a DHCP server, it does not respect my > subnet, only allows me to provide a starting and ending IP with the > final field blank.
A design limitation, I'd guess, for a consumer-grade router. I'd expect trouble with more than just DHCP. NAT, for example. I'd also worry about performance with more than 250 client devices. (Safe bet it wasn't tested that way.)
> Looks like the UI is hardcoded to only allow the 256-value range, not > Subnet Mask-driven range.
Did you also try a _more_ restrictive subnet mask? It might be "hardcoded" on one side, only.
