I broke a coaxial connector (CH0 2.4GHz) on the Xiaomi Mi Router 3G board...
There are still 3 functionnal antennas :
CH1 for 2.4GHz
CH0 and CH1 for 5GHz
I have no problem with 5GHz but the 2.4GHz is not good at all.
Is it possible to disable CH0 for 2.4GHz to have better performance ?
At least for 802.11n and "HT" modes, MCS 0-7 are single-stream modulations. It doesn't look like VHT is as easy to tell the difference between single- and multi-stream modulation from the MCS index alone.
I would have expected to see a "zero" for the first antenna there ("-95" or some other consistent number). I haven't looked into to the bitmaps for antennas in a while. You might want to look into https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf and what is generated on your machine in /tmp/run/
You also might try "poking at it" with iw -- from the help it provides
phy <phyname> set antenna <bitmap> | all | <tx bitmap> <rx bitmap>
Set a bitmap of allowed antennas to use for TX and RX.
The driver may reject antenna configurations it cannot support.
Also, the values could be listed with something like
iw phy phy1 info | head -n20
Wiphy phy1
max # scan SSIDs: 16
max scan IEs length: 195 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* monitor
* mesh point
When I try to set the antenna on my device, it fails -- you might want to check your logs.
jeff@office:~$ sudo iw phy phy1 set antenna 0x2
command failed: Not supported (-95)
The copper live trace is right there below where the pad ripped off. Taking the board out of the frame will show it better. That's very fixable by someone with experience at such things.
WN823N uses a Realtek chip which tends to be not well supported. Any USB adapter is limited by the bus bandwidth and latency so it won't work as well as a chip with an internal or PCI connection.
you should patch driver to force it to 1x1 mode as userspace tools generally won't support it. since you damaged main chain that might be a bit tricky. or you can keep scratching until you break something else