NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Christian_R
Jul 16, 2021NETGEAR Employee Retired
RBK750 Series - Firmware Update v4.6.3.7
Hello Orbi AX Community,
We are excited to announce that we have started to roll out new firmware which enables NETGEAR Smart Parental Controls on RBK750 Systems. Customers with RBK750 series ...
Jktw
Sep 15, 2021Guide
Well, it appears that 4.6.3.16 has not resolved the stability and connectivity issues. My system auto updated to 4.6.3.16 and I reset my system. Things went well for about the first ten hours or so and then the issues related to stability and connectivity returned.
Not happy with NG at all. The previous version did not have any of these issues.
Mastra11
Sep 15, 2021Apprentice
What problems does it give you to you?
- JktwSep 15, 2021Guide
Devices lose connection to a satellite and then connect to the router with a poor connection and low speed. For example, Roku device was connected to Sat 1 great connection at 140 Mbps. It dropped from Sat 1 and connected to the router at 2Mbps.
With the previous FW, devices were connected pretty much equally across the router and satellites. Now most are connected to the router, a dozen or so to Sat 1 and 1 on Sat 2. This is a FW issue.
- Mastra11Sep 15, 2021Apprenticea ok but always does it?
- JlhardwickSep 15, 2021Star
Made 1 more attempt to factory reset and try again with the latest firmware. Since I needed to bring this up in parallel with an old router I'm using due this FW problem, I started with a different SSID. All started out ok and configured most of the settings. When it came time to bring down the old router and swap out with the Orbi I changed the SSID to match what I have been using all along and the problem started again with devices not being able to connect. No matter what I do most of my devices will not connect. This is the problem I have had since the original FW update and the current Beta/Release version is no different.
I have wasted hours of time on this and I give up...
- JktwSep 15, 2021Guide
yes, this has occurred with the two latest FW versions. This did not happen before these latest updates.
- raven_auSep 16, 2021Virtuoso
Jktw wrote:Devices lose connection to a satellite and then connect to the router with a poor connection and low speed. For example, Roku device was connected to Sat 1 great connection at 140 Mbps. It dropped from Sat 1 and connected to the router at 2Mbps.
With the previous FW, devices were connected pretty much equally across the router and satellites. Now most are connected to the router, a dozen or so to Sat 1 and 1 on Sat 2. This is a FW issue.
Yes, I do see similar behaviours but only on very few devices with the update.
But I also mostly see it with devices in poor locations relative to the routers and satelites.
And I have noticed there is an increased affinity to connecting to the main router.
But, so far, my impression is that the low bitrate associations occur when devices go into power save mode and don't ramp up bitrate quickly enough which looks like the diconnection problem we have previously seen.
So I think this is a seperate problem and I for one am happy to use a firmware that solves a serious problem now rather than wait until more problems are fixed.
The disconnection problem may well have been a wireless software development kit (SDK) problem for which netgear possibly had to go to the chip manufactures for a solution. So getting a fix this quickly is amazingly good becuase when they have to go to vendors themselves they will generally have much the same problems that we have in getting a problem recognised and then intergrating the updated SDK into the Orbi. More or less double development, double QA etc.
I have yet to do a factory default reset myself but, the wireless drivers have been updated, then it may made a difference and devices would probably need to forget the connection and reconnect to ensure they gat the best they can from that update.
The fact that a facory reset is recommended for the update makes me think this might be the case.