NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FURRYe38
Jul 06, 2020Guru - Experienced User
New Orbi 50 series Firmware Version 2.5.1.32 FW Release
RBR50, RBS50, RBK50, and RBK53 New Features and Enhancements: Improves the NTP sync speed and success rate Includes updates to the Terms and Conditions and adds a Privacy Policy link Bug Fix...
Lyth
Jul 18, 2020Guide
I updated 2 days ago and have no apparent issues with performance or connectivity so that's good. I did have to reconnect my alarm system manually tho, it didn't just reconnect on its own. I have also noticed that the log no longer shows DHCP requests at all now or when a device connects via WiFi. It also doesn't seem to retain any information beyond 24 hours either.
FURRYe38
Jul 21, 2020Guru - Experienced User
FYI, I got word from NG that v32 has been pullfed or the 50 series Orbi systems. NG feels that there were problems they found that needs to be resolved.
I recommend users load v16. That version worked well for me at least. if you have v32 loaded and don't experience any problems, keep it loaded. IF you are experiencing problems, revert back to v16.
- jhoff909Jul 22, 2020Apprentice
Any idea what the issues were / are?
- FURRYe38Jul 22, 2020Guru - Experienced User
No details on why it was pulled.
I did notice one thing, the RBR reported my RBS as wirelessly connected instead of wired which it was wired connected. I checked everything I could tell the connection was wired as I connected my phone to the RBS and saw data flow going thru the wired connection to the switch the RBS was connected too. The RBS showed that the wireless connection was grayed out as well. But the RBRs status page showed wireless. So I reverted back to v16 and it's now reporting correctly.
jhoff909 wrote:Any idea what the issues were / are?
- clammerdsJul 22, 2020Apprentice
FURRYe38 wrote:FYI, I got word from NG that v32 has been pullfed or the 50 series Orbi systems. NG feels that there were problems they found that needs to be resolved.
I recommend users load v16. That version worked well for me at least. if you have v32 loaded and don't experience any problems, keep it loaded. IF you are experiencing problems, revert back to v16.
Good to know. I have to admit, I have v32 installed and for me at least, it's been rock solid. Will leave as is for now. Will be interested to know what it is that's made NG pulli it. Obviously, if it's security reasons, I'll have to reconsider keeping it.
thanks
- FURRYe38Jul 22, 2020Guru - Experienced User
IF it works for now. let it run. If you notice anything, concider reverting. I did see one problem with status not reporting correctly for a ethernet connected RBS. Other wise, it seemed to work ok for me. I've since downgraded back to v16.
clammerds wrote:
FURRYe38 wrote:FYI, I got word from NG that v32 has been pullfed or the 50 series Orbi systems. NG feels that there were problems they found that needs to be resolved.
I recommend users load v16. That version worked well for me at least. if you have v32 loaded and don't experience any problems, keep it loaded. IF you are experiencing problems, revert back to v16.
Good to know. I have to admit, I have v32 installed and for me at least, it's been rock solid. Will leave as is for now. Will be interested to know what it is that's made NG pulli it. Obviously, if it's security reasons, I'll have to reconsider keeping it.
thanks