NetGear Router | WAN / LAN IP Conflict issue

(sigh) yet another instance where access to the source code would lead almost immediately to the source of the problem.

It might be interesting to see if the choice of IP subnet has any effect on this.  i.e. rather than set the router to use 10.0.0.x, pick some other IP subnet, such as the traditional 192.168.1.x  Something is triggering the router firmware to this invalid conclusion and unfortunate acction.

As a side note, people on the Forum have different methods to approach the concept of IP addresses in the defined subnet.  There are three types of address assignments:

• Static: where the IP address is set on the device, rather than on the router. The device never issues a DHCP request.
• Reserved: where the router maintains a list of MAC addresses and the IP address that should be given to each when it makes a DHCP request.
• Pool: a set of IP addresses that are randomly given out to devices that make requests and do not appear in the reserved list.

My personal practice is to divide the IP subnet into three contiguous sets:

• One set of IP addresses that are used for Reserved devices.
• One set of IP addresses that are used for the 'pool'.
• One set of IP addresses that are NEVER used for DHCP, and thus available for use by devices set with Static IPs.

My setup is

• IPs 192.168.1.2 through 192.168.1.100 are used for 'reserved' devices.  The LAN setup table is used to record the MAC address of devices I want to manage and the IP address to assign to each of them. 
• IPs 192.168.1.101 through 192.168.199 are used for the 'pool'.  Any device that makes a DHCP request and is not in the assignment table gets an IP from this pool. 
• IPs 192.168.201 through 192.168.1.154 are not defined as far as DHCP is concerned.  The router will NEVER issue an IP address in this range to any device.  (I actually have zero devices with Static IPs, but might occasionally set one up for an experiment.)