Are you noticing high CPU utilization as well? Wondering if the CPU utilization is increasing higher and higher, and maybe triggering some type of safety reboot or something? Or maybe just crashing the device from the CPU maxing out? Just a theory...
Model: RBK50| Orbi AC3000 High-Performance Tri-Band WiFi System
Tried this today for fun. No nvram or factory reset, just redeployed the .16 update to satellite and router and restarted. Looked fine for about 3 hours, then the connection list on the satellite disappeared. The router attached devices list shows connections to the satellite, and the satellite "status" indicates connections to 2.4 and 5 ghz. So still messed up from that regard.
@webminster wrote: Sorry if I misunderstood. Yes, the router list doesn't accurately show what's connected to router vs. satellite. I didn't install .12, but did the auto-update to .16.
Since things obviously aren't working for you, would you mind trying re-update the devices manually? First the satellites and then router. Just wondering if something didn't happen during the update. I did re-install my .12 and then when I moved to .16 device list was fixed.
Model: RBK50| Orbi AC3000 High-Performance Tri-Band WiFi System
I had never used this either. So being a noob to this and looking at the System Uptime, I have been out of the house for 3 hours. Would this mean that the router rebooted 1:22 minutes ago?
Model: RBK53| Orbi Router + 2 Satellites Orbi WiFi System
I had never used this either. So being a noob to this and looking at the System Uptime, I have been out of the house for 3 hours. Would this mean that the router rebooted 1:22 minutes ago?
Your numbers didn't come through, but yes, if you show 1:22 minutes up-time, that would mean that the system restarted 1 hour and 22 minutes ago, while you were away.
Frankly, I suspect a lot of people who believe they have "no problems" are just missing the moments when their system reboots, if they aren't home, or aren't using Wi-Fi/network when it happens. It's easy to miss unless you are looking at the router or satellites while the reboot is happening, as you're only offline for a few minutes. Only way to be sure is look at the up-time info.
@kmichalec wrote: Do you have logging turned on in the debug settings? What is it saying before the crash?
No, I forgot to turn on logging in debug, unfortunately.
I've taken down the Orbi and am using my Eero system right now as family demanded I stop "playing around and breaking the network." 🙂😮
The next time I have some time to try the Orbi again (either late at night or early AM when they are asleep) I'll enable the logging so I can see what preceeds the reboots.
Yes many are seeing all the satellite show devices or are all connected to main router and list is incorrect not sure what Netgear is doing to address this issue.
And now, none of my devices show as connected to the satellite, just the router. What a joke!
This is a known issue, but it's display only - assuming you are on firmware 2.1.1.16 - you should see some devices in the router as connected to your satellites - otherwise your firmware is probably not installed correctly and your satellites are not accepting connections. I would try to re-install the firmware in your case - follow the normal instructions - download both router and satellite firmware, unzip it and then install it onto satellites first - one by one - then on the router after the satellites come back (light on top goes solid blue and then out.)
Netgear are working on the not all devices are displayed issue and that will be fixed in the next firmware - but otherwise I am find 2.1.1.16 very solid. Uptime now for me is 4 days and 16 hours.
Whatever I had with. 16 it's fine now. I found it rebooting randomly, disabled circle ran a few days.. Re enabled it and no random reboots now. ¯\_(ツ)_/¯
We have 2 Pixel XL phones and we had no issues with reboots when we had the Orbi system... Also the Linksys Velop has been working flawlessly. Both phones have been on Oreo 8.1.
Since the 2.1.1.16 update, I have been forced to restart Circle a few times to make internet connectivity work again. I have not restarted router or satellites in these circumstances.
Darren...just to clarify...this new beta firmware fixes stability issues in 2.1.1.16? I.e., this should be installed if we already have 2.1.1.16 installed, correct?
I just updated my router and all satellites to the beta. So far so good but I am going to run it through its paces to see if I get any more random disconnects and reboots.
Having been a very early adopter of 2.1.1.16 and experiencing a lot of wifi disconnections I decided to wait a day or so before upgrading to the beta software. Just over 24 hours ago I upgraded as follows RBR50 to 2.1.2.10, RBS50 (2) to 2.1.2.10 and RBW30 (1) to 2.1.2.2. Everything seemed rock solid so I decided to try the ethernet backhaul to one of my RBS50 satellites. Within moments of plugging an ethernet cable into one of the LAN ports of the satellite and the other end into a remote switch located near the satellite the network just went into a cycle of crashing, coming back up, crashing etc. I have a number of IP cameras both on the LAN and remote (on iSPY) and they were streaming video, then disconnected, coming back and then disconnecting again. I waited 15 minutes to see if things would settle down but then gave up and disconnected the ethernet cable. After about 5 minutes and a power cycle of the RBR50 things returned to normal. I see from this thread that others seem to be using ethernet backhaul without any issues. I haven't found any instructions saying there is some particular way to connect the RBS50 to the RBR50 via the LAN so can anyone shed any light on what I am doing wrong?
Model: RBK50| Orbi AC3000 High-Performance Tri-Band WiFi System
