NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New - RBK752/753 Firmware Version 4.6.3.7 Released
Security Fixes: Fixes security vulnerabilities. For more information about security vulnerabilities, visit https://www.netgear.com/about/security. New Features and Enhancements: Supports Smart...
***Updated: 9/13/2021 11:50 AM PT
Hello Orbi Community,
Please accept my apologies for any delay in getting this message to you. I have been advised that an official firmware release is in the final stages of internal testing and in the process of being posted to our support site. Likely, within the next 24 hours.
To get this firmware release now please click the link below:
For instructions on how to manually download this firmware please visit:
How do I manually upgrade firmware on my Orbi router using orbilogin.com?
Thank you for your patience,
ChristineT
Thanks for letting us know. Let us know how it goes later on down the road.
First experience with the 4.6.3.16 beta fw is that the issues are not gone. I think it has improved a little bit but definetely this device disconnects keep happening all the time...(I did switch on the AX Features again after the update to the Beta FW)
Personally i think most of the issues are DHCP related, i have no configured some devices that disconnect often, to static. Lets see how that goes.
- I noticed that too. The router cannot release the IP, or keeps it in memory too long. Is there a way to release it faster?
Has a factory reset on the RBR and RBS been performed, then power OFF of the RBR and RBS with pulling the power adapters for a good 5 minutes, then back ON then walk thru the setup wizard been performed since you applied the beta FW?
Berryvl wrote:
First experience with the 4.6.3.16 beta fw is that the issues are not gone. I think it has improved a little bit but definetely this device disconnects keep happening all the time...(I did switch on the AX Features again after the update to the Beta FW)
Personally i think most of the issues are DHCP related, i have no configured some devices that disconnect often, to static. Lets see how that goes.
Of course not.. This was also not adviced by NG Support.
I understand that doing this is something that 'could' work or solve the issue but lets be honest. To do this it takes me another 1-2 hrs (because i don't think restoring a backup is wise at that point as well?). Also, I already spent hours fighting this issue and It is not normal, nor should it be required that with every fw update you have to go through a factory reset, why would there be an 'upgrade firmware' option to begin with. If there is a confirmed bug in the fw, and the bug is solved in the source code of a newer version then a factory reset should not be needed. I don't think your aim is to keep us busy while NG solves the bug.. but it is just too much to ask. If NG can guarantee that if I do factory reset all will be good, I will of course (reluctantly) do it :)
Nevertheless I understand you want to help, and it is appreciated.
FURRYe38 wrote:Has a factory reset on the RBR and RBS been performed, then power OFF of the RBR and RBS with pulling the power adapters for a good 5 minutes, then back ON then walk thru the setup wizard been performed since you applied the beta FW?
Berryvl wrote:First experience with the 4.6.3.16 beta fw is that the issues are not gone. I think it has improved a little bit but definetely this device disconnects keep happening all the time...(I did switch on the AX Features again after the update to the Beta FW)
Personally i think most of the issues are DHCP related, i have no configured some devices that disconnect often, to static. Lets see how that goes.
OK then your choice of course. Seen many issues resolved by a reset as setup from scratch. One should be saving a backup configuration to file for safe keeping which ALSO saves time when and if a factory reset is performed. Resets are a valid troubleshooting step and due to the nature of FW updates and such, they should be employed to help narrow down issues and ensure there is a good seating of the FW and configuration is clean. There maybe some incompatibilities causing problems from prior versions loaded that may cause problems. So resets do help in this area. We can't catagorize continued problems unless a reset has been done as well. Understand the frustrations as well. I would recommend a full power OFF of the RBR and RBS for at least 1 minute or more then back ON to see if anything changes. I found that this helped my system and has been stable since.
Good Luck.
There is no discussion wether or not going through a reset is a valid troubleshooting step, of course it is. And yes it really is frustrating, and Yes I really hoped the issue would have been identified and the new fw would solve it without the pain of a full reset. But the reality can be different. Since the issue is not resolved and I don't expect a new beta everyday I just migh go through another reset. btw, i did power everything off for a few minutes after the beta fw update.
Thanks again for your continued effort to help.
FURRYe38 wrote:
OK then your choice of course. Seen many issues resolved by a reset as setup from scratch. One should be saving a backup configuration to file for safe keeping which ALSO saves time when and if a factory reset is performed. Resets are a valid troubleshooting step and due to the nature of FW updates and such, they should be employed to help narrow down issues and ensure there is a good seating of the FW and configuration is clean. There maybe some incompatibilities causing problems from prior versions loaded that may cause problems. So resets do help in this area. Understand the frustrations as well. I would recommend a full power OFF of the RBR and RBS for at least 1 minute or more then back ON to see if anything changes. I found that this helped my system and has been stable since.
Good Luck.
Since the issue is not solved in the beta, then a reset would be needed to check this. Just saying.
Berryvl wrote:
There is no discussion wether or not going through a reset is a valid troubleshooting step, of course it is. And yes it really is frustrating, and Yes I really hoped the issue would have been identified and the new fw would solve it without the pain of a full reset. But the reality can be different. Since the issue is not resolved and I don't expect a new beta everyday I just migh go through another reset. btw, i did power everything off for a few minutes after the beta fw update.
Thanks again for your continued effort to help.
@
