NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBK853 Ping Lags/Drops - Network unusable this morning
I'm NOT a happy camper. So this morning, my wife mentioned that the Wi-Fi was having issues early this morning and woke me up. I noticed that all security cameras were offline and my phone was h...
Orbi AX and the AX system seem to be one system where CTS 64 seems to be what NG has tuned with in the wifi drivers. Ya most N and AC wifi current and past was always set for 2347. Seems that isn't the case anymore for Orbi AX.
FURRYe38 wrote:Orbi AX and the AX system seem to be one system where CTS 64 seems to be what NG has tuned with in the wifi drivers. Ya most N and AC wifi current and past was always set for 2347. Seems that isn't the case anymore for Orbi AX.
I think Netgear needs to make 64 the default setting when they release the next firmware (and document it as such in the changelog or release notes). This would not only eliminate a lot of support calls, headaches and frustrations and and even customer returns of the Orbi units, all because of something as simple as a configuration setting.
I'll give 64 a try again when I factory reset my units and attempt it again.
Quick question on the 20/40 MHz coexistence: should I leave it enabled or disabled? I know the default was enabled but apparently at the expense of performance?
64 has been default for several versions of FW now.
Try 20/40Mhz i've left mine at 20/40Mhz and haven't see any issues in performances.
- I've factory reset and got my Orbi AX up and operational.
Updated the router and the satellites to the latest firmware during the initial setup (it was required).
The CTS setting by default was already at 64 so I left it at that.
Keeping my fingers crossed that it doesn't break again!OK, looks like I was overly optimistic. :(
Here's the full details.
Last night after everyone was asleep, I got the main router up and the two satellites factory reset, configured and back online. I was only able to put one satellite into production (via wired backhaul) and that was good. I wasn't able to bring the second one online as the room was occupied so I had to wait until morning.
Throughout the night, I had continuous pings running to the following:
192.168.1.1 - router
192.168.1.10 - satellite 1 (in production)
8.8.8.8 - google
Everything looked good, without a single drop on the pings and the network seemed fine.
This morning, when I plugged the second satellite in (wired backhaul), it came online. Within a few minutes, I noticed that my pings to the router, both satellites and to google were dropping. The issues that I had experienced earlier yesterday were occuring again; cameras, etc. were all going offline. I quickly disconnected the power to the second satellite and the pings resumed back to normal and everything came back online.Here are the symptoms that I'm seeing:
-- In the GUI, under basic, home tab, for the box that says "attached devices", it shows the correct number of satellites: 1.
-- If I click on the attached devices box, it shows 2 satellites? Shouldn't it only show 1?
-- In the app (Android), it show 2 satellites as being online (the icons have the green LEDs). Shouldn't this only show 1?
I plan to reset the satellite that's offline currently but how do I remove it properly from the Orbi network? I don't see an option to remove or disassociate it from my current network from either the app or the GUI.
.