NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
The IP address conflicts with the WAN IP subnet. Please enter a different IP address.
Note that the "asspciated Products" field refused to take any version of my actual product name or model number. I ended up entering "netgear" and selecting the first choice out of a total of two ch...
I do not have any ISP-provided hardware. I own the cable modem and I own the one and only router. The only thing the ISP provides is the wire connected to my home.
You suggested changing the subnet mask to 255.255.255.0. I can see this is going to get messy right away. It already is 255.255.255.0. The subnet mask you might be referring to, which is stated as 255.255.240.0 in my initial writeup seems to be the subnet of the ISP-provided public IP address (the IP that shows up if I go to whatismyipaddress.com). I have no way of modifying that subnet. It seems to be totally separate and unrelated to the subnet mask that is listed with my router's internal IP address of 192.168.1.1 (this has been my router's internal address for decades, along with my subnet mask of 255.255.255.0).
MY ROUTER, on the other hand, is at 192.168.1.1 with its own subnet of 255.255.255.0. It doesn't matter whether I set this internal subnet mask to the 255.255.240.0 subnet to match that of the ISP. As for changing my router IP to 192.168.0.1, I've tried that, and it doesn't fix the issue.
Any progress on this?
RL5000 wrote:
I do not have any ISP-provided hardware. I own the cable modem and I own the one and only router. The only thing the ISP provides is the wire connected to my home.
You suggested changing the subnet mask to 255.255.255.0. I can see this is going to get messy right away. It already is 255.255.255.0. The subnet mask you might be referring to, which is stated as 255.255.240.0 in my initial writeup seems to be the subnet of the ISP-provided public IP address (the IP that shows up if I go to whatismyipaddress.com). I have no way of modifying that subnet. It seems to be totally separate and unrelated to the subnet mask that is listed with my router's internal IP address of 192.168.1.1 (this has been my router's internal address for decades, along with my subnet mask of 255.255.255.0).
MY ROUTER, on the other hand, is at 192.168.1.1 with its own subnet of 255.255.255.0. It doesn't matter whether I set this internal subnet mask to the 255.255.240.0 subnet to match that of the ISP. As for changing my router IP to 192.168.0.1, I've tried that, and it doesn't fix the issue.