NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
20/40MHz Coexistance (RBK963)
I have tried responding to the thread titled "Orbi 960 2.4GHz Bug Causes Devices to Disconnect from 5GHz and 6GHz Networks" twice now. Yesterday's response disappeared in a couple of hours and today...
Ya, keep v.21 loaded. What I have loaded. You'll be good there.
If disabling 20/40Mhz works then keep it disabled. Just won't effect 5ghz is all.
Aggie88 wrote:
I'm running on 7.2.6.21_5.0.20. I understand about having things in the basement but that is how I had my old RBR50 system configured and I just stayed the same.
I'll experiment soon and see if the problem comes back with coexistence turned on. I am curious from my previous software background perspective. I'll post back here when I do. Thanks for everyone's help.
đź‘Ť
Hi,
To expand on this, here's one way you can test this issue:
• Enable the 20/40MHz setting.
• Turn on the IoT network and set it to 2.4GHz only.
• Enable the 6GHz network.
Now, perform the following tests:
• Connect to the 2.4GHz IoT network and monitor for any dropouts.
• Connect to the main network ensuring the connection is 5G and monitor for dropouts.
• Connect to the 6GHz network and monitor for dropouts.
Alternatively, if you have a single device with an adapter that supports all three bands, you could manually force it to connect to each band separately by adjusting the adapter properties.
For me when I did this test the 2.4GHz remained stable without any dropouts, but both the 5GHz and 6GHz would dropout, disabling the 20/40Mhz and setting a static channel were the only two settings that had an impact on this issue, however out of these two settings the 20/40Mhz had the biggest impact.
Regards,
Liam
New FW is out:
Please update and check. May need a facory reset and setup from scratch to ensure a good take on the new FW and see if all works better for you.
I have now managed to get round to testing this, and I can confirm that "Firmware Version 7.2.7.15" has fixed this issue for me.