NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBK50 firmware update bug messes up Orbi address
When you first use the app to install Orbi, Orbi sees that there is still an existing router and gives itself a non-conflicting address. Then it installs any firmware update, and then the problems b...
Well nobody else has reported something happening like this. I haven't seen anything like this either. I set up my friends 50 series last month and saw no IP address changes during FW updates. And I had to do a few. However his system is running in AP mode.
There will be some changing in IP addresses if you do have a Modem/router connected to the orbi system. If that modem/router uses 192.168.1.1 then it's possibe that the FW and or Setup wizard wil auto change the Orbi router to something different to avoid IP conflic as you can't have the same device using the same IP address.
Modem Combo Units:
Couple of options,
1. Configure the modem for transparent bridge mode. Then use the Orbi router in router mode.
2. If you can't bridge the modem, disable ALL wifi radios on the modem, configure the modems DMZ for the IP address the Orbi router gets from the modem. Then you can use the Orbi router in Router mode.
3. Or disable all wifi radios on the modem and connect the Orbi router to the modem, LAN to LAN and configure AP mode on the Orbi router.
If it's working, should be fine. Maybe next time, try a update using a wired PC connected to the router with a web browser instead of the mobile app.
Enjoy.
Just to clarify the conditions of the initial setup and F/W update, I turned the Google Fiber Wifi off before beginning setting up the Orbi. The Orbi must have initially connected correctly to the web and the satellite because both the Orbi and its satellite updated their F/W. Then the problems began because Orbi must have then switched to its default address which conflicted with the GF address. At that point it would not connect to the satellite and rebooting it did not help. Starting the setup over again fixed it. It has been working great since.
Yep, that would be the senario. Anyways, glad it's working now. Enjoy.