@antinode wrote:
> Yes to reserve [an] IP address, it must be in the DHCP IP address
> range. Anything outside of the IP address pool range can be set for a
> STATIC IP address which is set ON devices, not the router.
Why? Around here (D7000[v1], V1.0.1.78_1.0.1), that would be
considered a firmware bug.
My DHCP pool range is ".224" - ".239". I have 23 address
reservations, all of which are outside the pool. I also have some
devices with static (ex-pool) addresses.
Obviously, there's no compelling reason for such a restriction.
Correct, I can't agree more: There is no reason for such a limitation. When I have it right, I complained about the limitation on the D7000 and some other subsequent Dxxxx Beta tests ... and it was changed accordingly on select products. Why ever, it never made it to the standard specs.
In my router and security appliance world this is the way most units work - we can add any address, regardless if inside or outside of the generic "free" DHCP pool, as a reserved MAC<->IP pair.
It's a question of specification, standardisation, and testing.
@antinode wrote:
> [...] Too bad the UI doesnt remind the user.
I'd say, "Too bad the (unspecified) firmware's defective."
It does not remind the user because the default DHCP poo is wide open (.2 ... .254 when I have it right) on Netgear routers - so the majority of users never hit this limitation.
I would expect the UI would allow enabling/disabling for IP<->MAC pairs already known (from the connected devices table) and adding reservation, regardess if these addresses are in the DHCP pool or not.
Correct UI behaviour would be to inform the user if the IP is outside of the pool, but allow continuing.
Needless to say, if the design does not allow IP addresses outside of the configured IP pool range, the user must be informed.
I'm fully with @bozojoe here.
@antinode All this was discussed and complained many times. Netgear's consumer router product management and development lost the contact to the reality out here in the market years ago already. Specs change randomly, UI behaviour does change randomly, there is no standardisation on product features (and even less on testing). Products are run under marketing numbers, generic features (outside of the latest and greatest WiFi and Mesh tech) as well as product continuity and standards don't count anymore.
