Neither Stable 3.23.4.0 nor Nightly 20230709 attempts 802.11n nor 802.11ac speeds.
Using Nightly 20230709
My -nD to nD devices are capable of 130/144 TxMbps link speed.
My -ac to -ac and -nD to -ac only attempt 802.11g speeds!
I was hoping to see a MCS8 156/173.3 link between my -ac devices.
Especially, I was not expecting to be reduced to 802.11g, 54 TxMbps.
See
http://gelm.net/AREDN/whence-ac.html
edited.
73, Chuck
54 TxMbps is not a possible 802.11n-ac speed.
https://d2cpnw0u24fjm4.cloudfront.net/wp-content/uploads/2020/09/11102924/802.11n-and-802.11ac-MCS-Chart-1.pdf
73, Chuck
Orv W6BI
Hi, Orv:
As advertised in "See http://gelm.net/AREDN/whence-ac.html edited":
802.11n MCSs are not attempted, only 802.11g speeds are attempted.
It seems to me that my 802.11n device (RB-LHG-HP5nd) thinks that my RB-SXTsq-5ac device is an 802.11g device.
Why else would only be testing and linking at 802.11g MCSs?
Also note that the LQ and NLQ are all 100%, so there is no multiplication with values < 1.0 happening.
?
73, Chuck
73
Orv
Yes.
TxMbps 54: Multiple firmware versions => 3.23.4.0, 202308??
I tried to load iperfspeed_0.8, but is seems to be failing to load on the Nightly.
Now, even my GL iNet AR300M16 is doing 54 Mbps with the Nightly.
:-|
73, Chuck
Yes, TxMbps is is a data speed, not data throughput speed.
TxMbps indicates the link speed (MCS) less retries (if any).
iperfspeed would indicate throughput (TxMpbs)*(LQ/100)*(NLQ/100)-overhead(FEC,...)
These are half-duplex radio links so throughput can only approach MCS speed selected.
I am looking at rc_stats and wondering if my new 'ac' device broadcasts that it can do 802.11 encoding.
?
73, Chuck