Just my 5 cents. What I have understood about 802.11 a/b/g/n/ac , and its working.
Basic rate: this transmission is not checked with a received ACK from the other side. The rate must be chosen to allow for a guaranteed delivery.
AP's send their capability and SSID information as beacons. Mostly every 100ms. These beacons are necessary for the clients to negotiate supported rates and encoding. (Among other things)
Clients send probes to find AP's that are not broadcasting their SSID
Broadcast and multicast traffic is sent at basic rate.
The association/ disassociation and values of the connection are sent at basic rate.
RTS/CTS and other control packets are sent at basic rate
So for "Basic rate" one has to choose the highest possible rate but still maintain 100% delivery to all stations.
Supported rates: are the possible usable rates for ACKed unicasts. They may fail. The "hw_retries" attempts will be made to still deliver it. If this fails the transmission is stepped down to next lower common supported rate. Again "hw_retries" times retry until it is delivered. If it fails again then we step down again. If we are at the lowest supported rate and it fails , we try 2 more time ( 3 x hw_retries in total). If it still failed, then the "Disconnect Timeout" timer starts. During this disconnect timeout we will retry every "On fail retry time". If it still fails there is disconnect.
If it succeeds we go on with the next packet. If it succeeds 3 times in a row (not sure about this number 3 ) we step up to the next higher common supported rate.
This dynamic rate state is recorded per station in the AP, for TX and RX. (See the "wireless registration" TXrate and RXrate for these live values in the AP, or in the status of the wlan in the station)
This all is the basis for setting the advanced parameters in MKT (HW_retries, Disconnect timeout, On fail retry time)
But at the rate settings be careful !
There are different sets.per 802.11 generation, and sometimes we set things like b/g/n, a/n/ac, g/n/ac, n-only, g-only mode. The mixed modes are tricky because they not only use more rate sets but also for n use other packets if "mixed" versus "greenfield". Also these higher modes are downward compatible.
The rate sets used are:
- special set from 1-11 Mbps for "b"
-set from 6 till 54 Mbps for "a" and "g"
- HT MCS rates for "n"
-VHT MCS rates for "ac"
Klembord-2.jpg
You can configure it, or set it to default. If set to default the tick changes while in config are not used, but the default ones. (Needs to be checked if the implementation is that way or not).
MCS0 corresponds to 6.5 Mbps. It rises up to MCS7, then MCS8 is MCS0 on 2 spatial stream .... etc etc (
http://mcsindex.com/)
Klembord-3.jpg
802.11n lets us play a lot with supported and basic rates. Removing higher rates for stability is common practice. Removing lower rates is tricky, as it will introduce more disconnects.(See earlier rate selector algoritm) What do you prefer, slowing down due to an interference burst or poor temporary condition and recover, or lose connection ?
I did not figure out the "basic rate" selector algoritme yet for MKT, if there is more than one basic rate. (Wireshark could tell)
"ac" uses VHT MCS rates , but they greatly reduced the 802.11 overhead by limiting the room to play. The rate announcement data has now only a small space in the beacon to send this. The only values are , one per chain, "None/MCS 0-7/MCS 0-9" The selection panel only comes visible when "configured" is activated, and on an "ac" capable wlan. Removing lower rates is clearly not possible nor wanted.
Klembord-4.jpg
You do not have the required permissions to view the files attached to this post.