NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Latest Firmware V2.5.0.38
I applied this latest firmware and my satellite is no longer connected. Also my attached devices is not working. It seems wonky. I'm not sure how to get my sattelite back nor do I trust what my devices are.
Is there anyway to roll this back? Or is this a known issue?
Thansks.
106 Replies
Has a factory reset and setup from scratch been performed since last FW update?
Was this FW update in the RBRs web page?
No not at all. I update to the lastest firmware since I've installed it, usually without a problem.
Please try a factory reset on the RBR and RBS and setup from scratch. Walk thru the setup wizard.
What is the Mfr and model# of the ISP modem the NG router is connected too?
FURRYe38 wrote:Has a factory reset and setup from scratch been performed since last FW update?
Was this FW update in the RBRs web page?
You didn't answer these questions:
Is there anyway to roll this back? Or is this a known issue?
RDMSYS wrote:I applied this latest firmware and my satellite is no longer connected.
Why did YOU update?
- I always do when it says theres a new firmware. Why shouldn't I?
Please try a factory reset and setup from scratch first to see if you get the system back up and running. Let us know.
https://community.netgear.com/t5/Orbi/New-Firmware-v2-5-0-38/m-p/1813852/highlight/true#M73266
RDMSYS wrote:
I always do when it says theres a new firmware. Why shouldn't I?
Ok, my RBK50 is setup and running. Use the Update ALL to apply the new version. Factory reset RBS and RBR and setup from scratch.
OK, I really don't get it. I can see some devices are STILL connected to the satellite and are in fact working without an issue. Yet, the management screens say it's disconnected? I don't know what to make of it but I guess I still am planning to drop and readd the satellite.
Let us know it the REMOVE, reboot the RBR and then Add Satellite works to solve this.
All this could be fixed by NG just turning off auto updates...Simple as that, no if ands or buts.
kyleb88 wrote:All this could be fixed by NG just turning off auto updates...Simple as that, no if ands or buts.
what would that do? Leave you to decide what FW you install? and...how would you do that?
NG forces my orbi to update to 2.3.5.30 which kills my wifi. If I run 2.3.1.44 my orbi runs rock solid. This update then says it fixes wifi stability. It does not fix my stability. I do not want to update from my 1.44 firmware.
kyleb88 wrote:All this could be fixed by NG just turning off auto updates...Simple as that, no if ands or buts.
This is not an "auto update". User who go to the web interface or the Orbi "app" get a notice thta new firmware is available. Everyone who is commenting on the new firmware chose to install it. (Just as I have chosen to wait until a concensus appears about whether the update is on balance a "good thing" or a "bad thing.")
CrimpOn wrote:
kyleb88 wrote:All this could be fixed by NG just turning off auto updates...Simple as that, no if ands or buts.
This is not an "auto update". User who go to the web interface or the Orbi "app" get a notice thta new firmware is available. Everyone who is commenting on the new firmware chose to install it. (Just as I have chosen to wait until a concensus appears about whether the update is on balance a "good thing" or a "bad thing.")
That's what I was wondering. After reading all these posts about the latest FW, I was wondering was it pushed (no action by user) or did the user go looking for trouble?
I do not see a link to download it anymore have a link?
I cannot believe some of the people in this thread blaming users for installing a fw update that was readily available on the web console. Guys-- this isn't a little company and it is 2019. Firmware that is released to the public regardless of whether it is auto-pushed or not shouldn't have these bugs. I could be a new user that just purchased and click check for updates and see there is one available never having stepped on this forum for guidance.
Most smaller companies I've worked for would fire QA leads/teams if this kind of stuff got shipped out. Look at other tech/software companies and you typically can enroll in BETA groups to test firmware that is suspect to have bugs. Netgear should be ashamed of themselves for continuing to release FW that isn't ready for the spotlight-- and blaming it on end users is absolutely asinine.Not blaming users, were trying to help them get the system working here. I and others are having good experiences since updating FW. I have done a factory reset which I always do. Some have not done a factory reset and have good experiences still. There are many factors that contribute to bad experiences. Were here to work thru them is all. The more information and feedback we get from users helps us help user with bad experiences.
I don't understand the "factory reset after each update". Why is that necessary? I have updated my firmware maybe 5-6 times since I installed. And nothing happened. Which I expected fully. WHY would you need to do a factory reset EACH time you apply firmware?
I said it yesterday and I'll say it again, ridiculous.
The poor guy above spent 5 hours setting up his network again? I'm not sure it would take me that long but I don't want to have to do it at all.
And I see a lot Netgear isn't that great posts. Well when I was looking at Mesh routers last Janurary they were reccommeded by a lot of people and were a lot of bang for the buch so I went with them.
Now I don't really have any issues with my set up. Everything runs great. But in my mind I think that a FW can only make things better.
Maybe i'm naive.
I was miffed on Monday after doing it blindly and getting semi hosed. But seeing all these other issues I guess I shouldn't complain.
I won't do that again though. I'll wait for the push.
Hixz wrote:I cannot believe some of the people in this thread blaming users for installing a fw update that was readily available on the web console. Guys-- this isn't a little company and it is 2019. Firmware that is released to the public regardless of whether it is auto-pushed or not shouldn't have these bugs. I could be a new user that just purchased and click check for updates and see there is one available never having stepped on this forum for guidance.
Most smaller companies I've worked for would fire QA leads/teams if this kind of stuff got shipped out. Look at other tech/software companies and you typically can enroll in BETA groups to test firmware that is suspect to have bugs. Netgear should be ashamed of themselves for continuing to release FW that isn't ready for the spotlight-- and blaming it on end users is absolutely asinine.You may have not visited with our friends over at Linksys. Most router manufacturers suffer throught the same firmware war. That is trying to find the perfect firmware for all users. NOT. One only has to spend a few days in here to read of the dozen+ ways that people run their systems with double routers, switches, speed test, etc. This whole FW subject has been beat to death, and my position remains, IF your system works, leave it alone. Your will gain much more joy in knowing it works than ever performing a self install of the next wiz bang FW. Good luck.
I've been using Orbi since 2017 and do enjoy Netgear and the equipment. My frustration is that some of these bugs continue to be the same throughout fw releases, such as the device names resetting. By now this should be a part of the regression testing and I've seen it posted on enough sites to know it's an issue for a large majority of users. It isn't a small one off issue with configuration. I can reset my system and add only 1 device and it still has the bug. The QA team is either too small or they aren't testing enough configurations.
Cannot rename attached devices, no matter what.
Cannot change icons in attached devices list.
Known issue already:
schornstadt wrote:Cannot rename attached devices, no matter what.
Cannot change icons in attached devices list.
I upgraded without issue(for the most part). I run as vanilla a setup as it gets. Only change my DNS to OPENDNS and 2 wifi settings(enabled beamforming and MU-MIMO). I do not use guest access, Armor, or Circle services. Upgrade an rebooted without issue.
I dont really pay attention to the device list all too much. But I did notice that my ring doorbell pro device now has a name of "Homeboy" which was not there before. Anyone else have this?
Thanks
- For any Circle issues, Please post about this in the Circle app forum:
First time ever I did a firmware update and had a problem similar to everyone else. After the update finished, my router turned on and 2 of 2 sattelites were disconnected.
Solution for me:
I unplugged the router and both sattelites. Then replugged. Both turned blue, but only one showed up as connected. So I went to the one sattelite that said disconnected and instead of doing the same thing, I took a paperclip and did a reset. And it worked. I'm sure this is a type of problem that has different solutions for everyone, but I'm glad I didn't have to do a factory reset.
This may or may not help, and may or may not be pure coincidence - but reading the solutions (factory reset) presented made me irritated enough to post it as a suggestion -- in case it helps.
I decided to try to poke and bang it a little, so to speak, to see if anything came loose - I turned on "Access control" ( [Admin_Base_URL]/adv_index.htm ) - just turned it on, nothing else. After a few minutes, it started showing everything, Could be a coincidence - no idea.
One other thing: despite the web interface showing no satellites attached, I used a wireless card in "monitor mode" to verify that the routers were in fact connected and talking. (Aircrack-NG, Kismet, Bettercap etc - tools we don't talk about in polite conversation, but they help here!)
Best of luck!
