NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CTS/RTS and "hidden node problem"
Hey all I have my CTS/RTS value set to 2100. I recently changed the setup on the RBK752 to use a wired backhaul (15m CAT6a run). I've reduced 2.4Ghz power to 25% and 5Ghz power to 50%. I have ...
Jimbo84 wrote:If I were wanting to try and keep all devices "happy" (especially mobile calls over WiFi) would your advice be to have a lower CTS/RTS value to help in this situation. As voice data is real-time and can't be re-transmitted I guess having that "all clear to send" is a good thing?
Are you experiencing a problem with devices on your network and that you're trying to resolve with these adjustments? If not, then I recommend not trying to fiddle with your settings or else you're not able to detect if you're making things worse vs. better.
For most Orbi customers the default settings are fine and if they are not experiencing issues with their wireless network, they don't need to go into the Advanced Settings and make changes to things like CTS/RTS Threshold.
Hi Mikey94025 - yes originally I was trying to fix the issue with WiFi calling on the Orbi kit.
Do you happen to recall what the default value is for CTS/RTS? I'm happy to put this back to default to begin with and see how things pan out.
Thanks.
Jimbo84 wrote:
Hi Mikey94025 - yes originally I was trying to fix the issue with WiFi calling on the Orbi kit.
Do you happen to recall what the default value is for CTS/RTS? I'm happy to put this back to default to begin with and see how things pan out.
There appears to be no single default value for CTS/RTS. On the original Orbi, the default value was 2347 (the maximum possible). When the AX product came out, the default was set to 64. I have a memory that someone spoke to a Netgear engineer who said something along the line of... "our lab environment had so much WiFi going on that we had to set the value to 64 to get things to work." This indicates (to me) that there is no value that is best for every situation. (If there actually is a best value, then Netgear would set the default to that and not let customers change it.)
Jimbo84 wrote:Do you happen to recall what the default value is for CTS/RTS? I'm happy to put this back to default to begin with and see how things pan out.
I would recommend 2347. If you have problems then try 64.
For wi-fi calling issues also try:
- Disable SIP ALG: https://community.netgear.com/t5/Orbi/Wifi-calling-and-Orbi-on-iPhone/m-p/1742153#M60248
- Make sure you don't have Double NAT: https://community.netgear.com/t5/Orbi/AT-amp-T-Wifi-Calling/m-p/1876908#M85177
Thanks both.
Yesterday I tried 64 but I noticed some "funnies" with the network afterwards. Delays in sending WhatsApp messages from my phone, some weird WiFi printing issues. So I reverted it back to 2347. I'll keep an eye / a note / on how things go.
Mikey94025thanks for the links. Just to confirm that I have SIP ALG disabled (on both the Orbi and my Edge Router). I also have NAT set to "open" on the Orbi as my Edge Router has the NAT "enabled". I run both the Orbi and Edge Router in "Router Mode". I just chose to manually have the Edge Router configured (i.e. DHCP, WiFi, NAT, and so forth - all disabled).
