NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Firmware 2.2.1.210 released as of 10/3/18
New firmware is available via the GUI ....
Let's hope for success.
Hi,
I have an RBK50 (Router + Satellite) from our isp Ooredoo. its running firmware version V2.1.4.16_1.1.23.
when i use the gui to check for firmware update, it displays that "No new firmware version available. ". So i downloaded the v2.2 firmware manually for both satellite and router. I used the manual update option to update the satellite first but i get this error
"This firmware file is incorrect! Please get the firmware file again and make sure it is the correct firmware for this product."
i tried to update the router and get the same error.
any advice?
thanks
If your Orbi system is from yoru ISP, then you'll need to contact your ISP. NG makes the HW, however some times the FW is developed by ISPs for there systems like Verizon. They develop and update there own FW for the Orbi HW for there systems.
orbiRBK50 wrote:
Hi,
I have an RBK50 (Router + Satellite) from our isp Ooredoo. its running firmware version V2.1.4.16_1.1.23.
when i use the gui to check for firmware update, it displays that "No new firmware version available. ". So i downloaded the v2.2 firmware manually for both satellite and router. I used the manual update option to update the satellite first but i get this error
"This firmware file is incorrect! Please get the firmware file again and make sure it is the correct firmware for this product."
i tried to update the router and get the same error.
any advice?
thanks
- thank you for the reply
Slightly late to the feedback thread, but .210 is terrible. I have the RBR40 as router with wired backhaul to the RBS40 satellite, around 30-40 devices total including Windows and Macs, iphones and ipads, TP link and Belkin light switches, Lyric thermostat and leak detector, Tivos on ethernet and MoCa, Ring and Sharx cameras. The prior public release firmware was great.
After I installed .210 and restarted, the SB6141 cable modem decided that it needed to start doing DHCP. That gave a bunch of devices IP addresses outside the range the Orbi expected, and I started seeing the upstream server from Comcast as a device on my network. Power cycling everything seemed to convince the cable modem that the Orbi could be trusted to do DHCP duties, but then the Orbi stopped giving IP addresses to the Tivos (Roamio and Mini).
I poked around these groups and read that the daisy chain setting might be reversed and that changing it was fixing some problems for people. So I reversed mine, except it was already on and we all know now that disabling daisy chain causes a lot of problems. Fast forward through a couple of days of satellite misbehavior, grumpy family, with my evening hours spent power cycling and resyncing and backhaul cable checking and switch swapping and I finally stumble across the board post that says definitely enable daisy chaining. So I get back to square one.
(During this time I learned just how arbitrary the iOS app for Orbi is. Password not accepted, empty lists of devices, satellites not appearing on network map, device lists not remembering their filter settings, etc)
Now DHCP is working for the Tivos, but something has broken with the TPlink switches. The TPlink HS105 is the worst affected - it keeps assigning itself an IP address at random, despite having an address reservation. The Orbi logs don't even see a DHCP request from the HS105.
I've verified that the Orbi settings are the same as they were before the firmware update, I've got 20/40 coexistence on, MU-MIMO and fast roaming off, any other device in the same location as the switches gets full speed up or down (180 mbps down, 12 up).
Does anyone have any other ideas about how to get my light and power switches connected reliably again?
Thanks!