NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR850 RTS / CTS
I’ve been doing some research around RTS / CTS. It would appear that the current size parameters of RTS/CTS are based around the older WEP encryption standard. Below are the different possible m...
I’d be interested to understand if this remains an issue if the satellite uses a wired backbone instead.
I can confirm that this issue definitely did occur with a wired satellite, during long videocalls with the threshold set to 2347. Since I set it to 500 I haven't seen the same behaviour.
Garwoofoo Thanks for the confirmation.
I’ve just updated to the latest firmware v4.6.7.5 (was previously on v4.6.6.11) and have set the CTS/RTS to 2347 so I can observe it’s behaviour.
I’ll soon know if it becomes an issue when the kids get home from school / college and start hammering the Wi-Fi. 😂
I’ve just updated to the latest firmware v4.6.7.5 (was previously on v4.6.6.11) and have set the CTS/RTS to 2347 so I can observe it’s behaviour.
I’ll soon know if it becomes an issue when the kids get home from school / college and start hammering the Wi-Fi. 😂
I've only seen a reboot problem once on my 7 series however that was with older version of v4 FW. I've always left my Orbis with default CTS values to see how the system and my devices should work with defaut out of the box settings. I only did change the CTS value to max one time while in v3 FW due to troubleshooting NEST controller low battery issues back then. Since v4 has been out, I have not change CTS from 64. Haven't seen any issues since. We are tracking one issue with Whats App and voice calls seem to be problematic on v5 FW. Other then that, been fairl stable. I may need to revisit the Whats app problem and see if CTS maybe involved any.
I usually change my CTS/RTS settings to max (2347) as soon as I get a new NG device. Then, I watch the router statistics closely for a few days/weeks to see if there are any collisions. While I have a fair number of connected devices (35), the majority of them are low traffic devices and I have never had an issue with any collisions so 2347 works fine with me.
From what I've read regarding CTS/RTS settings, as long as you are not getting any collisions, 2347 (basically CTS/RTS OFF) is fine. If you start getting collisions, then you need to adjust.
I have also seen on several places that with such a low value as is set by NG when their Orbi devices are delivered, that you may end up with a latency issue.
I am not a user of ZOOM or other videocall type of software except on very rare occasions. I've not had any drop/reconnect, but then again, I do not have a great number of calls to refer to.
The issue of default RTS value is somewhat of a puzzle to me. I read comments on the forum that Netgear delivers products with the RTS value set to 64, but mine is 2347 and I have no memory of ever changing it. As a check, I just now did a factory reset on an RBR50 and the RTS value came up 2347. Perhaps some Netgear WiFi routers come set to 64 and others come set up 2347?
Further, when I search for "RTS default value", hits come up from Cisco, Linksys, and other vendors stating that the default value is 2347. Articles about "What is the best RTS value?" typically zero in on somewhere in the 500 range after going through a long discussion of the pros and cons of larger vs. smaller RTS values.
