NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AzJazz
Sep 11, 2017Apprentice
Orbi always loses configuration after cable modem reset
Hi - I have a Orbi RBR50 and one RBS50. My firmware version is V1.12.0.18 I have always had a problem where my Orbi base unit will lose its configuration information every time my cable modem res...
- Sep 12, 2017
Your cable modem is hardwired with an IP address of 192.168.100.1. This is described in the manual here: http://www.downloads.netgear.com/files/GDC/CM400/CM400_UM_17July2015.pdf
With your Orbi setup to use a LAN IP of 192.168.1.1 and a subnet mask of 255.255.0.0 you have included the address space used by the modem in you LAN and created a conflict between the Orbi LAN and the cable modem's IP address. I'm not certain what's happening exactly, but it's very likely this is the source of your issue with Orbi sensing a conflict and resetting the LAN to 10.0.0.1.
You should change your Orbi LAN subnet to something different, like 172.16.X.X.
I'm curious. Why are you using 255.255.0.0? What are you doing that you need 65534 IP addresses on your LAN?
AzJazz
Sep 12, 2017Apprentice
st_shaw wrote:AzJazz Do you really mean your subnet mask is: 255.255.0.0? If it is, I would suggest you change it to 255.255.255.0.
Yes, the subnet mask of 255.255.0.0 is intentional. I could trim that down to 255.240.0.0, but then it gets a bit messy with configuring devices on the LAN.
st_shaw
Sep 12, 2017Master
Your cable modem is hardwired with an IP address of 192.168.100.1. This is described in the manual here: http://www.downloads.netgear.com/files/GDC/CM400/CM400_UM_17July2015.pdf
With your Orbi setup to use a LAN IP of 192.168.1.1 and a subnet mask of 255.255.0.0 you have included the address space used by the modem in you LAN and created a conflict between the Orbi LAN and the cable modem's IP address. I'm not certain what's happening exactly, but it's very likely this is the source of your issue with Orbi sensing a conflict and resetting the LAN to 10.0.0.1.
You should change your Orbi LAN subnet to something different, like 172.16.X.X.
I'm curious. Why are you using 255.255.0.0? What are you doing that you need 65534 IP addresses on your LAN?
- st_shawSep 12, 2017Master
Ok. So you could change your servers to 172.16.2.1 and 172.16.10.1.
What does that address scheme do that you can't do with both servers under a single /24 address space?
- AzJazzSep 12, 2017Apprentice
st_shaw wrote:Ok. So you could change your servers to 172.16.2.1 and 172.16.10.1.
What does that address scheme do that you can't do with both servers under a single /24 address space?
st_shaw - Thanks, I wasn't familiar with the 172.16.x.x through 172.31.x.x range. I'll give it a shot.
But ... When I tried to set that up with my Orbi, but I wasn't able to adjust the first three octets of the DNS server IP address. The first three octets were grayed-out and unmodifiable.
- st_shawSep 12, 2017Master
I'm not really sure what you are saying.
The DNS settings are located in the Internet (WAN) settings part of the router GUI.
Changing the LAN to 172.16.X.X. is located in the LAN settings part of the router GUI.
One setting should have no impact on the other.
- AzJazzSep 12, 2017Apprentice
st_shaw wrote:I'm not really sure what you are saying.
The DNS settings are located in the Internet (WAN) settings part of the router GUI.
Changing the LAN to 172.16.X.X. is located in the LAN settings part of the router GUI.
One setting should have no impact on the other.
It was a glitch in the Orbi firmware. For some reason, changing the Orbi base IP address was not changing the DHCP Server IP address range to match, which it should have been changing. As a result, I was getting a pop-up error from the Orbi that the Orbi base IP address wasn't in the DHCP range.
After I got out of the Orbi Setup pages and got back in, the DHCP Server octets were changing to match as I modified my Orbi base IP address.
I've seen this happen with the Orbi before, but very rarely.I have started reconfiguring my network to the 172.16.xx.xx range.
- st_shawSep 12, 2017Master
OK. I hope it works for you.
- AzJazzSep 16, 2017Apprentice
st_shaw wrote:Your cable modem is hardwired with an IP address of 192.168.100.1. This is described in the manual here: http://www.downloads.netgear.com/files/GDC/CM400/CM400_UM_17July2015.pdf
With your Orbi setup to use a LAN IP of 192.168.1.1 and a subnet mask of 255.255.0.0 you have included the address space used by the modem in you LAN and created a conflict between the Orbi LAN and the cable modem's IP address. I'm not certain what's happening exactly, but it's very likely this is the source of your issue with Orbi sensing a conflict and resetting the LAN to 10.0.0.1.
You should change your Orbi LAN subnet to something different, like 172.16.X.X.
Thanks, st_shaw - I've used the 172.16.xx.xx range for a few days now, and forced quite a few cable modem resets (without powering off my Orbi). The Orbi seems to be keeping its configuration settings without getting messed up anymore. I'm glad you told me about this, and your theory that the 192.168.100.1 IP address of the cable modem confusing the Orbi seems valid.
That said ... It seems like there is still a bug in the Orbi firmware that causes this to occur. I have had at least a half-dozen different WiFi routers (some of them by Netgear) connected to the same or similar cable modems with a 192.168.100.1 fixed IP address, and I have never run into the lost configuration settings or router IP address reassignment that I have seen with the Orbi. The Orbi is getting confused where no other WiFi router has.
I don't know what it would take to get this raised as an issue with Netgear to get a firmware fix implemented.
Thanks again for the great help!AzJazz
- st_shawSep 16, 2017Master
I'm happy to hear this solved your problem. Regarding a possible bug... I don't believe it's a bug. It's a feature and Orbi is operating as designed. The issue occurred because you initially set your LAN subnet to encompass the IP range used by your modem. The reason you haven't seen the behavior with other routers is because they do not have the feature of detecting a conflict between the WAN and LAN. I think you have demonstrated that the feature can have some unintended consequences though, and perhaps the feature causes more trouble than it saves.
- peteytestingSep 16, 2017Hero
hi
most modern routers now have the ip conflict resolution , its pretty standard and needed in what are complex systems some have these days