/interface wireless registration-table print stats
rx-rate="104Mbps-20MHz/2S"
tx-rate="78Mbps-20MHz/2S"
frames=39020,3177 hw-frames=53631,3440
signal-strength=-58dBm@6Mbps signal-to-noise=55dB
signal-strength-ch0=-63dBm signal-strength-ch1=-60dBm tx-signal-strength-ch0=-79dBm tx-signal-strength-ch1=-65dBm
strength-at-rates=-58dBm@HT20-7 9s10ms
tx-signal-strength=-65dBm
tx-ccq=85% rx-ccq=85% p-throughput=53459
authentication-type=wpa2-psk encryption=aes-ccm group-encryption=aes-ccm
tx-rate-set="CCK:1-11 OFDM:6-54 BW:1x HT:0-15"
Lets read this .... most is good to very good
rx-rate="104Mbps-20MHz/2S"
tx-rate="78Mbps-20MHz/2S"
Ok that's the interface rate, data rate through this is normally limited to 50-60% because of unavoidable 802.11 overhead. So 50-40 Mbps is expected max.
Dual stream (2S) is used. Theorethical max is 144Mbps
interface rate (but that needs SGI, else here it is 130Mbps). 80 Mbps
data rate is almost impossible.
frames=39020,3177 hw-frames=53631,3440
We have re-transmits. Some data packages are sent multiple times before they are acknowledged.
This reduces the effective data throughput here to 39/53 of the max possible above 39/53 * 50 =
rx 36 Mbps - tx 29 Mbps
This is also the reason why the interface rate is reduced from MCS15 down till some more stable encoding is reached. (MCS 13 and 12 : see
http://mcsindex.com/ )
Signal strength is OK
tx-ccq=85% rx-ccq=85% p-throughput=53459
CCQ Calculated from other statistics. p-throughput looks optimistic (did it not account for retransmits?) 53Mbps expected max as per RouterOS. Will be reduced by retransmits.
Rest is OK.
Not available with RouterOS is info about the contention for air-time/transmit time. (% channel busy) This will also again reduce the effective max data rate. (Co-channel coexistence/interference)
(Freq Usage: could be an indication for channel busy, but this is not real time). High signal to noise suggests here no adjacent channel interference.
Real usage (not only UDP test)
Bi-directional will split the airtime and data rate for tx and rx. TCP is always somewhat bi-directional (ACK must be sent)
TCP congestion avoidance (in the client device) might further reduce the TCP performance.