Open morrownr opened 2 years ago
This is my results (openwrt in the rpi400 and CF-953AX)
root@OpenWrtRpi400:~# iw reg get
global
country FR: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
(57000 - 71000 @ 2160), (N/A, 40), (N/A)
root@OpenWrtRpi400:~# iw reg set GR
root@OpenWrtRpi400:~# iw reg get
global
country GR: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
I'm feeling a sudden urge to both jailbreak this thing AND put a 2kW hamradio linear amplifier just to make a statement...
(5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
Hmmm...
@yaslama
Which version of OpenWRT are you using?
Are you able to use the 953AX as an AP with 6 GHz?
Which version of OpenWRT are you using?
root@OpenWrtRpi400:~# cat /etc/openwrt_version
r20156-0f301b0b1d
root@OpenWrtRpi400:~# cat /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='SNAPSHOT'
DISTRIB_REVISION='r20156-0f301b0b1d'
DISTRIB_TARGET='bcm27xx/bcm2711'
DISTRIB_ARCH='aarch64_cortex-a72'
DISTRIB_DESCRIPTION='OpenWrt SNAPSHOT r20156-0f301b0b1d'
DISTRIB_TAINTS=''
Are you able to use the 953AX as an AP with 6 GHz?
root@OpenWrtRpi400:~# iw dev wlan0 info
Interface wlan0
ifindex 37
wdev 0x12
addr e0:e1:a9:34:a6:d1
ssid testssid6
type AP
wiphy 0
channel 53 (6215 MHz), width: 80 MHz, center1: 6225 MHz
txpower 3.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
0 0 0 0 0 0 0 0 0
The AP is configured but I still wasn't able to connect to it (at 5Ghz it was ok). I see the the ssid but, the the connection fails. I ordered some 7921k m.2 cards to test.
My WDR4300 with OpenWRT 22.03 and kernel 5.10 is much more liberal, even has the mt7921u module and is loading it to the correct USB device, but iw
isn't recognizing it for some reason. Probably the USB2.0 port? I can try flashing the nightly snapshot of OpenWRT into the RPi4B.
root@heimdall:~# iw reg get
global
country US: DFS-FCC
(902 - 904 @ 2), (N/A, 30), (N/A)
(904 - 920 @ 16), (N/A, 30), (N/A)
(920 - 928 @ 8), (N/A, 30), (N/A)
(2400 - 2472 @ 40), (N/A, 30), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
(5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS
(5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW
(5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN
(5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN
(57240 - 71000 @ 2160), (N/A, 40), (N/A)
phy#2
country US: DFS-FCC
(902 - 904 @ 2), (N/A, 30), (N/A)
(904 - 920 @ 16), (N/A, 30), (N/A)
(920 - 928 @ 8), (N/A, 30), (N/A)
(2400 - 2472 @ 40), (N/A, 30), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
(5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS
(5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW
(5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN
(5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN
(57240 - 71000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(902 - 904 @ 2), (N/A, 30), (N/A)
(904 - 920 @ 16), (N/A, 30), (N/A)
(920 - 928 @ 8), (N/A, 30), (N/A)
(2400 - 2472 @ 40), (N/A, 30), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
(5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS
(5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW
(5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN
(5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN
(57240 - 71000 @ 2160), (N/A, 40), (N/A)
My WDR4300 with OpenWRT 22.03 and kernel 5.10 is much more liberal, even has the mt7921u module...
I'm running 22.03 on my Zyxel wifi router. I had not thought to check for the driver since it is running kernel 5.10. I smell a backport:
kmod-mt7921u
Probably the USB2.0 port?
I doubt it. Is the firmware installed?
Done.
Before setting region on nightly snapshot of x86_64 OpenWRT:
root@OpenWrt:~# iw reg get
global
country 00: DFS-UNSET
(755 - 928 @ 2), (N/A, 20), (N/A), PASSIVE-SCAN
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
(5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
(5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
(5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
(57240 - 63720 @ 2160), (N/A, 0), (N/A)
root@OpenWrt:~# iw list
Wiphy phy0
wiphy index: 0
max # scan SSIDs: 4
max scan IEs length: 482 bytes
max # sched scan SSIDs: 10
max # match sets: 16
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Device supports T-DLS.
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* managed
* AP
* AP/VLAN
* monitor
Band 1:
Capabilities: 0x9ff
RX LDPC
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: No restriction (0x00)
HT TX/RX MCS rate indexes supported: 0-15
HE Iftypes: managed
HE MAC Capabilities (0x08011a000040):
+HTC HE Supported
Trigger Frame MAC Padding Duration: 2
OM Control
Maximum A-MPDU Length Exponent: 3
A-MSDU in A-MPDU
HE PHY Capabilities: (0x2270ce120dc0b306423f00):
HE40/2.4GHz
242 tone RUs/2.4GHz
Device Class: 1
LDPC Coding in Payload
HE SU PPDU with 1x HE-LTF and 0.8us GI
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
SU Beamformee
Beamformee STS <= 80Mhz: 3
Ng = 16 SU Feedback
Ng = 16 MU Feedback
Codebook Size SU Feedback
Codebook Size MU Feedback
Triggered CQI Feedback
Partial Bandwidth Extended Range
PPE Threshold Present
Power Boost Factor ar
HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
20MHz in 40MHz HE PPDU 2.4GHz
DCM Max BW: 1
Longer Than 16HE SIG-B OFDM Symbols
Non-Triggered CQI Feedback
TX 1024-QAM
RX 1024-QAM
RX Full BW SU Using HE MU PPDU with Compression SIGB
RX Full BW SU Using HE MU PPDU with Non-Compression SIGB
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: managed
EHT MAC Capabilities (0x0000):
EHT PHY Capabilities: (0x0000000000000000):
EHT MCS/NSS: (0x):
EHT bw=20 MHz, max NSS for MCS 0-7: Rx=0, Tx=0
EHT bw=20 MHz, max NSS for MCS 8-9: Rx=0, Tx=0
EHT bw=20 MHz, max NSS for MCS 10-11: Rx=0, Tx=0
EHT bw=20 MHz, max NSS for MCS 12-13: Rx=0, Tx=0
HE Iftypes: AP
HE MAC Capabilities (0x00011a081044):
+HTC HE Supported
BSR
OM Control
Maximum A-MPDU Length Exponent: 3
BQR
A-MSDU in A-MPDU
OM Control UL MU Data Disable RX
HE PHY Capabilities: (0x0220ce120000a000000c00):
HE40/2.4GHz
LDPC Coding in Payload
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
Partial Bandwidth Extended Range
PPE Threshold Present
TX 1024-QAM
RX 1024-QAM
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: AP
EHT MAC Capabilities (0x0000):
EHT PHY Capabilities: (0x0000000000000000):
EHT MCS/NSS: (0x):
EHT bw=20 MHz, max NSS for MCS 0-7: Rx=0, Tx=0
EHT bw=20 MHz, max NSS for MCS 8-9: Rx=0, Tx=0
EHT bw=20 MHz, max NSS for MCS 10-11: Rx=0, Tx=0
EHT bw=20 MHz, max NSS for MCS 12-13: Rx=0, Tx=0
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm) (no IR)
* 2472 MHz [13] (20.0 dBm) (no IR)
* 2484 MHz [14] (20.0 dBm) (no IR)
Band 2:
Capabilities: 0x9ff
RX LDPC
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: No restriction (0x00)
HT TX/RX MCS rate indexes supported: 0-15
VHT Capabilities (0x339071b2):
Max MPDU length: 11454
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
TX STBC
SU Beamformee
MU Beamformee
RX antenna pattern consistency
TX antenna pattern consistency
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
VHT extended NSS: supported
HE Iftypes: managed
HE MAC Capabilities (0x08011a000040):
+HTC HE Supported
Trigger Frame MAC Padding Duration: 2
OM Control
Maximum A-MPDU Length Exponent: 3
A-MSDU in A-MPDU
HE PHY Capabilities: (0x4470ce120dc0b306423f00):
HE40/HE80/5GHz
242 tone RUs/5GHz
Device Class: 1
LDPC Coding in Payload
HE SU PPDU with 1x HE-LTF and 0.8us GI
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
SU Beamformee
Beamformee STS <= 80Mhz: 3
Ng = 16 SU Feedback
Ng = 16 MU Feedback
Codebook Size SU Feedback
Codebook Size MU Feedback
Triggered CQI Feedback
Partial Bandwidth Extended Range
PPE Threshold Present
Power Boost Factor ar
HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
20MHz in 40MHz HE PPDU 2.4GHz
DCM Max BW: 1
Longer Than 16HE SIG-B OFDM Symbols
Non-Triggered CQI Feedback
TX 1024-QAM
RX 1024-QAM
RX Full BW SU Using HE MU PPDU with Compression SIGB
RX Full BW SU Using HE MU PPDU with Non-Compression SIGB
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: managed
EHT MAC Capabilities (0x0000):
EHT PHY Capabilities: (0x0000000000000000):
EHT MCS/NSS: (0x):
EHT bw <= 80 MHz, max NSS for MCS 8-9: Rx=0, Tx=0
EHT bw <= 80 MHz, max NSS for MCS 10-11: Rx=0, Tx=0
EHT bw <= 80 MHz, max NSS for MCS 12-13: Rx=0, Tx=0
HE Iftypes: AP
HE MAC Capabilities (0x00011a081044):
+HTC HE Supported
BSR
OM Control
Maximum A-MPDU Length Exponent: 3
BQR
A-MSDU in A-MPDU
OM Control UL MU Data Disable RX
HE PHY Capabilities: (0x0420ce120000a000000c00):
HE40/HE80/5GHz
LDPC Coding in Payload
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
Partial Bandwidth Extended Range
PPE Threshold Present
TX 1024-QAM
RX 1024-QAM
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: AP
EHT MAC Capabilities (0x0000):
EHT PHY Capabilities: (0x0000000000000000):
EHT MCS/NSS: (0x):
EHT bw <= 80 MHz, max NSS for MCS 8-9: Rx=0, Tx=0
EHT bw <= 80 MHz, max NSS for MCS 10-11: Rx=0, Tx=0
EHT bw <= 80 MHz, max NSS for MCS 12-13: Rx=0, Tx=0
Frequencies:
* 5180 MHz [36] (20.0 dBm)
* 5200 MHz [40] (20.0 dBm)
* 5220 MHz [44] (20.0 dBm)
* 5240 MHz [48] (20.0 dBm)
* 5260 MHz [52] (20.0 dBm) (no IR, radar detection)
* 5280 MHz [56] (20.0 dBm) (no IR, radar detection)
* 5300 MHz [60] (20.0 dBm) (no IR, radar detection)
* 5320 MHz [64] (20.0 dBm) (no IR, radar detection)
* 5500 MHz [100] (20.0 dBm) (no IR, radar detection)
* 5520 MHz [104] (20.0 dBm) (no IR, radar detection)
* 5540 MHz [108] (20.0 dBm) (no IR, radar detection)
* 5560 MHz [112] (20.0 dBm) (no IR, radar detection)
* 5580 MHz [116] (20.0 dBm) (no IR, radar detection)
* 5600 MHz [120] (20.0 dBm) (no IR, radar detection)
* 5620 MHz [124] (20.0 dBm) (no IR, radar detection)
* 5640 MHz [128] (20.0 dBm) (no IR, radar detection)
* 5660 MHz [132] (20.0 dBm) (no IR, radar detection)
* 5680 MHz [136] (20.0 dBm) (no IR, radar detection)
* 5700 MHz [140] (20.0 dBm) (no IR, radar detection)
* 5720 MHz [144] (20.0 dBm) (no IR, radar detection)
* 5745 MHz [149] (20.0 dBm) (no IR)
* 5765 MHz [153] (20.0 dBm) (no IR)
* 5785 MHz [157] (20.0 dBm) (no IR)
* 5805 MHz [161] (20.0 dBm) (no IR)
* 5825 MHz [165] (20.0 dBm) (no IR)
* 5845 MHz [169] (disabled)
* 5865 MHz [173] (disabled)
Band 4:
HE Iftypes: managed
HE MAC Capabilities (0x08011a000040):
+HTC HE Supported
Trigger Frame MAC Padding Duration: 2
OM Control
Maximum A-MPDU Length Exponent: 3
A-MSDU in A-MPDU
HE PHY Capabilities: (0x4470ce120dc0b306423f00):
HE40/HE80/5GHz
242 tone RUs/5GHz
Device Class: 1
LDPC Coding in Payload
HE SU PPDU with 1x HE-LTF and 0.8us GI
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
SU Beamformee
Beamformee STS <= 80Mhz: 3
Ng = 16 SU Feedback
Ng = 16 MU Feedback
Codebook Size SU Feedback
Codebook Size MU Feedback
Triggered CQI Feedback
Partial Bandwidth Extended Range
PPE Threshold Present
Power Boost Factor ar
HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
20MHz in 40MHz HE PPDU 2.4GHz
DCM Max BW: 1
Longer Than 16HE SIG-B OFDM Symbols
Non-Triggered CQI Feedback
TX 1024-QAM
RX 1024-QAM
RX Full BW SU Using HE MU PPDU with Compression SIGB
RX Full BW SU Using HE MU PPDU with Non-Compression SIGB
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: managed
EHT MAC Capabilities (0x0000):
EHT PHY Capabilities: (0x0000000000000000):
EHT MCS/NSS: (0x):
EHT bw <= 80 MHz, max NSS for MCS 8-9: Rx=0, Tx=0
EHT bw <= 80 MHz, max NSS for MCS 10-11: Rx=0, Tx=0
EHT bw <= 80 MHz, max NSS for MCS 12-13: Rx=0, Tx=0
HE Iftypes: AP
HE MAC Capabilities (0x00011a081044):
+HTC HE Supported
BSR
OM Control
Maximum A-MPDU Length Exponent: 3
BQR
A-MSDU in A-MPDU
OM Control UL MU Data Disable RX
HE PHY Capabilities: (0x0420ce120000a000000c00):
HE40/HE80/5GHz
LDPC Coding in Payload
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
Partial Bandwidth Extended Range
PPE Threshold Present
TX 1024-QAM
RX 1024-QAM
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: AP
EHT MAC Capabilities (0x0000):
EHT PHY Capabilities: (0x0000000000000000):
EHT MCS/NSS: (0x):
EHT bw <= 80 MHz, max NSS for MCS 8-9: Rx=0, Tx=0
EHT bw <= 80 MHz, max NSS for MCS 10-11: Rx=0, Tx=0
EHT bw <= 80 MHz, max NSS for MCS 12-13: Rx=0, Tx=0
Frequencies:
* 5955 MHz [1] (disabled)
* 5975 MHz [5] (disabled)
* 5995 MHz [9] (disabled)
* 6015 MHz [13] (disabled)
* 6035 MHz [17] (disabled)
* 6055 MHz [21] (disabled)
* 6075 MHz [25] (disabled)
* 6095 MHz [29] (disabled)
* 6115 MHz [33] (disabled)
* 6135 MHz [37] (disabled)
* 6155 MHz [41] (disabled)
* 6175 MHz [45] (disabled)
* 6195 MHz [49] (disabled)
* 6215 MHz [53] (disabled)
* 6235 MHz [57] (disabled)
* 6255 MHz [61] (disabled)
* 6275 MHz [65] (disabled)
* 6295 MHz [69] (disabled)
* 6315 MHz [73] (disabled)
* 6335 MHz [77] (disabled)
* 6355 MHz [81] (disabled)
* 6375 MHz [85] (disabled)
* 6395 MHz [89] (disabled)
* 6415 MHz [93] (disabled)
* 6435 MHz [97] (disabled)
* 6455 MHz [101] (disabled)
* 6475 MHz [105] (disabled)
* 6495 MHz [109] (disabled)
* 6515 MHz [113] (disabled)
* 6535 MHz [117] (disabled)
* 6555 MHz [121] (disabled)
* 6575 MHz [125] (disabled)
* 6595 MHz [129] (disabled)
* 6615 MHz [133] (disabled)
* 6635 MHz [137] (disabled)
* 6655 MHz [141] (disabled)
* 6675 MHz [145] (disabled)
* 6695 MHz [149] (disabled)
* 6715 MHz [153] (disabled)
* 6735 MHz [157] (disabled)
* 6755 MHz [161] (disabled)
* 6775 MHz [165] (disabled)
* 6795 MHz [169] (disabled)
* 6815 MHz [173] (disabled)
* 6835 MHz [177] (disabled)
* 6855 MHz [181] (disabled)
* 6875 MHz [185] (disabled)
* 6895 MHz [189] (disabled)
* 6915 MHz [193] (disabled)
* 6935 MHz [197] (disabled)
* 6955 MHz [201] (disabled)
* 6975 MHz [205] (disabled)
* 6995 MHz [209] (disabled)
* 7015 MHz [213] (disabled)
* 7035 MHz [217] (disabled)
* 7055 MHz [221] (disabled)
* 7075 MHz [225] (disabled)
* 7095 MHz [229] (disabled)
* 7115 MHz [233] (disabled)
valid interface combinations:
* #{ managed } <= 4, #{ AP } <= 1,
total <= 4, #channels <= 1, STA/AP BI must match
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
max # scan plans: 1
max scan plan interval: 65535
max scan plan iterations: 0
Supported extended features:
* [ RRM ]: RRM
* [ SET_SCAN_DWELL ]: scan dwell setting
* [ BEACON_RATE_LEGACY ]: legacy beacon rate setting
* [ BEACON_RATE_HT ]: HT beacon rate setting
* [ BEACON_RATE_VHT ]: VHT beacon rate setting
* [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
* [ AIRTIME_FAIRNESS ]: airtime fairness scheduling
* [ AQL ]: Airtime Queue Limits (AQL)
* [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
* [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
* [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support
* [ BEACON_RATE_HE ]: HE beacon rate support (AP/mesh)
After setting US:
root@OpenWrt:~# iw reg set US
root@OpenWrt:~# iw reg get
global
country US: DFS-FCC
(902 - 904 @ 2), (N/A, 30), (N/A)
(904 - 920 @ 16), (N/A, 30), (N/A)
(920 - 928 @ 8), (N/A, 30), (N/A)
(2400 - 2472 @ 40), (N/A, 30), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
(5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS
(5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW
(5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN
(5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN
(57240 - 71000 @ 2160), (N/A, 40), (N/A)
root@OpenWrt:~# iw list
Wiphy phy0
wiphy index: 0
max # scan SSIDs: 4
max scan IEs length: 482 bytes
max # sched scan SSIDs: 10
max # match sets: 16
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Device supports T-DLS.
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* managed
* AP
* AP/VLAN
* monitor
Band 1:
Capabilities: 0x9ff
RX LDPC
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: No restriction (0x00)
HT TX/RX MCS rate indexes supported: 0-15
HE Iftypes: managed
HE MAC Capabilities (0x08011a000040):
+HTC HE Supported
Trigger Frame MAC Padding Duration: 2
OM Control
Maximum A-MPDU Length Exponent: 3
A-MSDU in A-MPDU
HE PHY Capabilities: (0x2270ce120dc0b306423f00):
HE40/2.4GHz
242 tone RUs/2.4GHz
Device Class: 1
LDPC Coding in Payload
HE SU PPDU with 1x HE-LTF and 0.8us GI
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
SU Beamformee
Beamformee STS <= 80Mhz: 3
Ng = 16 SU Feedback
Ng = 16 MU Feedback
Codebook Size SU Feedback
Codebook Size MU Feedback
Triggered CQI Feedback
Partial Bandwidth Extended Range
PPE Threshold Present
Power Boost Factor ar
HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
20MHz in 40MHz HE PPDU 2.4GHz
DCM Max BW: 1
Longer Than 16HE SIG-B OFDM Symbols
Non-Triggered CQI Feedback
TX 1024-QAM
RX 1024-QAM
RX Full BW SU Using HE MU PPDU with Compression SIGB
RX Full BW SU Using HE MU PPDU with Non-Compression SIGB
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: managed
EHT MAC Capabilities (0x0000):
EHT PHY Capabilities: (0x0000000000000000):
EHT MCS/NSS: (0x):
EHT bw=20 MHz, max NSS for MCS 0-7: Rx=0, Tx=0
EHT bw=20 MHz, max NSS for MCS 8-9: Rx=0, Tx=0
EHT bw=20 MHz, max NSS for MCS 10-11: Rx=0, Tx=0
EHT bw=20 MHz, max NSS for MCS 12-13: Rx=0, Tx=0
HE Iftypes: AP
HE MAC Capabilities (0x00011a081044):
+HTC HE Supported
BSR
OM Control
Maximum A-MPDU Length Exponent: 3
BQR
A-MSDU in A-MPDU
OM Control UL MU Data Disable RX
HE PHY Capabilities: (0x0220ce120000a000000c00):
HE40/2.4GHz
LDPC Coding in Payload
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
Partial Bandwidth Extended Range
PPE Threshold Present
TX 1024-QAM
RX 1024-QAM
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: AP
EHT MAC Capabilities (0x0000):
EHT PHY Capabilities: (0x0000000000000000):
EHT MCS/NSS: (0x):
EHT bw=20 MHz, max NSS for MCS 0-7: Rx=0, Tx=0
EHT bw=20 MHz, max NSS for MCS 8-9: Rx=0, Tx=0
EHT bw=20 MHz, max NSS for MCS 10-11: Rx=0, Tx=0
EHT bw=20 MHz, max NSS for MCS 12-13: Rx=0, Tx=0
Frequencies:
* 2412 MHz [1] (30.0 dBm)
* 2417 MHz [2] (30.0 dBm)
* 2422 MHz [3] (30.0 dBm)
* 2427 MHz [4] (30.0 dBm)
* 2432 MHz [5] (30.0 dBm)
* 2437 MHz [6] (30.0 dBm)
* 2442 MHz [7] (30.0 dBm)
* 2447 MHz [8] (30.0 dBm)
* 2452 MHz [9] (30.0 dBm)
* 2457 MHz [10] (30.0 dBm)
* 2462 MHz [11] (30.0 dBm)
* 2467 MHz [12] (disabled)
* 2472 MHz [13] (disabled)
* 2484 MHz [14] (disabled)
Band 2:
Capabilities: 0x9ff
RX LDPC
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: No restriction (0x00)
HT TX/RX MCS rate indexes supported: 0-15
VHT Capabilities (0x339071b2):
Max MPDU length: 11454
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
TX STBC
SU Beamformee
MU Beamformee
RX antenna pattern consistency
TX antenna pattern consistency
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
VHT extended NSS: supported
HE Iftypes: managed
HE MAC Capabilities (0x08011a000040):
+HTC HE Supported
Trigger Frame MAC Padding Duration: 2
OM Control
Maximum A-MPDU Length Exponent: 3
A-MSDU in A-MPDU
HE PHY Capabilities: (0x4470ce120dc0b306423f00):
HE40/HE80/5GHz
242 tone RUs/5GHz
Device Class: 1
LDPC Coding in Payload
HE SU PPDU with 1x HE-LTF and 0.8us GI
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
SU Beamformee
Beamformee STS <= 80Mhz: 3
Ng = 16 SU Feedback
Ng = 16 MU Feedback
Codebook Size SU Feedback
Codebook Size MU Feedback
Triggered CQI Feedback
Partial Bandwidth Extended Range
PPE Threshold Present
Power Boost Factor ar
HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
20MHz in 40MHz HE PPDU 2.4GHz
DCM Max BW: 1
Longer Than 16HE SIG-B OFDM Symbols
Non-Triggered CQI Feedback
TX 1024-QAM
RX 1024-QAM
RX Full BW SU Using HE MU PPDU with Compression SIGB
RX Full BW SU Using HE MU PPDU with Non-Compression SIGB
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: managed
EHT MAC Capabilities (0x0000):
EHT PHY Capabilities: (0x0000000000000000):
EHT MCS/NSS: (0x):
EHT bw <= 80 MHz, max NSS for MCS 8-9: Rx=0, Tx=0
EHT bw <= 80 MHz, max NSS for MCS 10-11: Rx=0, Tx=0
EHT bw <= 80 MHz, max NSS for MCS 12-13: Rx=0, Tx=0
HE Iftypes: AP
HE MAC Capabilities (0x00011a081044):
+HTC HE Supported
BSR
OM Control
Maximum A-MPDU Length Exponent: 3
BQR
A-MSDU in A-MPDU
OM Control UL MU Data Disable RX
HE PHY Capabilities: (0x0420ce120000a000000c00):
HE40/HE80/5GHz
LDPC Coding in Payload
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
Partial Bandwidth Extended Range
PPE Threshold Present
TX 1024-QAM
RX 1024-QAM
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: AP
EHT MAC Capabilities (0x0000):
EHT PHY Capabilities: (0x0000000000000000):
EHT MCS/NSS: (0x):
EHT bw <= 80 MHz, max NSS for MCS 8-9: Rx=0, Tx=0
EHT bw <= 80 MHz, max NSS for MCS 10-11: Rx=0, Tx=0
EHT bw <= 80 MHz, max NSS for MCS 12-13: Rx=0, Tx=0
Frequencies:
* 5180 MHz [36] (23.0 dBm)
* 5200 MHz [40] (23.0 dBm)
* 5220 MHz [44] (23.0 dBm)
* 5240 MHz [48] (23.0 dBm)
* 5260 MHz [52] (24.0 dBm) (radar detection)
* 5280 MHz [56] (24.0 dBm) (radar detection)
* 5300 MHz [60] (24.0 dBm) (radar detection)
* 5320 MHz [64] (24.0 dBm) (radar detection)
* 5500 MHz [100] (24.0 dBm) (radar detection)
* 5520 MHz [104] (24.0 dBm) (radar detection)
* 5540 MHz [108] (24.0 dBm) (radar detection)
* 5560 MHz [112] (24.0 dBm) (radar detection)
* 5580 MHz [116] (24.0 dBm) (radar detection)
* 5600 MHz [120] (24.0 dBm) (radar detection)
* 5620 MHz [124] (24.0 dBm) (radar detection)
* 5640 MHz [128] (24.0 dBm) (radar detection)
* 5660 MHz [132] (24.0 dBm) (radar detection)
* 5680 MHz [136] (24.0 dBm) (radar detection)
* 5700 MHz [140] (24.0 dBm) (radar detection)
* 5720 MHz [144] (24.0 dBm) (radar detection)
* 5745 MHz [149] (30.0 dBm)
* 5765 MHz [153] (30.0 dBm)
* 5785 MHz [157] (30.0 dBm)
* 5805 MHz [161] (30.0 dBm)
* 5825 MHz [165] (30.0 dBm)
* 5845 MHz [169] (27.0 dBm) (no IR)
* 5865 MHz [173] (27.0 dBm) (no IR)
Band 4:
HE Iftypes: managed
HE MAC Capabilities (0x08011a000040):
+HTC HE Supported
Trigger Frame MAC Padding Duration: 2
OM Control
Maximum A-MPDU Length Exponent: 3
A-MSDU in A-MPDU
HE PHY Capabilities: (0x4470ce120dc0b306423f00):
HE40/HE80/5GHz
242 tone RUs/5GHz
Device Class: 1
LDPC Coding in Payload
HE SU PPDU with 1x HE-LTF and 0.8us GI
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
SU Beamformee
Beamformee STS <= 80Mhz: 3
Ng = 16 SU Feedback
Ng = 16 MU Feedback
Codebook Size SU Feedback
Codebook Size MU Feedback
Triggered CQI Feedback
Partial Bandwidth Extended Range
PPE Threshold Present
Power Boost Factor ar
HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
20MHz in 40MHz HE PPDU 2.4GHz
DCM Max BW: 1
Longer Than 16HE SIG-B OFDM Symbols
Non-Triggered CQI Feedback
TX 1024-QAM
RX 1024-QAM
RX Full BW SU Using HE MU PPDU with Compression SIGB
RX Full BW SU Using HE MU PPDU with Non-Compression SIGB
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: managed
EHT MAC Capabilities (0x0000):
EHT PHY Capabilities: (0x0000000000000000):
EHT MCS/NSS: (0x):
EHT bw <= 80 MHz, max NSS for MCS 8-9: Rx=0, Tx=0
EHT bw <= 80 MHz, max NSS for MCS 10-11: Rx=0, Tx=0
EHT bw <= 80 MHz, max NSS for MCS 12-13: Rx=0, Tx=0
HE Iftypes: AP
HE MAC Capabilities (0x00011a081044):
+HTC HE Supported
BSR
OM Control
Maximum A-MPDU Length Exponent: 3
BQR
A-MSDU in A-MPDU
OM Control UL MU Data Disable RX
HE PHY Capabilities: (0x0420ce120000a000000c00):
HE40/HE80/5GHz
LDPC Coding in Payload
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
Partial Bandwidth Extended Range
PPE Threshold Present
TX 1024-QAM
RX 1024-QAM
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: AP
EHT MAC Capabilities (0x0000):
EHT PHY Capabilities: (0x0000000000000000):
EHT MCS/NSS: (0x):
EHT bw <= 80 MHz, max NSS for MCS 8-9: Rx=0, Tx=0
EHT bw <= 80 MHz, max NSS for MCS 10-11: Rx=0, Tx=0
EHT bw <= 80 MHz, max NSS for MCS 12-13: Rx=0, Tx=0
Frequencies:
* 5955 MHz [1] (12.0 dBm) (no IR)
* 5975 MHz [5] (12.0 dBm) (no IR)
* 5995 MHz [9] (12.0 dBm) (no IR)
* 6015 MHz [13] (12.0 dBm) (no IR)
* 6035 MHz [17] (12.0 dBm) (no IR)
* 6055 MHz [21] (12.0 dBm) (no IR)
* 6075 MHz [25] (12.0 dBm) (no IR)
* 6095 MHz [29] (12.0 dBm) (no IR)
* 6115 MHz [33] (12.0 dBm) (no IR)
* 6135 MHz [37] (12.0 dBm) (no IR)
* 6155 MHz [41] (12.0 dBm) (no IR)
* 6175 MHz [45] (12.0 dBm) (no IR)
* 6195 MHz [49] (12.0 dBm) (no IR)
* 6215 MHz [53] (12.0 dBm) (no IR)
* 6235 MHz [57] (12.0 dBm) (no IR)
* 6255 MHz [61] (12.0 dBm) (no IR)
* 6275 MHz [65] (12.0 dBm) (no IR)
* 6295 MHz [69] (12.0 dBm) (no IR)
* 6315 MHz [73] (12.0 dBm) (no IR)
* 6335 MHz [77] (12.0 dBm) (no IR)
* 6355 MHz [81] (12.0 dBm) (no IR)
* 6375 MHz [85] (12.0 dBm) (no IR)
* 6395 MHz [89] (12.0 dBm) (no IR)
* 6415 MHz [93] (12.0 dBm) (no IR)
* 6435 MHz [97] (12.0 dBm) (no IR)
* 6455 MHz [101] (12.0 dBm) (no IR)
* 6475 MHz [105] (12.0 dBm) (no IR)
* 6495 MHz [109] (12.0 dBm) (no IR)
* 6515 MHz [113] (12.0 dBm) (no IR)
* 6535 MHz [117] (12.0 dBm) (no IR)
* 6555 MHz [121] (12.0 dBm) (no IR)
* 6575 MHz [125] (12.0 dBm) (no IR)
* 6595 MHz [129] (12.0 dBm) (no IR)
* 6615 MHz [133] (12.0 dBm) (no IR)
* 6635 MHz [137] (12.0 dBm) (no IR)
* 6655 MHz [141] (12.0 dBm) (no IR)
* 6675 MHz [145] (12.0 dBm) (no IR)
* 6695 MHz [149] (12.0 dBm) (no IR)
* 6715 MHz [153] (12.0 dBm) (no IR)
* 6735 MHz [157] (12.0 dBm) (no IR)
* 6755 MHz [161] (12.0 dBm) (no IR)
* 6775 MHz [165] (12.0 dBm) (no IR)
* 6795 MHz [169] (12.0 dBm) (no IR)
* 6815 MHz [173] (12.0 dBm) (no IR)
* 6835 MHz [177] (12.0 dBm) (no IR)
* 6855 MHz [181] (12.0 dBm) (no IR)
* 6875 MHz [185] (12.0 dBm) (no IR)
* 6895 MHz [189] (12.0 dBm) (no IR)
* 6915 MHz [193] (12.0 dBm) (no IR)
* 6935 MHz [197] (12.0 dBm) (no IR)
* 6955 MHz [201] (12.0 dBm) (no IR)
* 6975 MHz [205] (12.0 dBm) (no IR)
* 6995 MHz [209] (12.0 dBm) (no IR)
* 7015 MHz [213] (12.0 dBm) (no IR)
* 7035 MHz [217] (12.0 dBm) (no IR)
* 7055 MHz [221] (12.0 dBm) (no IR)
* 7075 MHz [225] (12.0 dBm) (no IR)
* 7095 MHz [229] (12.0 dBm) (no IR)
* 7115 MHz [233] (12.0 dBm) (no IR)
valid interface combinations:
* #{ managed } <= 4, #{ AP } <= 1,
total <= 4, #channels <= 1, STA/AP BI must match
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
max # scan plans: 1
max scan plan interval: 65535
max scan plan iterations: 0
Supported extended features:
* [ RRM ]: RRM
* [ SET_SCAN_DWELL ]: scan dwell setting
* [ BEACON_RATE_LEGACY ]: legacy beacon rate setting
* [ BEACON_RATE_HT ]: HT beacon rate setting
* [ BEACON_RATE_VHT ]: VHT beacon rate setting
* [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
* [ AIRTIME_FAIRNESS ]: airtime fairness scheduling
* [ AQL ]: Airtime Queue Limits (AQL)
* [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
* [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
* [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support
* [ BEACON_RATE_HE ]: HE beacon rate support (AP/mesh)
It's a backport, but it worked. I had to manually download the firmware though. I will prepare some performance tests later on.
I had to manually download the firmware though.
You might want to report the issue with lack of firmware package to:
https://github.com/openwrt/mt76
It is not like the OpenWRT folks don't know the firmware is needed as a couple of the OpenWRT devs work in linux-wireless. It could be that they are not aware that there has been a public release of mt7921au based adapters and we need that firmware package available in 22.03.
Here is the direct link to where I give instructions for the installation of the latest firmware files:
Obviously you have already done it but others that read this later may want to know.
I will prepare some performance tests later on.
Cool.
What does iw dev
look like now that the firmware is installed?
What does
iw dev
look like now that the firmware is installed?
@morrownr Nothing there just yet. I haven't connected in the other adapter yet, and if I connect on my own AP it is likely to restrict allowed bands again.
root@OpenWrt:~# iw dev
phy#0
Interface wlan0
ifindex 3
wdev 0x1
addr e0:e1:a9:34:a6:67
type managed
txpower 3.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
0 0 0 0 0 0 0 0 0
Which version of OpenWRT are you using?
root@OpenWrtRpi400:~# cat /etc/openwrt_version r20156-0f301b0b1d root@OpenWrtRpi400:~# cat /etc/openwrt_release DISTRIB_ID='OpenWrt' DISTRIB_RELEASE='SNAPSHOT' DISTRIB_REVISION='r20156-0f301b0b1d' DISTRIB_TARGET='bcm27xx/bcm2711' DISTRIB_ARCH='aarch64_cortex-a72' DISTRIB_DESCRIPTION='OpenWrt SNAPSHOT r20156-0f301b0b1d' DISTRIB_TAINTS=''
Are you able to use the 953AX as an AP with 6 GHz?
root@OpenWrtRpi400:~# iw dev wlan0 info Interface wlan0 ifindex 37 wdev 0x12 addr e0:e1:a9:34:a6:d1 ssid testssid6 type AP wiphy 0 channel 53 (6215 MHz), width: 80 MHz, center1: 6225 MHz txpower 3.00 dBm multicast TXQ: qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets 0 0 0 0 0 0 0 0 0
The AP is configured but I still wasn't able to connect to it (at 5Ghz it was ok). I see the the ssid but, the the connection fails.
Good news. I have a connection between debian (CF-951AX) and openwrt running in a rpi400 (CF-953AX) using the channel 53 (6215 Mhz). The distance between them is about 50cm and I obtain about 410Mb/s in iperf3. If you need more info and/or tests, I can do that.
@yaslama
Thanks for the offer. I think the two most important things that viewers would appreciate right now are:
FYI: I have not added the 951AX yet as I have enough reports on the 953AX to feel comfortable with adding it to the list but am waiting for more reports on the 951AX
Nick
My interest in these adapters is just from a troubleshooting point of view: being able to scan for wireless networks and capture Wi-Fi traffic. I can confirm monitor mode works well in the CF-953AX in all 3 bands: 2.4, 5, and 6 GHz (US regulatory domain).
On 6 GHz, it can capture traffic using 20, 40, and 80 MHz. You can set 160 MHz, but only malformed frames are generated.
Also, reported "antenna signal" (RSSI) values are way off, unfortunately, but Mediatek is aware of this issue and looking into it.
Very promising as the first Wi-Fi 6/6E USB adapter I've been able to use for capturing.
Adrian
I had to manually download the firmware though.
You might want to report the issue with lack of firmware package to:
https://github.com/openwrt/mt76
It is not like the OpenWRT folks don't know the firmware is needed as a couple of the OpenWRT devs work in linux-wireless. It could be that they are not aware that there has been a public release of mt7921au based adapters and we need that firmware package available in 22.03.
Here is the direct link to where I give instructions for the installation of the latest firmware files:
Obviously you have already done it but others that read this later may want to know.
I will prepare some performance tests later on.
Cool.
What does
iw dev
look like now that the firmware is installed?
The firmware is is packaged with kmod-mt7921e so you can either install this package to have the firmware or install it manually.
I'll try to post a pull-request to package the firmware in its own package and have both kmod-mt7921e and kmod-mt7921u depend on it or maybe move it to mt7621-common when I have time...
My CF-953AX is on its way from China and should be there soon to replace one of my Alfa Network mt7612u adapter.
Hi Adrian,
Thanks for the report. I'm sure it will be read by many.
My interest in these adapters is just from a troubleshooting point of view: being able to scan for wireless networks and capture Wi-Fi traffic. I can confirm monitor mode works well in the CF-953AX in all 3 bands: 2.4, 5, and 6 GHz (US regulatory domain).
We needed a good report on monitor mode and this report provides additional confirmation that this adapter is indeed a tri band adapter.
On 6 GHz, it can capture traffic using 20, 40, and 80 MHz. You can set 160 MHz, but only malformed frames are generated.
The mt7921 chipset does not support the 160 MHz channel width. It is the next step up, the mt7922 chipset that supports 160. If I am reading the messages correctly, the mt7921 driver already supports the mt7922 chipset...but I have yet to see any products, PCIe or USB released with the mt7922.
Also, reported "antenna signal" (RSSI) values are way off, unfortunately, but Mediatek is aware of this issue and looking into it.
Copy all. Good info. I am convinced that Mediatek will work hard at fixing the issues and some issues only show up with the release of the product. I monitor linux-wireless and the best analogy I can come up with is the Ham and Eggs Breakfast. The chicken is involved but the pig is committed. I think you know which of the two companies is which.
Very promising as the first Wi-Fi 6/6E USB adapter I've been able to use for capturing.
This sounds good. I am curious as to your opinion of the range of the 953AX. Any thoughts?
Nick
Regarding OpenWRT: I had to manually download the firmware though.
The firmware is is packaged with kmod-mt7921e so you can either install this package to have the firmware or install it manually.
This is good info. I did not think about that but the devs do need to be consistent in how they are packaging things, It does not take much to confuse me. he he
I'll try to post a pull-request to package the firmware in its own package and have both kmod-mt7921e and kmod-mt7921u depend on it or maybe move it to mt7621-common when I have time...
That reminds me. I need to download the Ubuntu 22.10 that is indevelopment to test to see if it is up to speed with the latest firmware. If not, I can post a bug so maybe the new release will ship as plug and play. Users of other distros need to think about doing this also.
Nick
I'll try to post a pull-request to package the firmware in its own package and have both kmod-mt7921e and kmod-mt7921u depend on it or maybe move it to mt7621-common when I have time...
Hey @coudu
Hopefully that works its way in soon. Thanks for doing that. My plan is to add 6 GHz capability to my main wifi router as soon as I have two good adapters. What I want to know is where is ALFA? Come on ALFA, we are waiting!
Also, reported "antenna signal" (RSSI) values are way off, unfortunately, but Mediatek is aware of this issue and looking into it.
@adriangranados
I noticed a patch in linux-wireless today that might be aimed at fixing this issue.
I noticed a patch in linux-wireless today that might be aimed at fixing this issue.
@morrownr that's great! Can't wait to test it. Thanks for letting me know.
Hey @coudu
Hopefully that works its way in soon. Thanks for doing that. My plan is to add 6 GHz capability to my main wifi router as soon as I have two good adapters. What I want to know is where is ALFA? Come on ALFA, we are waiting!
Same here, I was a bit worried when I had to move from ath9k/ath10k cause I needed the mpcie slots for SFP and 2.5Gbe, but I have two Alfa AWUS036ACM (one for 2.4, one for 5Ghz) and they have been quite amazing on stability/AP runtime being USB adapters. I would also like an Alfa made 6Ghz one because their products are very well made.
Thanks @morrownr for "centralizing" all these infos.
I noticed a patch in linux-wireless today that might be aimed at fixing this issue.
@morrownr that's great! Can't wait to test it. Thanks for letting me know.
The patch still needs to get approved, but made the changes by hand, tried them and got correct RSSI measurements 🥳
I have received my CF-953AX. Shipping to the US East coast was took around 2 weeks. I'm using it as AP instead of the Raspberry Pi 4 Broadcom BCM2711 chip. It works mostly well with the following hostapd config:
interface=wlxredacted
ssid=Pi-USB
# ssid=Pi
# Driver interface type (hostap/wired/none/nl80211/bsd)
driver=nl80211
# Country code (ISO/IEC 3166-1)
country_code=US
# Operation mode (a = IEEE 802.11a (5 GHz), b = IEEE 802.11b (2.4 GHz),
# g = IEEE 802.11g (2.4 GHz), ad = IEEE 802.11ad (60 GHz). For IEEE 802.11ax
# (HE) on 6 GHz this needs to be set to hw_mode=a.
hw_mode=a
ieee80211n=1
ieee80211ac=1
ieee80211ax=1
channel=36
# Maximum number of stations allowed
max_num_sta=255
# Bit field: bit0 = WPA, bit1 = (WPA2 or WPA3)
wpa=2
# Bit field: 1=wpa, 2=wep, 3=both
auth_algs=1
# Set of accepted cipher suites; disabling insecure TKIP
wpa_pairwise=CCMP
# Set of accepted key management algorithms
wpa_key_mgmt=WPA-PSK
wpa_passphrase=redacted
# hostapd event logger configuration
logger_stdout=-1
logger_stdout_level=2
# QoS support
wmm_enabled=1
# Use "iw list" to show device capabilities and modify ht_capab accordingly
ht_capab=[HT40+][SHORT-GI-20][SHORT-GI-40][DSSS_CCK-40]
vht_capab=[SHORT-GI-80][SU-BEAMFORMEE]
For example, the following is the speedtest output for the BCM2711 AP and few centimeters distant AX210 based client:
[iwd]# station wlan0 show
Station: wlan0 *
--------------------------------------------------------------------------------
Settable Property Value
--------------------------------------------------------------------------------
Scanning no
State connected
Connected network Pi
IPv4 address 192.168.11.242
ConnectedBss e4:5f:01:30:41:d4
Frequency 5180
Security WPA2-Personal
RSSI -40 dBm
AverageRSSI -39 dBm
RxMode 802.11ac
RxMCS 9
TxMode 802.11ac
TxMCS 9
TxBitrate 200000 Kbit/s
RxBitrate 200000 Kbit/s
% speedtest-cli
Retrieving speedtest.net configuration...
Testing from Verizon Fios (100.8.215.199)...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by Pilot Fiber (New York, NY) [3.99 km]: 35.289 ms
Testing download speed................................................................................
Download: 88.67 Mbit/s
Testing upload speed......................................................................................................
Upload: 76.10 Mbit/s
In contrast, with CF-953AX
[iwd]# station wlan0 show
Station: wlan0
--------------------------------------------------------------------------------
Settable Property Value
--------------------------------------------------------------------------------
Scanning no
State connected
Connected network Pi-USB
IPv4 address 192.168.10.112
ConnectedBss e0:e1:a9:34:a6:a9
Frequency 5180
Security WPA2-Personal
RSSI -39 dBm
AverageRSSI -38 dBm
RxMode 802.11ax
RxMCS 9
TxMode 802.11ax
TxMCS 9
TxBitrate 458800 Kbit/s
RxBitrate 458800 Kbit/s
% speedtest-cli
Retrieving speedtest.net configuration...
Testing from Verizon Fios (100.8.215.199)...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by new york mega (New York, NY) [3.98 km]: 8.661 ms
Testing download speed................................................................................
Download: 181.50 Mbit/s
Testing upload speed......................................................................................................
Upload: 209.75 Mbit/s
The speed differential grows with distance.
However, there is one significant problem with the CF-953AX / MT7921U / hostapd: If I move one of the clients out of range from the AP while running a speedtest from that client, the client will eventually (after a few seconds) disconnect and the AP will hang forever until hostapd is be restarted. dmesg
shows (#
indicate my annotation):
# AP Hangs. Restarted hostapd
[76215.950863] mt7921u 2-1:1.3: Message 00020002 (seq 2) timeout
[76215.950897] mt7921u 2-1:1.3: chip reset
[76216.234848] mt7921u 2-1:1.3: timed out waiting for pending tx
[76216.439881] mt7921u 2-1:1.3: HW/SW Version: 0x8a108a10, Build Time: 20210122002654a
[76216.448109] mt7921u 2-1:1.3: WM Firmware Version: ____000000, Build Time: 20210122002730
[76222.095035] mt7921u 2-1:1.3: Message 00020003 (seq 1) timeout
[76222.095111] mt7921u 2-1:1.3: chip reset
[76222.383010] mt7921u 2-1:1.3: timed out waiting for pending tx
[76222.596973] mt7921u 2-1:1.3: HW/SW Version: 0x8a108a10, Build Time: 20210122002654a
[76222.607455] mt7921u 2-1:1.3: WM Firmware Version: ____000000, Build Time: 20210122002730
[76225.660595] IPv6: ADDRCONF(NETDEV_CHANGE): wlxe0e1a934a6a9: link becomes ready
# AP Hangs. Restarted hostapd
[77179.287085] mt7921u 2-1:1.3: Message 00020002 (seq 8) timeout
[77179.287164] mt7921u 2-1:1.3: chip reset
[77181.623085] mt7921u 2-1:1.3: timed out waiting for pending tx
[77181.805101] mt7921u 2-1:1.3: HW/SW Version: 0x8a108a10, Build Time: 20210122002654a
[77181.815371] mt7921u 2-1:1.3: WM Firmware Version: ____000000, Build Time: 20210122002730
[77185.017076] IPv6: ADDRCONF(NETDEV_CHANGE): wlxe0e1a934a6a9: link becomes ready
# AP Hangs. Restarted hostapd
[77769.884059] mt7921u 2-1:1.3: Message 00020001 (seq 3) timeout
[77769.884097] mt7921u 2-1:1.3: chip reset
[77770.100847] mt7921u 2-1:1.3: HW/SW Version: 0x8a108a10, Build Time: 20210122002654a
[77770.108946] mt7921u 2-1:1.3: WM Firmware Version: ____000000, Build Time: 20210122002730
[77772.923290] IPv6: ADDRCONF(NETDEV_CHANGE): wlxe0e1a934a6a9: link becomes ready
# Unplug CF-953AX
[77782.712226] usb 2-1: USB disconnect, device number 4
[77782.876291] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[77782.884544] wlxe0e1a934a6a9: failed to remove key (0, ce:d3:79:8c:5b:aa) from hardware (-19)
[77782.890112] wlxe0e1a934a6a9: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-19)
[77783.028189] usb 1-1.1: new high-speed USB device number 37 using xhci_hcd
[77783.130083] usb 1-1.1: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[77783.130119] usb 1-1.1: New USB device strings: Mfr=6, Product=7, SerialNumber=8
[77783.130135] usb 1-1.1: Product: Wireless_Device
[77783.130150] usb 1-1.1: Manufacturer: MediaTek Inc.
[77783.130163] usb 1-1.1: SerialNumber: 000000000
[77783.832206] mt7921u 2-1:1.3: timed out waiting for pending tx
[77784.736435] usb 2-1: new SuperSpeed USB device number 5 using xhci_hcd
[77784.758580] usb 2-1: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[77784.758600] usb 2-1: New USB device strings: Mfr=6, Product=7, SerialNumber=8
[77784.758607] usb 2-1: Product: Wireless_Device
[77784.758613] usb 2-1: Manufacturer: MediaTek Inc.
[77784.758619] usb 2-1: SerialNumber: 000000000
[77785.148184] Bluetooth: hci0: Opcode 0x c03 failed: -110
[77785.833117] mt7921u: probe of 1-1.1:1.3 failed with error -5
[77785.840756] usb 1-1.1: USB disconnect, device number 37
[77786.780193] Bluetooth: hci1: Opcode 0x c03 failed: -110
[77786.909328] usb 2-1: reset SuperSpeed USB device number 5 using xhci_hcd
[77786.971534] mt7921u 2-1:1.3: HW/SW Version: 0x8a108a10, Build Time: 20210122002654a
[77786.986068] mt7921u 2-1:1.3: WM Firmware Version: ____000000, Build Time: 20210122002730
[77788.956251] Bluetooth: hci0: Opcode 0x c03 failed: -110
[77789.063213] mt7921u 2-1:1.3 wlxe0e1a934a6a9: renamed from wlan1
[77902.239716] IPv6: ADDRCONF(NETDEV_CHANGE): wlxe0e1a934a6a9: link becomes ready
I plan to email Lorenzo about this issue, as he wrote the driver https://lwn.net/ml/linux-wireless/cover.1647188301.git.lorenzo@kernel.org/ Please let me know if you have other suggestions. For example, if you think this is rather a hostapd issue than a driver issue.
Hi @leezu
if you think this is rather a hostapd issue than a driver issue.
Can I get you to post the full output of "iw list" so that I can use the info to dig into the hostapd docs? I don't know at this point because I don't have an adapter based on the mt7921au chipset yet but I do have a lot of experience with hostapd so I might be able to make some suggestions.
Are you trying to use 5 GHz? What channel width are you trying to use?
Nick
Thank you, @morrownr! I'm trying to use 5 GHz on channel 36. The full output is at iw_list.txt Preparing the output, I noticed that I mistakenly referred to BCM2711 Capabilities and VHT Capabilities when preparing the CF-953AX hostapd configuration. These are the corrected capabilities:
ht_capab=[LDPC][HT40+][GF][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935]
vht_capab=[MAX-MPDU-7991][RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN]
The correct capabilities improve the throughput by ~25% and improve the range, or at least the chip does not crash/disconnect anymore when I reach the same distance. However, I did see another hang / crash that required me to restart hostapd, but I'm not yet sure how I triggered it. The output is
[83579.085394] mt7921u 2-1:1.3: Message 00020002 (seq 15) timeout
[83579.085429] mt7921u 2-1:1.3: chip reset
[83579.373382] mt7921u 2-1:1.3: timed out waiting for pending tx
[83579.574329] mt7921u 2-1:1.3: HW/SW Version: 0x8a108a10, Build Time: 20210122002654a
[83579.583227] mt7921u 2-1:1.3: WM Firmware Version: ____000000, Build Time: 20210122002730
[83582.822582] IPv6: ADDRCONF(NETDEV_CHANGE): wlxe0e1a934a6a9: link becomes ready
I'm trying to use 5 GHz on channel 36.
Good idea to optimize that while we figure out how to handle 6 GHz.
From hostapd.conf above:
channel=36
Recommend:
# Channel
channel=36
# Channel width
vht_oper_chwidth=1
# VHT center channel (chan + 6)
vht_oper_centr_freq_seg0_idx=42
That should take you into 80 MHz channel width mode.
Recommend you add the following:
# Advertises the country_code and the set of allowed channels and transmit power levels
ieee80211d=1
# Enables support for 5GHz DFS channels (requires ieee80211d=1)
#ieee80211h=1
We should check to see if DFS channels are working in AP mode.
mt7921u 2-1:1.3: timed out waiting for pending tx
At this point, I am no help with that.
Question: Does the LED flash?
Nick
Thank you, @morrownr! Enabling your recommended settings worked. Did you mean #ieee80211h=1
or rather ieee80211h=1
? How do you suggest to check if DFS channels are working in AP mode?
mt7921u 2-1:1.3: timed out waiting for pending tx
At this point, I am no help with that. Question: Does the LED flash?
The LED remains on constantly.
How do you suggest to check if DFS channels are working in AP mode?
Change settings to reflex a DFS channel for your country. I see your country setting is US so:
DFS FCC 80 MHz channels for hostapd: 52(58), 100(106), 116(122) and 132(138)
Example using channel 100:
# Channel
channel=100
# Channel width
vht_oper_chwidth=1
# VHT center channel (chan + 6)
vht_oper_centr_freq_seg0_idx=106
You will also need to uncomment the following line as shown:
ieee80211h=1
save and reboot then check to see if you can connect. Note: DFS channels require a 60 second delay to make sure there is not something on the channel that should make the channel unusable so you won't see the ap for at least 60 seconds... you have to wait. I'm hoping DFS works on 5 GHz as it is very handy depending on the local wifi situation. This message is coming to you via DFS channel 52(58). It is clean air here and my mt7612u based adapter that is in client mode shows ~400 Mb/s as shown by iperf3. WiFi can really go fast in clean air. The mt7612u chipset has not supported DFS in AP mode so I am hoping the new chipset, mt7921au, does support it. Let us know what you find out.
Enabling your recommended settings worked
You may see higher speeds now that you are using 80 MHz channel width.
Nice, thank you @morrownr! I'm in contact with Deren from Mediatek regarding the hang, which also persists with the latest firmware. I'll keep the current setup running for a few days to gather more information about the situations in which the hang occurs / the frequency of occurrence and also see if Deren has a quick fix for this particular issue. Following that, I'll proceed and try DFS based on your suggestion.
@leezu Not sure if related, but there's been some activity in OpenWRT about a bug that causes some halting condition when a client leaves a Wi-Fi network, plus some other regressions that have been apparently fixed in the last days.
Dave Taht on a post on LinkedIn:
I have been working on the "make wifi fast project" now for going on 10 years. In the last 6 months we untangled a string of regressions in the openwrt (and #linux mainline) stack that entered the "stable" 21.02.2 and .3 releases, which I think are now fixed in 22.03-rc6. If anyone out there has been struggling with #openwrt's #wifi for the last 9+ months, I apologize. And if you or anyone you know could step up to #help #test 22.03-rc6, especially if you use the #ath9k, #ath10k, or #mt76 wifi chips in your #router, I'd really appreciate it.
The post then points to https://forum.openwrt.org/t/aql-and-the-ath10k-is-lovely/59002/831
Just thought I'd share.
Adrian
@leezu
Following that, I'll proceed and try DFS based on your suggestion.
Thanks. I think a lot of folks would be interested. I know I am interested.
Nick
There are some AP mode issues in v5.19 stable tree. The fix is mainline ready and would be post to v5.19.y later. If you want to run AP mode now, please take the patch below and update to latest firmware. :) mt76: mt7921: fix command timeout in AP stop period
I am surprised by the good community that there is here.
This seems to be the place to talk about the CF-953AX so I will share my experience using it with Ubuntu 22.04 as simple wifi client.
I bought the CF-953AX to replace my CF-955AX, which I'm currently using with this driver https://github.com/lwfinger/rtl8852au, with something that offers a in-kernel-driver.
To test the CF-953AX with 22.04 I installed kernel versions 5.18, 5.18.15 and 5.19 from https://kernel.ubuntu.com/~kernel-ppa/mainline/.
At first I used the firmware already provided by 22.04.
The router is ax capable -> Fritzbox 6660 cable set to channel 36 at 5Ghz. Channel width can't be changed and can be up to 160Mhz.
The client is set to use only the 5Ghz band.
The distance from client to router is around 7m with two thin ceilings between.
Kernel 5.18 didn't have stable throughput rates. They where fluctuating between 50 and 300 Mbit using a two minute connection test to the router with iperf.
So I switched to 5.18.15. Throughput became stable at ~300 Mbit. But after about two hours the client got deauthenticated from the router (Reason: 16=GROUP_KEY_HANDSHAKE_TIMEOUT) and a reboot was necessary to reestablish the connection.
After that I tied 5.19 (Daily/current -> 2022-08-11). Throughput stayed at ~300 Mbit. Client got deauthenticated after about two hours again.
As next step I replaced the provided firmware (Files: BT_RAM_CODE_MT7961_1_2_hdr.bin, WIFI_MT7961_patch_mcu_1_2_hdr.bin, WIFI_RAM_CODE_MT7961_1.bin) with the ones here https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/mediatek. Checking the size and date on the files showed that they differ from the included ones. Even with the new firmware the client got deauthenticated again, sadly.
The CF-955AX works stable on the same port at the same location, but with ~110 Mbit less throughput compared to the CF-953AX. No other wireless client has issues with deauthentication.
That's it. No happy end, so far. Maybe this helps somebody.
Aug 11 16:59:47 ... kernel: [ 8765.480856] wlan0: deauthenticated from ... (Reason: 16=GROUP_KEY_HANDSHAKE_TIMEOUT)
I am surprised by the good community that there is here.
I have been surprised at how many people use this site. I had known there was need for better usb wifi support for many years and the begiinning of COVID-19 gave me a good excuse to start working on something and it has evolved based on input from many people and help from many people.
Nick
Hi @UnknownProgrammer
I think it would work better if you started a new issue for just this issue as this thread has grown so long that many will never read this far. You can copy most of what you wrote above into the new issue. A good title would attract others with the CF-953AX. Maybe something like this:
CF-953AX dropping connection with Fritzbox 6600
Some other questions that might help with the issue:
Have you tested with other bands? 6 GHz and 2 GHz? Results?
Have you tested on alternate 5 GHz channels?
Have you upgraded the firmware in the Fritzbox to the most up to date version?
If we can get verification that this is a driver issue, we can make a report to the Mediatek kernel devs.
Regards,
Nick
Hello @morrownr
took a while to perform the tests to answer your questions.
Have you tested with other bands? 6 GHz and 2 GHz? Results?
Set client to 2.4Ghz fix with the same result -> connection drop after 2-3 hours.
The 6660 is only a wifi 6 device not wifi 6e.
Have you tested on alternate 5 GHz channels?
Set the router to channel 100 -> also connection drop after 2-3 hours.
Have you upgraded the firmware in the Fritzbox to the most up to date version?
Firmware version is the latest 7.29. But the firmware is controlled by the cable provider, which takes quite some time to review and deliver the manufacturer firmware.
Looks like the time-out timer for rekeying is set to 3 seconds, because the deauthentication happens 3 seconds after the rekeying should have happened.
Would be nice if the driver had some recovery mechanism to reestablish a connection after deauthentication.
Thank you for your interest, I will open a separate issue.
Thank you for writing the instructions of adding a firmware. Aside from the firmware is there a foolproof way of manually installing the mt7921u driver in the kernel? The latest Raspberry Pi OS doesn't yet have the drivers included.
Hi @Anima1000000
Thank you for writing the instructions of adding a firmware.
Glad it helped.
is there a foolproof way of manually installing the mt7921u driver in the kernel?
The only practical way to install the driver (module) is to upgrade the kernel. Here is a guide for Ubuntu:
https://itsfoss.com/upgrade-linux-kernel-ubuntu/#ukuu
...but don't use that guide as the mainline kernel probably does not yet include some drivers that are included in the RasPiOS. I would have to investigate to see what options are available for the PiOS and I am very busy today patching some drivers. You might post a msg on the appropriate RasPi forum and ask how to upgrade the RasPiOS kernel to 5.19 so as to get driver support for your new adapter. If you don't have luck that way, come back and check in with me next week. I may have time then.
Nick
@Anima1000000
I had a thought: What are you doing with that Pi? If you are running an AP, OpenWRT 22.03 already has the driver. The devs backported it to kernel 5.10.
@yaslama @leezu @deren @bcdonadio @coudu @amisix @adriangranados
Good day all,
This is a broadcast message to many of those involved in this thread. Some of you already have cf-953ax or cf-951ax usb adapters that feature the mt7921au chipset. My cf-951ax arrived yesterday and I have been testing it.
So far the results are not good. In fact, the results are so bad that I need to do some comparisons with your results to see if I have a faulty adapter so I can return it.
What am I seeing:
The adapter is basically non functional in USB3 mode. The interface will come and go and even if it shows a connect in managed mode for a time, the connection is not pushing data. On the other hand, plugged into a USB2 port, things work well but the USB2 speed limitation is there.
The log provided by dmesg with unrelated items removed: (note that I do not have bluetooth capability in this test system so the new adapter is causing the system to now think there is bluetooth capability)
[ 18.171617] Bluetooth: hci0: Opcode 0x c03 failed: -110
[ 20.187608] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[ 22.203640] Bluetooth: hci0: AOSP get vendor capabilities (-110)
[ 22.332230] usb 4-1: reset SuperSpeed USB device number 3 using xhci_hcd
[ 22.478054] Bluetooth: hci0: Device setup in 120467 usecs
[ 22.488041] mt7921u 4-1:1.3: HW/SW Version: 0x8a108a10, Build Time: 20220608210839a
[ 22.497664] mt7921u 4-1:1.3: WM Firmware Version: ____010000, Build Time: 20220608210922
[ 22.548769] Bluetooth: hci0: AOSP extensions version v1.00
[ 22.548775] Bluetooth: hci0: AOSP quality report is supported
[ 22.554572] Bluetooth: RFCOMM TTY layer initialized
[ 22.554577] Bluetooth: RFCOMM socket layer initialized
[ 22.554580] Bluetooth: RFCOMM ver 1.11
[ 24.115765] mt7921u 4-1:1.3 wlxe0e1a935c51f: renamed from wlan0
[ 31.790672] wlxe0e1a935c51f: authenticate with 8c:59:73:fe:8b:f5
[ 31.790688] wlxe0e1a935c51f: Invalid HE elem, Disable HE
[ 31.821370] wlxe0e1a935c51f: send auth to 8c:59:73:fe:8b:f5 (try 1/3)
[ 31.856692] wlxe0e1a935c51f: authenticate with 8c:59:73:fe:8b:f5
[ 31.856699] wlxe0e1a935c51f: send auth to 8c:59:73:fe:8b:f5 (try 1/3)
[ 31.872510] wlxe0e1a935c51f: authenticated
[ 31.879606] wlxe0e1a935c51f: associate with 8c:59:73:fe:8b:f5 (try 1/3)
[ 31.881962] wlxe0e1a935c51f: RX AssocResp from 8c:59:73:fe:8b:f5 (capab=0x111 status=30 aid=3)
[ 31.881973] wlxe0e1a935c51f: 8c:59:73:fe:8b:f5 rejected association temporarily; comeback duration 1000 TU (1024 ms)
[ 32.923642] wlxe0e1a935c51f: associate with 8c:59:73:fe:8b:f5 (try 2/3)
[ 32.966071] wlxe0e1a935c51f: RX AssocResp from 8c:59:73:fe:8b:f5 (capab=0x111 status=0 aid=3)
[ 33.715639] usb 4-1: USB disconnect, device number 3
[ 36.155643] mt7921u 4-1:1.3: Message 00020002 (seq 6) timeout
[ 36.155706] mt7921u 4-1:1.3: chip reset
[ 36.160765] wlxe0e1a935c51f: associated
[ 36.161055] wlxe0e1a935c51f: deauthenticating from 8c:59:73:fe:8b:f5 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 36.161259] ------------[ cut here ]------------
[ 36.161264] WARNING: CPU: 2 PID: 234 at kernel/kthread.c:659 kthread_park+0x8a/0xa0
[ 36.161279] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) cmac algif_hash algif_skcipher af_alg bnep intel_rapl_msr nls_iso8859_1 intel_rapl_common mei_hdcp mei_pxp x86_pkg_temp_thermal snd_hda_codec_realtek intel_powerclamp mt7921u coretemp snd_hda_codec_generic mt7921_common ledtrig_audio snd_hda_codec_hdmi dcdbas mt76_connac_lib mt76_usb mt76 uvcvideo btusb videobuf2_vmalloc snd_hda_intel videobuf2_memops btrtl kvm_intel videobuf2_v4l2 dell_smm_hwmon mac80211 snd_intel_dspcfg btbcm snd_intel_sdw_acpi videobuf2_common snd_usb_audio btintel snd_hda_codec kvm btmtk videodev snd_usbmidi_lib snd_hda_core cfg80211 rapl snd_hwdep bluetooth joydev intel_cstate mc libarc4 input_leds snd_pcm ecdh_generic ecc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq at24 snd_seq_device snd_timer mei_me snd mei soundcore mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp ramoops parport reed_solomon mtd pstore_blk pstore_zone efi_pstore ip_tables x_tables
[ 36.161325] autofs4 btrfs blake2b_generic xor raid6_pq zstd_compress libcrc32c dm_mirror dm_region_hash dm_log hid_logitech_hidpp amdgpu iommu_v2 gpu_sched hid_logitech_dj hid_generic uas usb_storage usbhid hid radeon i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper syscopyarea crct10dif_pclmul sysfillrect crc32_pclmul sysimgblt ghash_clmulni_intel fb_sys_fops aesni_intel i2c_i801 crypto_simd cryptd i2c_smbus drm ahci r8169 libahci xhci_pci lpc_ich realtek xhci_pci_renesas video
[ 36.161350] CPU: 2 PID: 234 Comm: kworker/u8:5 Tainted: G OE 5.19.3-051903-generic #202208211442
[ 36.161352] Hardware name: Dell Inc. Vostro 470/0YJPT1, BIOS A14 06/25/2018
[ 36.161354] Workqueue: mt76 mt7921_mac_reset_work [mt7921_common]
[ 36.161360] RIP: 0010:kthread_park+0x8a/0xa0
[ 36.161363] Code: 32 31 c0 5b 41 5c 5d c3 cc cc cc cc 0f 0b 49 8b 9c 24 a8 0a 00 00 a8 04 74 ab 0f 0b b8 da ff ff ff 5b 41 5c 5d c3 cc cc cc cc <0f> 0b b8 f0 ff ff ff eb d0 0f 0b eb cc 66 0f 1f 84 00 00 00 00 00
[ 36.161364] RSP: 0018:ffffa86d406ffdb0 EFLAGS: 00010202
[ 36.161366] RAX: 0000000000000004 RBX: ffff95f01c07be80 RCX: ffff95f0131e24c0
[ 36.161367] RDX: 0000000000000001 RSI: 0000000000000286 RDI: ffff95f019e90000
[ 36.161367] RBP: ffffa86d406ffdc0 R08: 0000000000000000 R09: ffffa86d406ffd90
[ 36.161368] R10: 0000000000000000 R11: 0000000000000000 R12: ffff95f019e90000
[ 36.161369] R13: ffff95f0131e20e0 R14: ffff95f0131e20e0 R15: ffff95f0131e2430
[ 36.161370] FS: 0000000000000000(0000) GS:ffff95f212d00000(0000) knlGS:0000000000000000
[ 36.161371] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 36.161372] CR2: 00007f49183c9000 CR3: 0000000065a10004 CR4: 00000000001706e0
[ 36.161374] Call Trace:
[ 36.161375] <TASK>
[ 36.161377] mt76u_stop_rx+0x26/0xd0 [mt76_usb]
[ 36.161381] mt7921u_mac_reset+0x62/0x1a3 [mt7921u]
[ 36.161384] mt7921_mac_reset_work+0xa6/0x15a [mt7921_common]
[ 36.161388] process_one_work+0x21f/0x3f0
[ 36.161389] worker_thread+0x50/0x3e0
[ 36.161391] ? rescuer_thread+0x3a0/0x3a0
[ 36.161392] kthread+0xee/0x120
[ 36.161394] ? kthread_complete_and_exit+0x20/0x20
[ 36.161397] ret_from_fork+0x22/0x30
[ 36.161400] </TASK>
[ 36.161401] ---[ end trace 0000000000000000 ]---
[ 36.161955] mt7921u 4-1:1.3: chip reset failed
[ 36.161978] wlxe0e1a935c51f: Driver requested disconnection from AP 00:00:00:00:00:00
[ 37.111645] mt7921u 4-1:1.3: timed out waiting for pending tx
[ 37.431747] usb 4-1: new SuperSpeed USB device number 4 using xhci_hcd
[ 37.453769] usb 4-1: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[ 37.453778] usb 4-1: New USB device strings: Mfr=6, Product=7, SerialNumber=8
[ 37.453781] usb 4-1: Product: Wireless_Device
[ 37.453783] usb 4-1: Manufacturer: MediaTek Inc.
[ 37.453786] usb 4-1: SerialNumber: 000000000
[ 37.576021] Bluetooth: hci0: Device setup in 116416 usecs
[ 39.579616] Bluetooth: hci0: Opcode 0x c03 failed: -110
[ 41.595650] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[ 43.606783] Bluetooth: hci0: AOSP get vendor capabilities (-110)
[ 43.731448] usb 4-1: reset SuperSpeed USB device number 4 using xhci_hcd
[ 43.874526] Bluetooth: hci0: Device setup in 121863 usecs
[ 43.894596] mt7921u 4-1:1.3: HW/SW Version: 0x8a108a10, Build Time: 20220608210839a
[ 43.903996] mt7921u 4-1:1.3: WM Firmware Version: ____010000, Build Time: 20220608210922
[ 43.945886] Bluetooth: hci0: AOSP extensions version v1.00
[ 43.945892] Bluetooth: hci0: AOSP quality report is supported
[ 45.522648] mt7921u 4-1:1.3 wlxe0e1a935c51f: renamed from wlan0
[ 46.609545] usb 4-1: USB disconnect, device number 4
[ 46.974187] usb 4-1: new SuperSpeed USB device number 5 using xhci_hcd
[ 46.999369] usb 4-1: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[ 46.999375] usb 4-1: New USB device strings: Mfr=6, Product=7, SerialNumber=8
[ 46.999376] usb 4-1: Product: Wireless_Device
[ 46.999377] usb 4-1: Manufacturer: MediaTek Inc.
[ 46.999378] usb 4-1: SerialNumber: 000000000
[ 47.120648] Bluetooth: hci0: Device setup in 117814 usecs
[ 49.097443] Bluetooth: hci0: Opcode 0x c03 failed: -110
[ 51.090207] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[ 53.092423] Bluetooth: hci0: AOSP get vendor capabilities (-110)
[ 53.220126] usb 4-1: reset SuperSpeed USB device number 5 using xhci_hcd
[ 53.351111] Bluetooth: hci0: Device setup in 106999 usecs
[ 53.386661] mt7921u 4-1:1.3: HW/SW Version: 0x8a108a10, Build Time: 20220608210839a
[ 53.396121] mt7921u 4-1:1.3: WM Firmware Version: ____010000, Build Time: 20220608210922
[ 53.418456] Bluetooth: hci0: AOSP extensions version v1.00
[ 53.418461] Bluetooth: hci0: AOSP quality report is supported
[ 55.013501] mt7921u 4-1:1.3 wlxe0e1a935c51f: renamed from wlan0
[ 58.824269] wlxe0e1a935c51f: authenticate with 8c:59:73:fe:8b:f5
[ 58.824284] wlxe0e1a935c51f: Invalid HE elem, Disable HE
[ 58.880414] wlxe0e1a935c51f: send auth to 8c:59:73:fe:8b:f5 (try 1/3)
[ 58.913641] wlxe0e1a935c51f: authenticate with 8c:59:73:fe:8b:f5
[ 58.913648] wlxe0e1a935c51f: send auth to 8c:59:73:fe:8b:f5 (try 1/3)
[ 58.930081] wlxe0e1a935c51f: authenticated
[ 58.933104] wlxe0e1a935c51f: associate with 8c:59:73:fe:8b:f5 (try 1/3)
[ 58.935940] wlxe0e1a935c51f: RX AssocResp from 8c:59:73:fe:8b:f5 (capab=0x111 status=0 aid=2)
[ 59.451383] wlxe0e1a935c51f: associated
[ 59.466654] wlxe0e1a935c51f: Limiting TX power to 21 (24 - 3) dBm as advertised by 8c:59:73:fe:8b:f5
[ 60.036337] IPv6: ADDRCONF(NETDEV_CHANGE): wlxe0e1a935c51f: link becomes ready
My system is amd64 running Linux Mint 21 (Ubuntu based) . The kernel is updated to 5.19.3 and various other adapters using mt7612u, mt7610u and various Realtel chipsets are all working fine.
Thinks to look at:
$ lsusb -t
I have been checking what mode the adapter is using. The results are somewhat strange. In USB3 ports, sometimes the adapter is in USB3 mode and doesn't work and sometimes it is in USB2 mode and does work well with the USB2 speed limitations. If plugged into a USB2 port, it works but once again, with the speed limitations.Invalid HE elem, Disable HE
Anyone else seeing that?You thoughts and test results are welcome.
Nick
@yaslama @leezu @deren @bcdonadio @coudu @amisix @adriangranados
Follow on to my above message about the COMFAST CF-951AX: (using kernel 5.19.3)
Further testing this morning:
Regarding the bluetooth issue: Let me write out in simple terms what I think is happening:
I have tested multiple times with this adaper in a port and without it in a port. This adapter is causing the system to think it has bluetooth support. When the bluetooth firmware is available, it is loaded and then there is a failure noted in the log that makes it look like the driver cannot find the bluetooth hardware. If I remove the bluetooth firmware, firmware loading fails as expected.
So, it appears that ID 0e8d:7961 MediaTek Inc. Wireless_Device
is triggering bluetooth support but the actual bluetooth hardware is absent or not turned on in this implementation. This leaves a lot of nastiness in the system log. This needs to be addressed as my system shows active bluetooth support but then nothing works. I don't need bluetooth support and I was not expecting it in this adapter but we have a little mess on our hands.
I have a little laptop that has an internal card based on the mt7921. WiFi and bluetooth work great. It looks like someone involved in driver development forgot to account for situations where bluetooth is not implemented.
On to continue testing USB3.
Nick
@yaslama @leezu @deren @bcdonadio @coudu @amisix @adriangranados
Follow on to my above message about the COMFAST CF-951AX: (using kernel 5.19.3)
Further testing:
Regarding the USB3 issue:
Tested with OpenWRT 22.03 rc6 on a ZyXEL NBG6817 wifi router that has both USB3 and USB2 ports.
Totally non-functional on USB3. Functional in USB2.
Tested with Linux Mint 21 (based on Ubuntu 22.04) with kernel upgraded to 5.19.3.
Same as with the router. Totally non-functional on USB3. Functional in USB2.
So, same results with totally different platforms. I smell a problem with USB3 but it is not clear yet what the problem could be. If you have a cf-951ax or cf-953ax, can you please check your results when the adapter is in a USB3 port?
On to continue testing...
Nick
Hi @morrownr,
here are some answers to your questions, using Xubuntu 22.04 with iwd and kernel 5.19.3.
~$ uname -a
Linux Blade 5.19.3-051903-generic #202208211442 SMP PREEMPT_DYNAMIC Sun Aug 21 14:54:49 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Is your system showing a Bluetooth adapter?
Yes, it does. Mine is now running on USB3 connected with 2m USB3.0 extension cable, I previously tested it only on USB2. My OpenWrt router does only have a USB2 port.
|__ Port 6: Dev 3, If 0, Class=Wireless, Driver=btusb, 5000M
ID 0e8d:7961 MediaTek Inc.
|__ Port 6: Dev 3, If 3, Class=Vendor Specific Class, Driver=mt7921u, 5000M
ID 0e8d:7961 MediaTek Inc.
|__ Port 6: Dev 3, If 1, Class=Wireless, Driver=btusb, 5000M
ID 0e8d:7961 MediaTek Inc.
|__ Port 6: Dev 3, If 2, Class=Wireless, Driver=, 5000M
ID 0e8d:7961 MediaTek Inc.
does the bluetooth adapter work?
No, it doesn't work for me after installing blueman and bluez (I removed Bluetooth things on this install). I get error messages like yours in dmesg:
[ 5.155972] kernel: usbcore: registered new interface driver btusb
[ 5.240146] kernel: Bluetooth: hci0: urb 000000006a6e727d failed to resubmit (2)
...
[ 7.306730] kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110
[ 9.322825] kernel: Bluetooth: hci0: Failed to read MSFT supported features (-110)
Invalid HE elem, Disable HE
Anyone else seeing that?
I'm not seeing that, could be because of iwd.
Some results running it on USB3 port (distance to router, Fritzbox 6660 cable -> 7m with two ceilings between):
~$ iperf -c 192.168.2.1 -p 4711 -i 5 -t 120
------------------------------------------------------------
Client connecting to 192.168.2.1, TCP port 4711
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
[ 1] local 192.168.2.64 port 35702 connected with 192.168.2.1 port 4711
[ ID] Interval Transfer Bandwidth
[ 1] 0.0000-5.0000 sec 189 MBytes 318 Mbits/sec
[ 1] 5.0000-10.0000 sec 193 MBytes 323 Mbits/sec
[ 1] 10.0000-15.0000 sec 197 MBytes 331 Mbits/sec
[ 1] 15.0000-20.0000 sec 197 MBytes 330 Mbits/sec
[ 1] 20.0000-25.0000 sec 197 MBytes 331 Mbits/sec
[ 1] 25.0000-30.0000 sec 196 MBytes 329 Mbits/sec
[ 1] 30.0000-35.0000 sec 195 MBytes 327 Mbits/sec
[ 1] 35.0000-40.0000 sec 192 MBytes 322 Mbits/sec
[ 1] 40.0000-45.0000 sec 193 MBytes 324 Mbits/sec
[ 1] 45.0000-50.0000 sec 194 MBytes 325 Mbits/sec
[ 1] 50.0000-55.0000 sec 193 MBytes 324 Mbits/sec
[ 1] 55.0000-60.0000 sec 196 MBytes 329 Mbits/sec
[ 1] 60.0000-65.0000 sec 192 MBytes 323 Mbits/sec
[ 1] 65.0000-70.0000 sec 193 MBytes 324 Mbits/sec
[ 1] 70.0000-75.0000 sec 196 MBytes 329 Mbits/sec
[ 1] 75.0000-80.0000 sec 192 MBytes 321 Mbits/sec
[ 1] 80.0000-85.0000 sec 192 MBytes 322 Mbits/sec
[ 1] 85.0000-90.0000 sec 195 MBytes 328 Mbits/sec
[ 1] 90.0000-95.0000 sec 195 MBytes 327 Mbits/sec
[ 1] 95.0000-100.0000 sec 190 MBytes 320 Mbits/sec
[ 1] 100.0000-105.0000 sec 195 MBytes 327 Mbits/sec
[ 1] 105.0000-110.0000 sec 192 MBytes 323 Mbits/sec
[ 1] 110.0000-115.0000 sec 190 MBytes 318 Mbits/sec
[ 1] 115.0000-120.0000 sec 185 MBytes 311 Mbits/sec
[ 1] 0.0000-120.0941 sec 4.53 GBytes 324 Mbits/sec
Similar throughput as with USB2.
Hi all,
same here, I've tested mine on OpenWrt x86_64 master, AP mode, and so far results are not good at all. Configured on 5GHz ac it works well, even a bit faster than my mt7612u based Alpha Network sticks, but on 5GHz ax I have a very bad throughput (~ 33Mb/s) and random reboots...
Didn't have time to further look in logs but I think the driver and AP mode needs a bit more work. Didn't test on USB2, only USB3, but my x86 router has both so I'll give it a try to see if it's any better.
@yaslama @leezu @deren @bcdonadio @coudu @amisix @adriangranados @UnknownProgrammer
here are some answers to your questions, using Xubuntu 22.04 with iwd and kernel 5.19.3.
This is very much appreciated.
Is your system showing a Bluetooth adapter?
Yes, it does.
does the bluetooth adapter work?
No, it doesn't work for me after installing blueman and bluez (I removed Bluetooth things on this install). I get error messages like yours in dmesg:
I pulled an old bluetooth 4 nano adapter out and plugged it in. I then paired the system and my phone... bla bla bla...and everything works. Our testing and results seem to confirm that the device ID is triggering support for Bluetooth that does not exist. That needs to be fixed.
Invalid HE elem, Disable HE Anyone else seeing that?
I'm not seeing that, could be because of iwd.
Hmmm... is it time to point the finger at wpa_supplicant for this one?
Do you have good guide for replacing wpa_supplicant with iwd?
Some results running it on USB3 port (distance to router, Fritzbox 6660 cable -> 7m with two ceilings between):
Which of the 2 adapters do you have?
Have you tried all of your USB3 ports followed by a lsusb -t
to see if you are consistently in USB3 mode?
Thanks again,
Nick
aslama @leezu @deren @bcdonadio @amisix @adriangranados @UnknownProgrammer
@coudu
same here, I've tested mine on OpenWrt x86_64 master, AP mode, and so far results are not good at all. Configured on 5GHz ac it works well, even a bit faster than my mt7612u based Alpha Network sticks, but on 5GHz ax I have a very bad throughput (~ 33Mb/s) and random reboots...
Something we need to keep in mind is that the driver in OpenWRT is not necessarily the same as the mainline driver. The OpenWRT driver could be behind on patches. Same results for AX here... bad bad bad.
Which adapter are your using? Mine is the cf-951ax.
Didn't test on USB2, only USB3, but my x86 router has both so I'll give it a try to see if it's any better.
While testing, can you see if 5 GHz DFS channels are working?
Nick
Something we need to keep in mind is that the driver in OpenWRT is not necessarily the same as the mainline driver. The OpenWRT driver could be behind on patches.
Looking at commits for both linux mainline and backported OpenWrt they seem to be quite on par but Openwrt's 5.10 kernel might cause issues...
Which adapter are your using? Mine is the cf-951ax.
Mine is cf-953ax
While testing, can you see if 5 GHz DFS channels are working?
No, only tested on low channels
@morrownr
Invalid HE elem, Disable HE Anyone else seeing that?
I'm not seeing that, could be because of iwd.
Hmmm... is it time to point the finger at wpa_supplicant for this one?
I meant it that way, that since the switch to iwd all network interface messages are missing from dmesg. The event could still occur. Although nothing like that is listed in the iwd log.
Do you have good guide for replacing wpa_supplicant with iwd?
I didn't find a complete guide only partial directions, but that is what I did (for Xubuntu 22.04):
sudo apt install iwd
sudo systemctl enable iwd.service
sudo systemctl start iwd.service
Add iwd-config-path=auto
and wifi.backend=iwd
to config sudo nano /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile
iwd-config-path=auto
[ifupdown]
managed=false
[device]
wifi.scan-rand-mac-address=no
wifi.backend=iwd
Disable wpa_supplicant
sudo systemctl disable wpa_supplicant.service
or (but I used just the above)
sudo systemctl mask wpa_supplicant --now
Reboot system.
I didn't try to revert the procedure, so be warned. Do it on your own risk.
Which of the 2 adapters do you have?
It is the CF-953AX model.
Have you tried all of your USB3 ports followed by a
lsusb -t
to see if you are consistently in USB3 mode?
That mainboard has only 2 USB3 ports and both show 5000M connection speed when I switch ports.
Suggestion: before I was rudely interrupted by a shit ton of work these last weeks, I was testing on my main big x86 with plenty of USB3.{0,1,2} ports and bandwidth, and then handing off the USB devices directly to QEMU/KVM/libvirt via IO-MMU with two x86 VMs running OpenWRT nightly. Maybe this can solve your bandwidth issues?
I didn't get up to the point of doing performance tests, but I left the adapters pinging each other for a while without any issues.
I couldn't however test 6E because the regdomain for Brazil is completely outdated, and the kernel get clues from every damn where of where it is, including other APs and even cellular broadcasts. I left the work at the state that I was preparing a kernel build with a modified regdb with the latest updated rules from the government.
Updated: 2023-02-26
July 2022 Comfast CF-953AX - chipset: mt7921au (single-state) (BT 5.2) http://en.comfast.com.cn/index.php?m=content&c=index&a=show&catid=13&id=182
July 2022 Comfast CF- 951AX - chipset: mt7921au (single-state) (BT 5.2) http://en.comfast.com.cn/index.php?m=content&c=index&a=show&catid=13&id=209
October 2022 Netgear A8000 AX3000 USB Adapter - chipset: mt7921au https://dongknows.com/netgear-a8000-ax3000-usb-adapter-is-here/
February 2023 ALFA AWUS036AXML https://www.alfa.com.tw/products/awus036axml?variant=39754360684616
EDIT: 2022-07-22 - Important info: The above adapters use the mt7921u driver. The mt7921 base driver has been in the Linux kernel since 5.12 so internal cards have been working well for some time with the exception of AP mode. The above are usb adapters and usb support was not added to the mt7921 driver until kernel 5.18. Most of the more popular distros provide instructions for upgrading kernels. I can provide instructions for Ubuntu based distros on request. AP mode support was added in kernel 5.19. It requires a firmware upgrade, see Main Menu 8.
EDIT: 2022-07-22 - We now have reports from @foen73 and @yaslama about the CF-953AX. Both report that it is a single-state adapter. That is very encouraging.
EDIT: 2022-08-03 - FYI: I see from an ad that the chipset is called mt7921au. This is the first time I have seen that specific name. It appears the mt7921au chipset has the same capabilities as the mt7921k that we have known about for some time.
EDIT: 2022-07-22 - Disclaimer: While we do have limited positive reports at this point, there could be issues that have not been discovered yet.
Regards,
Nick