This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
It appears that NG released the beta to production last night. When I checked this morning the router was updated to 4.6.3.16_2.0.51. I then reset the router and satellites. As of now, things are working well. Speeds are good and connectivity to all devices appears to be stable. The reset of the router and satellites appears to be a key step with this update.
About time! Can't wait to get home and see if mine was updated... Oddly, NG had reached out to me in the past few days about my issue being endorsed by L2 Technical Support - hopefully OBE now. Thanks!
Things change man. FW code, features, some things get out dated or removed, all kinds of crazy things. Specially when going from one major version to a different newer major version, like v3 to v4. I get it, should keep working thru FW updates but FW is faliible and not perfect. So resets are needed. Then make a new back up to file for use on the new version.
It appears that NG released the beta to production last night. When I checked this morning the router was updated to 4.6.3.16_2.0.51. I then reset the router and satellites. As of now, things are working well. Speeds are good and connectivity to all devices appears to be stable. The reset of the router and satellites appears to be a key step with this update.
Wait. I noticed my router rebooted overnight according to my 12 years old Debian Jessie v8 PC's dmesg (other devices got disconnected too):
...
[Tue Sep 14 01:26:53 2021] r8169 0000:04:00.0 eth0: link down [Tue Sep 14 01:27:00 2021] r8169 0000:04:00.0 eth0: link up [Tue Sep 14 01:27:00 2021] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [Tue Sep 14 01:27:15 2021] r8169 0000:04:00.0 eth0: link down [Tue Sep 14 01:27:17 2021] r8169 0000:04:00.0 eth0: link up [Tue Sep 14 01:27:29 2021] r8169 0000:04:00.0 eth0: link down [Tue Sep 14 01:27:31 2021] r8169 0000:04:00.0 eth0: link up
...
So, I got this even though I just checked for a newer firmware version a couple nights ago?
Let us know how it goes after a reset and setup from scratch. Hopefully won't see that. The disconnect may have been due to the auto update happening and which if the system does receive a auto update FW, the system WILL reboot and cause the disconnect during this time frame.
Just curious, What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Let us know how it goes after a reset and setup from scratch. Hopefully won't see that. The disconnect may have been due to the auto update happening and which if the system does receive a auto update FW, the system WILL reboot and cause the disconnect during this time frame...
I will deal with that reset and tedious reconfiguration when life quiets down unless the situation gets worsen. When did the newest firmware come out since I checked for it a few nights ago? I don't remember what was the last version I saw in my http://192.168.1.1. Is there a changelog? 😞
I updated to V4.6.3.16_2.0.51 and still have poor speed compared to the results provided by Ookla on the router (about 100 Mbps less), and basically a useless guest network, same as before the update. I haven't done a "reset" yet, but will try that and update shortly.
Hello, this morning I found myself automatically updated router and the two satellites to version 4.6.3.16_2.0.51 Why is there not on the Netgear site ?? Is a beta version automatically installed ?? Thanks for the replies! ORBI RBK753
Version 4.6.3.16 is there now and Netgear is not being totally transparent with thier release notes. According to the release notes the only things addresses were security and the speed test inaccuracy.
Hello, this morning I found myself automatically updated router and the two satellites to version 4.6.3.16_2.0.51 Why is there not on the Netgear site ?? Is a beta version automatically installed ?? Thanks for the replies! ORBI RBK753
Hello and thanks for the answer, now I have not yet restarted router and satellites, tomorrow if I can I try to restart router and satellites one at a time. But can you tell me what better this firmware than on the site there is? Thank you
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.
Be sure to power them OFF fully for 2 minutes then back ON.
@Mastra11 wrote: Hello and thanks for the answer, now I have not yet restarted router and satellites, tomorrow if I can I try to restart router and satellites one at a time. But can you tell me what better this firmware than on the site there is? Thank you
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.
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...
My experience with the V 16 upgrade is mixed and hard to understand.
As suggested, I powered off all my devices and let the nighthawk docsis modem sync up, and then repowered my main router, let it sync, then repowered the satellite.
I did not do a factory reset which the Netgear admin said was ok.
For about 10 hours, everything was great. Download speeds as measured by the Orbi app were back to 900 mb. Thruput - both wired and wireless was excellent: 600 on wired connections and 400-500 mb on wireless.
Suddenly the wireless thruput as measured on the speed test dropped to 10 - 20 mb. The hardwired speed test had not changed. The Orbi app still reported download for ~800/850 mb but there was just a trickle of data being pumped out of the system.
I have several wired devices (an Apple 4k streamer) connected to the satellite. They were stuttering and buffering all over the place.
I checked the modem and the connection, SNR, and power levels were all nominal. I do not think it was a provider issue.
I repowered the base station and the satellite - let everything sync up and now I'm back to 400 - 500 mb wireless.
Does anyone have any thoughts?
Last point: this was the behavior that the migration to version 4x initiated.
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.
