I decided to upgrade one of my ap’s and start using the rts/cts in 3.18 and the wireless test. I set it at the access point (not sure I really had to do this) and then started to upgrade and set it at the clients. It worked fine for 5 out of 6 client radios, but the 6th one died after putting in the command:
/interface wireless set 0 hw-protection-mode=rts-cts
After a site visit, I found that it just won’t connect with it on, but connects fine without.
Signal levels are very good in the radio, so no issue there.
I observed similar problem. After I set hw-protection-mode=rts-cts on a RB411 station it disconnected and never connected again until the rts-cts on it was set back to none. But I never seen it again and all stations on the AP (30+) was set to rts-cts (changes made remotely). Even the station with problem connected properly. The only difference in settings was that hw-protection-threshold was not left 0 but set to 500. I tried several RBs on desk but they connected with RTS enabled and threshold set to zero.
3.20 ROS version was used in our case.
BTW: it looks we solved poor CPE TX quality (going to 10% when multiple station were active) problem on this site using RTS.
We’ve got an increase in performance, but I’m not sure if it’s related to RTS/CTS or card change, because we were using R52H before and changed to R52 the same time we’ve started to test RTS