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...
Yeah, "a while" sometimes mean a couple of hours, sometimes next day but it will eventually happen. Even tried the safe value of 500/512.. didn't bring down the network but definitely slowed it down.. so I'll back to 64. I've tested it multiple times to confirm... ask my wife lol
And yes, most other routers default to 2347 with no issues, not sure why it only happens with Orbi.
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!