NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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 li...
It's early to declare victory, but in 3 days I have not had any memory creep situation on the 970s (which ends up in a crash/restart), or restarts independent of memory creep (which I have seen). I only had 1 flip to cellular 5G less than about 4 hours after upgrading to 9.13.1.2, but that was when I was testing IPv6, which is NOT ready for prime time (Netgear knows and is working on this) - so I disabled it.
I did a power-cycle after disabling IPv6, and no flips to 5G cellular in 2 days. Memory creep can take up to 2-3 weeks to show up, but if I go 2 weeks with no flips to cellular/loss of WiFi in the house I would say they nailed it. This FW is solid otherwise for me - streaming, speed, latency, packet loss all perfect. Here is a mid-afternoon workday zoom call latency/pkt loss tracking result:
Looking good. Fingers crossed.
I am seeing something weird with this new firmware. Tonight, I keep getting the red light on my router, app showing router offline, but my Roku continues to stream, my computer continues to stream, but on that same computer I cannot go to websites, even though I am streaming Spectrum on it. Certain devices offline. Red light of router on/off on/off and various intervals. I submitted a bug report to Ssu-Tuan via email. Error page on Edge says it can't find DNS.
Didn't have this behavior on previous firmware.
JWS9518 you may have something else going on here. If it's just a simple case of the router not communicating with the modem/internet, the router is Magenta. Red pulsing light means the router thinks its WAN link or its own firmware is unhealthy – often a missed heartbeat to Netgear’s cloud or a brief loss of the ISP gateway. My theory is, existing TCP sessions stay up because they already know the server IPs and don’t need new DNS look-ups - so your Roku continues to stream. But fresh DNS queries from the PC are timing-out, so anything that needs a new IP address fails.
If you haven't taken these steps, I would try:
- Is there any way you can verify your ISP signal etc. is healthy - that they are not having any problems? I have Comcast for example, they have a status page which reports any issues, in addition to their app reporting that there are problems or maintenance in my neighborhood.
- What does your modem say is going on? I assume it shows no problems, log is clean, signals still good? If not the problem is there. Also, check cable connection between modem and router, they can come loose.
- Assuming no issues in #1 or #2, reboot through the Orbi router's web admin page at 192.168.1.1 - doing it there will reboot the satellites as well. Often a simple reboot will clear things up, especially after a firmware update.
- If it's on turn, off IPv6 setting on router admin page - Advanced tab, advanced section, IPv6. There are issues with it, NG is aware and is working on them. I actually have IPv6 turned off permanently.
- If the problem persists, as Netgear recommends, do a factory reset:
If continued problems are seen after a FW update, it's recommended to try a factory reset and setup from scratch with out loading any saved configurations from backup files. Use the ERASE button on the routers web page to factory reset the router:
https://kb.netgear.com/000062081/How-do-I-erase-the-configuration-settings-on-my-Orbi-WiFi-System
This sends a Factory Reset command to any and all connected RBS as well.Here's a good procedure with all the detailed steps for doing a factory reset if you have to:
Re: Orbi Satellite Information and FAQ | NETGEAR Communities
Good luck and let us know how it goes!
