NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jjlees
Mar 25, 2020Tutor
FW 2.5.1.8 took my hardwired satellites offline
Hello, Once again Netgear forced an auto update creating havoc with a system that had been stable for months (stable after I had taken days to get stable). Situation: I have 3 hardwired satellit...
- Mar 25, 2020
A big thank you to FURRYe38, SW_ , Retired_Member for actively responding to me all day, multiple times in the day.
Here is the latest. It is all working as of this post. In desperation, I took it all down (again). Powered down from beginning to end. And with the satellites in wireless backhaul when I did. I brought it up from front to back (Fios to RBR to switch to each device and each RBS). Again, the RBS's were wireless. I confirmed each device was working, each RBR/RBS and Sonos, TiVo, garage door, ring, etc. I then wire-connected an RBS to its switch. After 3-5 minutes, it changed in the console to wired backhaul. I verified all devices were working. I then connected the next RBS to the switch. It also converted to wired backhaul. I verified every device in every room continued to work. I then did the same with the last RBS. It is all up and working as desired. Almost an hour in and no drops or interruptions. Hopefully not too soon to declare a win.
I don't know what did it. Maybe everything ...? Maybe nothing ...? But it was a major ordeal. I do appreciate the support of the community walking me through it.
FURRYe38
Mar 25, 2020Guru - Experienced User
Try a reset on the RBR and RBS and this time wirelessly connect each RBS to the RBR, then one at a time, wire connect the RBS to the RBR. Do this while in the same room with the RBR to ensure they are working correctly after the connection is made.
Try enabling Beamforming and MIMO(MIMO may or maynot be needed) and WMM. Under Advanced Tab/Advanced Settings/Wireless Settings
Try disabling the following and see:
Armor, Circle, Daisy Chain, Fast Roaming, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Set Short preamble instead of Long preamble modes. Save settings and reboot the router and satellite(s).
What is the Mfr and model# of the ethernet switch in the configuration?
https://kb.netgear.com/000051205/What-is-Ethernet-backhaul-and-how-do-I-set-it-up-on-my-Orbi-WiFi-System
You might want to download the FW files and manully apply them yourself. Auto udpate seems to cause problems to users systems when it updates FW. I prefer using this method when doing FW updates. I haven't seen any issues with my one RBS thats wired behind 4 LAN switches in a daisy chain.
jjlees
Mar 25, 2020Tutor
FURRYe38 wrote:Try a reset on the RBR and RBS and this time wirelessly connect each RBS to the RBR, then one at a time, wire connect the RBS to the RBR. Do this while in the same room with the RBR to ensure they are working correctly after the connection is made.
Try enabling Beamforming and MIMO(MIMO may or maynot be needed) and WMM. Under Advanced Tab/Advanced Settings/Wireless Settings
Try disabling the following and see:
Armor, Circle, Daisy Chain, Fast Roaming, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Set Short preamble instead of Long preamble modes. Save settings and reboot the router and satellite(s).
What is the Mfr and model# of the ethernet switch in the configuration?
https://kb.netgear.com/000051205/What-is-Ethernet-backhaul-and-how-do-I-set-it-up-on-my-Orbi-WiFi-System
You might want to download the FW files and manully apply them yourself. Auto udpate seems to cause problems to users systems when it updates FW. I prefer using this method when doing FW updates. I haven't seen any issues with my one RBS thats wired behind 4 LAN switches in a daisy chain.
I appreciate the response.
My switches are all Netgear gigabit+ unmanaged switches. I have both 16 and 32 port ones. I don't have the model #'s handy, but I changed them all to Netgear after the last fiasco last summer. Of course, it wasn't the issue, but I did it nonetheless.
I have a mixture of the suggestions already. Beamforming, WMM are enabled, but MIMO is not. No armor, no circle, no daisy chain, no fast roaming, no IPv6. I do have 20/40 coexistence enabled. Preamble is automatic. So, I can change MIMO, coexistence, and preamble. But I am not sure how wireless settings will affect my wired situation?
I will try the settings, the manual update, and the same room setup after my kids' remote school wraps up for the day. (I attempted to try one satellite back on hardwire and the yells I got!)
I am willing to try anything, so I do appreciate the responses!
-John
- jjleesMar 25, 2020Tutor
SW_ wrote:jjlees , do you have any wired clients attached to that Satellite?
SW_ For all of the wired ones, yes. Fwiw, the TiVo Bolt+ DVR that I had hardwired directly to the router also ceased to access the internet through it. Once I made it wireless, I was able to get it back online.
- SW_Mar 25, 2020Prodigy
jjlees wrote:
SW_ wrote:jjlees , do you have any wired clients attached to that Satellite?
SW_ For all of the wired ones, yes. Fwiw, the TiVo Bolt+ DVR that I had hardwired directly to the router also ceased to access the internet through it. Once I made it wireless, I was able to get it back online.
This implies that one of the wired clients is holding on to old IP address and Orbi doesn't like and can't deal with duplicated IP addresses gracefully, which could explain why it works when you take them out of the network.
Try to disconnect all those wired clients and only bring the Satellite back online by itself first. After your network is stable, reconnecting wired clients one at a time. It's one way to reboot the entire network to get Orbi back to stable state. Good luck!
- Retired_MemberMar 25, 2020
I'm still missing the part how a FW update can corrupt hardware. If that's true I doubt there's no FW that can fix it.
- jjleesMar 25, 2020Tutor
Retired_Member wrote:I'm still missing the part how a FW update can corrupt hardware. If that's true I doubt there's no FW that can fix it.
Retired_Member I don't think it changed the hardware itself, but it has apparently affected the instructions that cause it to operate ... or not operate.
- Retired_MemberMar 25, 2020
jjlees wrote:
Retired_Member wrote:I'm still missing the part how a FW update can corrupt hardware. If that's true I doubt there's no FW that can fix it.
Retired_Member I don't think it changed the hardware itself, but it has apparently affected the instructions that cause it to operate ... or not operate.
Ok be careful for there are some who want you to reload the same FW that evidently started the problem just because it works for them
- FURRYe38Mar 25, 2020Guru - Experienced User
Have you powered off ALL switches then back ON then connect the RBS to the switch?
I would test all RBS directly to the RBR first while in the same room as the RBR. If you can get each one to connect directly to the RBR or ALL of them and they report wired status, then go back and place at remote locations. I would while your in the same room with the RBSs, do a IP address reservation for each RBS on the RBR. Something I do to ensure they get same IP addressing.
If you think the RBR or RBS have corrupt FW loads, I recommend you download the FW files for both and apply them manully using IE11 or FF browser with a wired PC. After the FW is reloaded, factory reset and setup from scratch. I would apply v2.5.1.8 again so your up to date. This version has been working fine for me and other with ethernet connected RBS.
jjlees wrote:I appreciate the response.
My switches are all Netgear gigabit+ unmanaged switches. I have both 16 and 32 port ones. I don't have the model #'s handy, but I changed them all to Netgear after the last fiasco last summer. Of course, it wasn't the issue, but I did it nonetheless.
I have a mixture of the suggestions already. Beamforming, WMM are enabled, but MIMO is not. No armor, no circle, no daisy chain, no fast roaming, no IPv6. I do have 20/40 coexistence enabled. Preamble is automatic. So, I can change MIMO, coexistence, and preamble. But I am not sure how wireless settings will affect my wired situation?
I will try the settings, the manual update, and the same room setup after my kids' remote school wraps up for the day. (I attempted to try one satellite back on hardwire and the yells I got!)
I am willing to try anything, so I do appreciate the responses!
-John
- Retired_MemberMar 25, 2020
FURRYe38 wrote:Have you powered off ALL switches then back ON then connect the RBS to the switch?
I would test all RBS directly to the RBR first while in the same room as the RBR. If you can get each one to connect directly to the RBR or ALL of them and they report wired status, then go back and place at remote locations. I would while your in the same room with the RBSs, do a IP address reservation for each RBS on the RBR. Something I do to ensure they get same IP addressing.
If you think the RBR or RBS have corrupt FW loads, I recommend you download the FW files for both and apply them manully using IE11 or FF browser with a wired PC. After the FW is reloaded, factory reset and setup from scratch. I would apply v2.5.1.8 again so your up to date. This version has been working fine for me and other with ethernet connected RBS.
why are you telling him to reload what caused the problem. There are more who have had problems than not.
jjlees wrote:I appreciate the response.
My switches are all Netgear gigabit+ unmanaged switches. I have both 16 and 32 port ones. I don't have the model #'s handy, but I changed them all to Netgear after the last fiasco last summer. Of course, it wasn't the issue, but I did it nonetheless.
I have a mixture of the suggestions already. Beamforming, WMM are enabled, but MIMO is not. No armor, no circle, no daisy chain, no fast roaming, no IPv6. I do have 20/40 coexistence enabled. Preamble is automatic. So, I can change MIMO, coexistence, and preamble. But I am not sure how wireless settings will affect my wired situation?
I will try the settings, the manual update, and the same room setup after my kids' remote school wraps up for the day. (I attempted to try one satellite back on hardwire and the yells I got!)
I am willing to try anything, so I do appreciate the responses!
-John
- jjleesMar 25, 2020Tutor
FURRYe38 wrote:Have you powered off ALL switches then back ON then connect the RBS to the switch?
I would test all RBS directly to the RBR first while in the same room as the RBR. If you can get each one to connect directly to the RBR or ALL of them and they report wired status, then go back and place at remote locations. I would while your in the same room with the RBSs, do a IP address reservation for each RBS on the RBR. Something I do to ensure they get same IP addressing.
If you think the RBR or RBS have corrupt FW loads, I recommend you download the FW files for both and apply them manully using IE11 or FF browser with a wired PC. After the FW is reloaded, factory reset and setup from scratch. I would apply v2.5.1.8 again so your up to date. This version has been working fine for me and other with ethernet connected RBS.
FURRYe38 I have powered off/on the switch next to the satellite I was most recently trying to bring back online as hardwired. I don't think they have corrupted FW now as I manually put in the previous version (satellites first, then router). I will try doing it to the current version with them in the same room later this afternoon.
I did the IP reservation a couple days ago for each satellite since the problem first occurred.
I looked up my switches. Netgear 16 and 24 port gigabit unmanaged switches. GS316 and GS324's.
Thanks!