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.
2.5.0.38 is the worst firmware my devices have ever seen. I have a RBK50 with two RBS50s and they have been functioning perfectly for over two years. Did the upgrade last night and multiple problems. (1) Attached devices naming, icons, and types are wrong and manual correction doesn't stick, (2) my Galaxy S10+ which normall connects at 5Ghz over 400Mbps struggled to maintain a 2.4 connection at abysmal speeds (< 40 Mbps) link speeds. This is without any geographic changes. Rebooted all and no help.
Downgraded back to 2.3.5.30 and everything worked perfectly again.
Not sure this firmware is ready for full production deployment. Recommend it be PULLED due to the plethora of problems are fixed.
2.5.0.38 is the worst firmware my devices have ever seen. I have a RBK50 with two RBS50s and they have been functioning perfectly for over two years. Did the upgrade last night and multiple problems. (1) Attached devices naming, icons, and types are wrong and manual correction doesn't stick, (2) my Galaxy S10+ which normall connects at 5Ghz over 400Mbps struggled to maintain a 2.4 connection at abysmal speeds (< 40 Mbps) link speeds. This is without any geographic changes. Rebooted all and no help.
Downgraded back to 2.3.5.30 and everything worked perfectly again.
Not sure this firmware is ready for full production deployment. Recommend it be PULLED due to the plethora of problems are fixed.
sheesh, I can do that but Netgears official documentation for in-place gui firmware updates does not require this. Every other time I have done such there has been no need to.
IMHO, if Netgear's official stance is that we have to do a factory reset and full reconfiguration with each and every in-place upgrade there is a significant engineering problem with the FW......
There are a bunch of posts similar to mine in the forum regarding device connectivity and reliability. And, for what it's worth, the device display is annoying.
I'm very happy since I downgraded (the RBS50s and the RBK50)
For a UI that recommends an in-place upgrade the update should be fully regression tested by netgear before it is offered up. I still content that a full factory reset is an unreasonable expectation.
Can you imagine how users would feel if a MSFT bi-annual feature update (1809, 1903, 1909, etc) required that you did a full factory reset (clean install) on windows?
Model: A6100|WiFi USB Mini Adapter, RBR50|Orbi AC3000 Tri-band WiFi Router
I have had no reliability issues with mine since updating. Yes, I factory reset and for what it's worth. It works
Factory reset is a last resort to any kind of issues that seems to appear out of any problem that arises on routers. Been like this for a long time. Though NG user experiences and expectations have been that FW has been upgraded on a router and should run after the update, those have had good experiences here. For those that don't, yes, a factory reset and setup from scratch is needed. This helps clear out any possible mis-configurations and any lingering prior FW code. Gives the FW and router a chance to start from a clean slate. I have seen this problem before after updating FW, odd things happen. After a reset is done, those odd problems were fixed.
Not a valid reset option for Windows since windows doesn't have a reset feature. Resets features have been and will be supported on any ROUTER device. There a good reasons why this feature is here.
There are a bunch of posts similar to mine in the forum regarding device connectivity and reliability. And, for what it's worth, the device display is annoying.
I'm very happy since I downgraded (the RBS50s and the RBK50)
For a UI that recommends an in-place upgrade the update should be fully regression tested by netgear before it is offered up. I still content that a full factory reset is an unreasonable expectation.
Can you imagine how users would feel if a MSFT bi-annual feature update (1809, 1903, 1909, etc) required that you did a full factory reset (clean install) on windows?
For what it's worth, I did the firmware upgrade to 2.5 earlier in the week, and after that my internet connection constantly dropped, ie every 5 minutes. Multiple devices had the same experience. I did the factory reset, and no improvement.
So today, I manually reverted back to the 2.3 firmware version, and I can tell immediately that the problem has been resolved in that the internet connection has been very stable and normal dl speeds.
Did you try a factory reset on the system after you updated? Mines been online and speeds are to spec since v38 was installed. 4 days and counting and no issues with speed. 200/10 wired and wireless. I factory reset mine after updaing FW and setting up from scratch.
For what it's worth, I did the firmware upgrade to 2.5 earlier in the week, and after that my internet connection constantly dropped, ie every 5 minutes. Multiple devices had the same experience. I did the factory reset, and no improvement.
So today, I manually reverted back to the 2.3 firmware version, and I can tell immediately that the problem has been resolved in that the internet connection has been very stable and normal dl speeds.
Did you separate the SSIDs? This isn't supported on any FW version.
Is there documentation that it is not supported? Considering we can telnet to the router and configure them that way, it seems unlikely that it wouldn't be a supported configuration.
Did you separate the SSIDs? This isn't supported on any FW version.
Is there documentation that it is not supported? Considering we can telnet to the router and configure them that way, it seems unlikely that it wouldn't be a supported configuration.
'I'm using a Netgear DM200 - the second factory reset seems to have resolved this"
Is this modem in router or bridge mode? It should be bridged or running modem mode only. If not, this would be one reason why the Orbi could be having problems.
It's in bridge mode, always has been, has never been set up as a router as was brought alongside the Orbi.
Ya I know about peoples configurations. However backup configurations to file can help here. First we need to get the modem and RBR setup and stable first. Lets leave IP reservations and access controls alone for now. Disabled. One step at a time.
I tried loading a back-up, first, still had lots of problems. I really don’t understand why anyone would think having to Factory reset your device every time there is an update is ok? It’s not.
Also now have new bug – it disconnects from the internet every time a new device is added and has to be rebooted to reconnect.
I have an RBR50 with one RBS50 satellite with a separate cable modem, and everything has been running smoothly until I upgraded to firmware version 2.5.0.38 yesterday. Since then, my iPhone (11 Pro Max iOS version 13.2) has been experiencing intermittent loss of connectivity issues where it will just stop being able to connect to the Internet and requires a reboot to fix. I noticed in my Orbi logs that it does seem to be doing DHCP requests quite often, but based on older posts, this seems to be normal behavior and shouldn't be an issue. I replaced the last six digits of my MAC address with xx:
[DHCP IP: 192.168.1.21] to MAC address 7c:a1:ae:xx:xx:xx, Wednesday, October 30, 2019 08:34:34
[DHCP IP: 192.168.1.21] to MAC address 7c:a1:ae:xx:xx:xx, Wednesday, October 30, 2019 08:22:29
[DHCP IP: 192.168.1.21] to MAC address 7c:a1:ae:xx:xx:xx, Wednesday, October 30, 2019 05:29:08
[DHCP IP: 192.168.1.21] to MAC address 7c:a1:ae:xx:xx:xx, Wednesday, October 30, 2019 05:13:07
It appears that the DHCP requests are coming in after the phone wakes from sleep after it's been sitting idle for awhile.
My Macbook Pro laptops don't seem to have this issue. Anyone else run into this? Is Netgear aware of it and working on a fix? Thanks!
So a 2nd factory reset resolved your problems you were seeing?
i agree that users shouldn't have too, however for these odd issues seen after a FW udpate, it maybe needed. I'd do another backup configuration to file after the reset and setup from scratch. So you have good clean backup.
'I'm using a Netgear DM200 - the second factory reset seems to have resolved this"
Is this modem in router or bridge mode? It should be bridged or running modem mode only. If not, this would be one reason why the Orbi could be having problems.
It's in bridge mode, always has been, has never been set up as a router as was brought alongside the Orbi.
Ya I know about peoples configurations. However backup configurations to file can help here. First we need to get the modem and RBR setup and stable first. Lets leave IP reservations and access controls alone for now. Disabled. One step at a time.
I tried loading a back-up, first, still had lots of problems. I really don’t understand why anyone would think having to Factory reset your device every time there is an update is ok? It’s not.
Also now have new bug – it disconnects from the internet every time a new device is added and has to be rebooted to reconnect.
What is the Mfr and model# of the ISP modem the NG router is connected too?
Has a factory reset and setup from scratch been performed since last FW update? Power OFF The ISP modem for 30 seconds then back on then walk thru the setup wizard after doing a factory reset?
I have an RBR50 with one RBS50 satellite with a separate cable modem, and everything has been running smoothly until I upgraded to firmware version 2.5.0.38 yesterday. Since then, my iPhone (11 Pro Max iOS version 13.2) has been experiencing intermittent loss of connectivity issues where it will just stop being able to connect to the Internet and requires a reboot to fix. I noticed in my Orbi logs that it does seem to be doing DHCP requests quite often, but based on older posts, this seems to be normal behavior and shouldn't be an issue. I replaced the last six digits of my MAC address with xx:
[DHCP IP: 192.168.1.21] to MAC address 7c:a1:ae:xx:xx:xx, Wednesday, October 30, 2019 08:34:34
[DHCP IP: 192.168.1.21] to MAC address 7c:a1:ae:xx:xx:xx, Wednesday, October 30, 2019 08:22:29
[DHCP IP: 192.168.1.21] to MAC address 7c:a1:ae:xx:xx:xx, Wednesday, October 30, 2019 05:29:08
[DHCP IP: 192.168.1.21] to MAC address 7c:a1:ae:xx:xx:xx, Wednesday, October 30, 2019 05:13:07
It appears that the DHCP requests are coming in after the phone wakes from sleep after it's been sitting idle for awhile.
My Macbook Pro laptops don't seem to have this issue. Anyone else run into this? Is Netgear aware of it and working on a fix? Thanks!
Off the top of my head, I don't know the make/model of the cable modem that I own, but nothing on it has changed, and other devices on my network aren't having the same problem of losing Internet connectivity, so I don't think it's a modem issue. I haven't done a factory reset of the Orbi, and I cringe at the thought of doing that. I'm just wondering if anyone else has run into the issue and if Netgear is aware of it. Thanks!
For some users, a reset and setup from scratch is needed. Others have post it has resolved there issues.
Just checking to see if there is a router built in to the modem is all.
I manually installed this v38 FW on my system, factory reset and setup from scratch. Other than a known device naming issue. System ran for a good solid week with ZERO issues.
Off the top of my head, I don't know the make/model of the cable modem that I own, but nothing on it has changed, and other devices on my network aren't having the same problem of losing Internet connectivity, so I don't think it's a modem issue. I haven't done a factory reset of the Orbi, and I cringe at the thought of doing that. I'm just wondering if anyone else has run into the issue and if Netgear is aware of it. Thanks!
Off the top of my head, I don't know the make/model of the cable modem that I own, but nothing on it has changed, and other devices on my network aren't having the same problem of losing Internet connectivity, so I don't think it's a modem issue. I haven't done a factory reset of the Orbi, and I cringe at the thought of doing that. I'm just wondering if anyone else has run into the issue and if Netgear is aware of it. Thanks!
For security reasons. In my opinion, it's always good to be running the latest firmware to get the latest security vulnerability fixes. By the way, my cable modem does not have a built in router. Thanks!
Ok, thanks for letting us know. Yes latest FW is good and does work. Again, some users need to factory reset and setup form scratch. I would also power OFF the modem for 30 seconds as well while the RBR is being reset. This should help resolve your issues. After getting it setup again, do a backup configuration and save to file. This will save you time should a reset be needed later on down the road.
For security reasons. In my opinion, it's always good to be running the latest firmware to get the latest security vulnerability fixes. By the way, my cable modem does not have a built in router. Thanks!
