NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

AzJazz's avatar
AzJazz
Apprentice
Sep 11, 2017
Solved

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 resets. If I turn off my Orbi base before resetting my cable modem, there are no problems - this only occurs when the cable modem resets on its own, or my cable company loses signal to my modem.

 

The lost configuration issue I see is this: After the cable modem comes back up, I get limited connectivity on my home LAN, and a lot of websites are not accessible. If I try to go to the Orbi configuration pages, I continuously get prompted to re-enter my username and password (which always fails). Eventually, I will get prompted to enter my router serial number, and I get my password recovery questions. However, even after that, my provided username/password (which is the one I always enter) still gets rejected. A while after that, I will get a prompt that says that my Orbi base address was changed to 10.0.0.1 to prevent IP address conflicts. At this point (it's been about 20 minutes since starting), I can usually get to the configuration page to reconfigure back to the 192.168.1.1 address and DNS range.

 

I have had this problem for many months now, and Netgear hasn't fixed it with any firmware updates.

How do I get this issue elevated to get the Orbi firmware issue resolved? This could be a massive pain to customers who aren't tech savvy and can't even get to the internet because their Orbi gets messed up by this.

  •  

    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?

20 Replies

  •  

    What subnet are you using for your Orbi LAN?  For example, is it 192.168.100.X?

  • following on from what steve has asked above

     

    whats the make and model of the cable modem and do you know if its running in bridge modem or router mode ( i suspect router mode ) , the reason the orbi is changing to 10.0.0.1 is because its seeing an upsream dhcp server or router using the same default 192.168.1.1 address and its attempting to avoid ip conflicts

     

    having a router behind another router is not a good thing and is best to be avoided where possible

     

    not sure what other functions your cable modem provides ( eg tv , phone etc ) if any as the easiest way to avoid this is to run the orbi in AP mode and let your cable modem do all the routing and dhcp etc , if the cable modem has wifi also disable it

     

    --------------

     

    the alternative is to bridge your cable modem ( if possible ) and run the orbi as your main router and wifi

     

     

    ether of the above will solve your issue

    • st_shaw's avatar
      st_shaw
      Master

       

      Guys, here is what might be happening. Some cable modems, even when setup as a bridge, will give out a private IP when they lose connection with the cable company's network.  For example, some the COMCAST/Arris modems will give out IPs in the 192.168.100.X range.  If Orbi is using the same range for its LAN, then Orbi will automatically change the LAN IP range, and hose things up.

       

      Note that this will happen even if things are properly configured with the cable box in bridged mode and Orbi as a router.

       

      Also note that you cannot solve this by using AP mode, because the cable modem is not a router and will assign WAN IPs when things are working properly.

       

      The only way to prevent this would be to use a subnet on the Orbi LAN that's different from the one used by the cable modem when the modem cannot reach the cable company.

       

      This is a case of Orbi trying to be helpful and automatically avoiding problems, but thereby causing problems.

      • 192.168.100.xxx wouldnt be a problem though , the cable modem would need to be using 192.168.1.xxx , and if its using 192.168.1.1 its usually routing , again we wont really know till the OP posts his make and model of cable modem

         

        it depends on the cable modem as many are also routers

         

        but i do agree if it changes to 10.0.0.1 it should then not have issue after that