NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
The community has waited six months for a firmware update
NETGEAR, the community has waited six months for a firmware update, yet critical issues persist—especially regarding wireless backhaul performance, Apple device compatibility, and overall network stability. The entire Orbi 970 community has voiced similar concerns across multiple forums, citing poor speeds and stability problems. Based on my testing, I suspect wireless backhaul may be an ongoing problem all along but has only been clearly identified now. At a minimum, an official response from NETGEAR would be appreciated. Additionally, despite enrolling in the beta program, I have yet to receive any updates regarding admittance. My urgent questions: 1) Can NETGEAR confirm whether a **firmware fix** is in development? 2) Can I join **beta testing** to assist with troubleshooting? If I receive no response by Monday or Tuesday, I will escalate via a support ticket. My intended actions include: Requesting RMAs for my two add-on satellites to rule out faulty hardware. Installing beta firmware if available to continue in-depth testing. Engaging directly with engineers for structured troubleshooting. The Orbi 970 has potential to be an outstanding system—but only if stability issues are properly addressed. If NETGEAR resolves these problems quickly, the system's premium price will be fully justified. However, until clear progress is made, I strongly advise potential buyers to reconsider. I sincerely appreciate any input from the community and NETGEAR representatives. Instead of looping through the same troubleshooting steps, let's work together to diagnose the firmware directly. I'm an experienced IT professional, and I have exhausted every possible avenue. Stop the runaround—analyze the debug logs, test the firmware with the variables I provide, and let’s resolve this. StephenT ,Straq , netgear Thank you all for your time!Device flipping to celllular/disconnecting when on WiFi? Read this for possible solution!
Technical Analysis and Repeatable Evidence of DHCP/Routing Bug in Netgear Orbi 971 (Router Mode) Summary of Issue In environments using the Orbi 971 system in router mode, certain iOS/iPadOS devices (tested: iPhone 16 Pro Max and iPad Pro 2024) sporadically exhibit a failure state in which the device: Remains physically connected to the Orbi Wi‑Fi network (SSID displays as connected), Maintains a strong Wi‑Fi signal with excellent throughput (700–1200 Mbps), Yet silently fails over to the cellular interface (e.g., 5G), with no data traversing the Wi‑Fi path. Others on the Netgear forums over the past months have posted similar failures, using both Apple and Android devices. My analysis and solution may be correct for other non-Apple devices and other Orbi routers. This failure is not associated with actual signal loss and does not trigger any user notification other than the UI-level switch from Wi‑Fi bars to a 5G indicator. It self-recovers after 1–2 minutes. No other devices on my network (macOS, smart TVs, Windows laptops) display similar behavior. Summary of Solution For any device exhibiting drops/flips to cellular when on a good WiFi signal, change IPv4 address to a manual address, outside the router’s DHCP range. Also, change DNS address to a manual entry – it can either be your router (192.168.1.1 usually) or a 3 rd party DNS server of your choice. Finally, you must disable IPv6 on the 970 router – Advanced tab, expand the Advanced section in the sidebar, choose IPv6 and disable. To learn more as to what the problem may be, read on. My Environment Netgear Orbi 971 (Wi-Fi 7), latest stable firmware (9.13.1.2) as of July 2025. Router mode (default DHCP and NAT). IPv6 disabled at the router level. iPhone and iPad running latest iOS/iPadOS 18.5. Orbi system is sole DHCP and DNS provider on LAN. WAN is Comcast/Xfinity (stable, no packet loss during tests, 2100/300 dl/ul plan). Orbi clients tested within 15 feet of router or satellite in clear line-of-sight — eliminating signal strength as a factor. Problem Behavior When in default DHCP configuration (automatic IP and DNS): iOS devices periodically experience a silent failover to cellular (5G). Devices retain visible SSID connection. Internet connectivity is routed over cellular until the issue self-resolves. The issue is sporadic, occurring 1–5 times per week for me (others have seen higher failure rates) under default conditions. Disruptions have been reported on non-iOS devices on the Netgear forums. I wrote and tested an Apple Shortcuts automation that will trigger when the Apple device it is running on does a Wi‑Fi disconnect. It does not fire, confirming that SSID association is intact. Testing Methodology and Key Finding I conducted controlled testing to isolate the failure cause. After numerous incidents in DHCP mode, I applied the following configuration to both iPhone and iPad: Manually assigned IPv4 address within the LAN’s valid range (outside the DHCP pool to avoid collision). Manually assigned IPv4 DNS server set to 192.168.1.1 (Orbi’s own LAN IP). IPv6 explicitly disabled at the router. This configuration has now been running for over 5 consecutive days as of the date of this posting, with no recurrence of the issue. Devices have remained on Wi‑Fi, and no visible or functional failovers to cellular occurred. Why Disabling IPv6 Was Critical On iOS and iPadOS, users cannot manually configure IPv6 addresses or DNS servers via the system interface. As a result, if IPv6 remains enabled on the network: iOS will continue to obtain IPv6 connectivity using SLAAC or DHCPv6 (often via Router Advertisements from the Orbi), Even if IPv4 is statically assigned, IPv6 may still be selected for outbound traffic when iOS considers it preferred (which is often), This reintroduces reliance on the Orbi’s IPv6 DHCP or routing stack, which in prior testing exhibited instability and routing failures, often leading to connectivity loss or fallback to cellular. Thus, disabling IPv6 at the router level is a necessary precondition to ensure the device fully relies on the statically configured IPv4 path — eliminating Orbi-managed DHCP lease/route state from the equation entirely. Theory: Root Cause Analysis I propose the following sequence of events under default DHCP operation: iOS frequently initiates DHCP lease renewal or INFORM messages more aggressively than other OSes (due to roaming, sleep/wake cycles, and Apple’s proactive network health checks). The Orbi 971’s DHCP server intermittently fails to respond promptly (or at all) to these renewal or rebind requests. During this silent DHCP stall, the iOS device: Still has a valid SSID association and a cached IP, But considers the Wi‑Fi interface non-functional due to: Missing or expired lease, Failure to renew default gateway, Unsuccessful DNS resolution, Or failure to receive HTTP 204 from captive.apple.com. iOS silently switches to cellular, even with Wi‑Fi Assist disabled (which I did a long time ago), because it considers the Wi‑Fi path “connected but unusable.” Eventually, the Orbi responds again, routing is restored, and iOS resumes Wi‑Fi traffic — all without disconnecting or notifying the user. Supporting Factors No failure symptoms observed under static IPv4 + DNS configuration with IPv6 disabled. Monitoring showed no WAN outage or SSID drop during incident periods. When using dynamic DHCP/DNS, the issue persists in high signal-strength environments, ruling out RF-related causes. IPv6 had previously been associated with similar instabilities and was disabled early in the test cycle. Recommendations to Netgear Engineering I recommend the following areas be prioritized for investigation: DHCP Server Responsiveness Analyze handling of frequent DHCP RENEW/INFORM messages from Apple devices. Investigate whether ACK or lease confirmations are being dropped or delayed. Internal Lease Table Integrity Confirm whether memory or timing issues affect DHCP state or ARP caching. Routing Table Consistency Validate propagation of default routes across mesh nodes, especially post-roaming or post-sleep. IPv6 Handling (if re-enabled) Evaluate Router Advertisement stability and DHCPv6 consistency. Provide user-accessible controls for IPv6 lease time and DNS relay. Debug Logging Tools Enable deeper client-specific DHCP logging in future firmware versions to support field diagnosis. Conclusion The silent failover of iOS devices to cellular, despite strong Wi‑Fi signal, appears to be rooted in intermittent failures of DHCP IPv4/IPv6 or routing state management by the Orbi 971. Disabling IPv6 and bypassing DHCP/DNS with manual configuration eliminated the issue so far — confirming the failure lies not in radio or ISP connection, but in the Orbi’s handling of dynamic IP and DNS lease logic under typical iOS behavior. I welcome the opportunity to collaborate on further testing or provide supplemental logs to support engineering review.Testing status of 9.13.1.2 (ongoing updates)
Summary: IPv6 failed, 1 flip to 5G cellular from iPhone, memory use growing a little on 970 - watching that one. I installed FW 9.13.1.2 yesterday. All seemed to go fine (although IPv6 failed quickly on iPad and iPhone after I re-enabled it. So now I have disabled IPv6 again. Overnight my iPhone 16 Pro Max was on the night stand. Strong WiFi connection. This morning, I pick it up off its wireless charger stand, walk about 8 feet, sit down to start checking the morning emails. In about 1 minute it went from strong WiFi connection to 5G cellular, even though settings still showed it connected to my WiFi. Router IP was blank, no IP address: I waited about minute doing nothing then WiFi came back: Also in the device list, the iPhone 16 is current connected at 6GHz with a router 4 feet away - it's usually connected at 5GHz + 6GHz. That will probably correct over the morning, it's an existing problem from FW 9.12.5.3. So after about 12 hours, flips to 5G and IPv6 failure is still problem with this firmware. Summary status of issues I saw on 9.12.5.3: IPv6 fail - still an issue. IPv6 has failed on both iPad and iPhone. Flips to 5G - one failure so far memory creep - After restart, this morning the two 970s are up to 620MB and 627MB. I'll be keeping an eye on this to see if memory continues to grow, on 9.12.5.3 before the upgrade they had been around 610MB for about a week. It's not an issue if memory use stabilizes at some point soon. restarts - none yet phantom devices - none yet/no new devices visiting the house I will keep posting updates here as things happen.Installed 9.13.1.2 - initial results (positive)
I installed 9.13.1.2 on two 971s and a 970 Orbi router tonight. I am looking to test 6 basic issues I have seen on the 970 series; some of these may take days or even weeks to surface. But my test list is: Do late model devices (iPhones, iPads, Macs) maintain IPv6 connectivity? iPhone flipping to 5G cellular where it should have a strong WiFi signal in the house Memory creep on router or satellites, resulting eventually in a crash Router/satellite crashes unrelated to memory creep Phantom devices showing up in router and Orbi app device list - devices that were in the house in the past, showing up as "connected" until a reboot clears them. Weird reporting in router device list - showing every device as Wired, connected to the wrong Orbi, etc. The first 4 points are the most serious. I turned IPv6 back on, on the router, to test #1. Hopefully this is part of the "connectivity" issues fixed in this release. If the Orbis prove to be stable re: restart/crashes, I will turn logging back on and see if that causes crashes. It usually did within 3-7 days. So far after my initial update to this version of FW: IPv6 working on 4 devices (2 Mac, iPhone, iPad) Speeds, wired and wireless, are fine Packet loss/latency, Jitter report fine - nothing odd showing in the modem log I did about a 5 minute walk-around the house with my iPhone, no flips to 5G - yet I could never make it happen in the past, so time will tell. I'll update here over the days ahead as testing continues...Disconnects for iOS Devices Multiple Times Per Day with Orbi 970
I have EXACTLY this problem. Was fine until sometime around mid-April and now it's a nightmare. Only new Apple devices (iPhone 16/16 Pro and new iPad Air). I can sit with my older iPad next to my iPhone 16 Pro and the iPad is solid as rock while the phone goes in and out. Same with my PC - it's getting almost 1Gb on speedtest while the phone right next to goes in and out - sometimes I have to turn off WIFI, but often it comes and goes with me doing nothing. I also have a ton of IoT devices (most not on the IoT network) that will complain as soon as they lose connection, yet none of them do. Of course, they are in fixed locations and don't roam around the house like my phone. But even when the phone is sitting on my desk not moving around, I have the dropouts. I plan to try this with the SAT turned off to see if the mesh is part or the problem. Also trying the IoT network at 2.4 to see if that is stable and then will try it at 2.5/5 if I get that far. Maybe I'll try the WPA3 thing, but yes, I would likely have to move many devices to the IoT net, and I really don't want to do that. And I agree that I am also way past a basic response. I think Apple broke something early Spring '25 - at least that is when we started seeing all these issues. We've had the phones since winter, and the iPad is new. My older iPads work fine. Although we were out of the house most of the winter, from Jan to Apr I didn't see any issues like this. Arggg!!!! Pointless things I tried: reset iPhone network - who even suggests this nonsense, but I tried it - don't bother turn off Private WiFi address - again, don't bother turn off Limit IP tracking - or just wave your arms in the air - same effect Wifi 6e mode - try all the settings - and then wave your arms more move your satellites to various locations - maybe put one outside somewhere...nope reboot everything - in fact turn the power off to your entire house for 15 minute and restart everything! OK, don't do that either. get a different phone or ipad or hope Apple fixes this - surely other people are having this issue unless it is unique to Apple/Orbi?Orbi continually disconnects
I had the RBR50 with one satellite for many years and it worked perfectly. Then one day, it started dropping connections and slow connections. I thought it was due to be replaced since we had it for 5+ years. I upgraded to the RBE971 (with one satellite) and the problem has continued, if not gotten worse. I am at the latest firmware update. My wired connection for my laptop works great. All my WiFi devices either drop multiple times per day or sit in spin. I don’t even bother trying to connect my phone to my WiFi anymore as it only works for a short period of time before it drops. I then thought it could be my ISP (we have fiber and no modem). Everything checked out with their tests and looked good. To test further, they left one of their routers for a week and during that time, everything worked perfectly. Swapped back in the Orbi and the problem immediately came back. I have been working with NETGEAR support for over two months now and have made zero progress. I just keep getting emails that they are still researching (I am not sure what as they have not asked for any info really). If I could return this $1300 investment, I would…but while I am past the 30 days…so I am stuck. I am hoping some very smart person can help me figure this issue out.blamed everything other than the router over 9 months
Having this exact same problem, I blamed everything other than the router over 9 months but after a lot of messing about it's still hopeless. They won't refund me (apparently nether dont do that) and the technical support seem to be clueless about what to do. Like you my old orbi was fine and am considering reinstalling it just to get decent wifi again.. what a total waste of money...
