morrownr
ALFA AWUS036AXML photos and information dumps
Manufacturer's product page: https://www.alfa.com.tw/products/awus036axml
Purchased from: https://store.rokland.com/collections/wifi-6-6e/products/alfa-awus036axml-802-11ax-wifi-6-1800-mbps-tri-band-wifi-usb-adapter-w-bluetooth
# lsusb -v -d 0e8d:
Bus 001 Device 005: ID 0e8d:7961 MediaTek Inc. Wireless_Device
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
idVendor 0x0e8d MediaTek Inc.
idProduct 0x7961
bcdDevice 1.00
iManufacturer 6 MediaTek Inc.
iProduct 7 Wireless_Device
iSerial 8 000000000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0154
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 9 Config_01
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 0
bInterfaceCount 3
bFunctionClass 224 Wireless
bFunctionSubClass 1 Radio Frequency
bFunctionProtocol 1 Bluetooth
iFunction 5 BT_FUNCTION
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 5
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 1 BT_ACL_If
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8f EP 15 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 2 BT_SCO_If
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 4
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 4
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 2 BT_SCO_If
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 4
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 4
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 2 BT_SCO_If
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 4
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 4
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 2 BT_SCO_If
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 4
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 4
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 2 BT_SCO_If
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 4
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 4
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 2 BT_SCO_If
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 4
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 4
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 6
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 2 BT_SCO_If
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x003f 1x 63 bytes
bInterval 4
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x003f 1x 63 bytes
bInterval 4
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 3 BT_ISO_If
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8a EP 10 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0a EP 10 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 3 BT_ISO_If
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8a EP 10 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0a EP 10 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 9
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 4 WiFi_If
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x08 EP 8 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x07 EP 7 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x09 EP 9 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 1
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 0x0016
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x0000f11e
BESL Link Power Management (LPM) Supported
BESL value 256 us
Deep BESL value 61440 us
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 1
Lowest fully-functional device speed is Full Speed (12Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 180 micro seconds
Device Status: 0x0002
(Bus Powered)
Remote Wakeup Enabled
After loading the US regulatory domain:
# 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.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* CCMP-256 (00-0f-ac:10)
* GCMP-128 (00-0f-ac:8)
* GCMP-256 (00-0f-ac:9)
* CMAC (00-0f-ac:6)
* CMAC-256 (00-0f-ac:13)
* GMAC-128 (00-0f-ac:11)
* GMAC-256 (00-0f-ac:12)
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: Station
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
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
Bitrates (non-HT):
* 1.0 Mbps (short preamble supported)
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
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
HE Iftypes: Station
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
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
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
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: Station
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
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
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
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)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* new_mpath
* set_mesh_config
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* tdls_mgmt
* tdls_oper
* start_sched_scan
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* connect
* disconnect
* channel_switch
* set_qos_map
* set_multicast_to_unicast
* Unknown command (140)
WoWLAN support:
* wake up on disconnect
* wake up on magic packet
* wake up on pattern match, up to 1 patterns of 1-128 bytes,
maximum packet offset 0 bytes
* can do GTK rekeying
* wake up on network detection, up to 10 match sets
software interface modes (can always be added):
* AP/VLAN
* monitor
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
Device supports TX status socket option.
Device supports HT-IBSS.
Device supports SAE with AUTHENTICATE command
Device supports scan flush.
Device supports per-vif TX power setting
Driver supports full state transitions for AP/GO clients
Driver supports a userspace MPM
Device supports active monitor (which will ACK incoming frames)
Device supports configuring vdev MAC-addr on create.
Device supports randomizing MAC-addr in scans.
Device supports randomizing MAC-addr in sched scans.
max # scan plans: 1
max scan plan interval: 65535
max scan plan iterations: 0
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xb0 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
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
Revelant excerpts from kernel log (Linux 6.1.13):
usb 1-1.3: new high-speed USB device number 5 using dwc_otg
usb 1-1.3: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
usb 1-1.3: New USB device strings: Mfr=6, Product=7, SerialNumber=8
usb 1-1.3: Product: Wireless_Device
usb 1-1.3: Manufacturer: MediaTek Inc.
usb 1-1.3: SerialNumber: 000000000
Bluetooth: Core ver 2.22
NET: Registered PF_BLUETOOTH protocol family
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
usbcore: registered new interface driver btusb
cfg80211: Loading compiled-in X.509 certificates for regulatory database
cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Bluetooth: hci0: Opcode 0x c03 failed: -110
usb 1-1.3: reset high-speed USB device number 5 using dwc_otg
usbcore: registered new interface driver mt7921u
mt7921u 1-1.3:1.3: HW/SW Version: 0x8a108a10, Build Time: 20230117170855a
mt7921u 1-1.3:1.3: WM Firmware Version: ____010000, Build Time: 20230117170942
Bluetooth: hci0: Opcode 0x c03 failed: -110
#87 #181
What does lsusb -t show?
Bluetooth: hci0: Opcode 0x c03 failed: -110
I wonder what this is. I actually did not expect bluetooth as it has been turned off on previous adapters.
What does
lsusb -tshow?
# lsusb -tv
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 480M
ID 0424:9512 Microchip Technology, Inc. (formerly SMSC) SMC9512/9514 USB Hub
|__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter
|__ Port 2: Dev 4, If 0, Class=Vendor Specific Class, Driver=r8188eu, 480M
ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter
|__ Port 3: Dev 5, If 0, Class=Wireless, Driver=btusb, 480M
ID 0e8d:7961 MediaTek Inc.
|__ Port 3: Dev 5, If 1, Class=Wireless, Driver=btusb, 480M
ID 0e8d:7961 MediaTek Inc.
|__ Port 3: Dev 5, If 2, Class=Wireless, Driver=, 480M
ID 0e8d:7961 MediaTek Inc.
|__ Port 3: Dev 5, If 3, Class=Vendor Specific Class, Driver=mt7921u, 480M
ID 0e8d:7961 MediaTek Inc.
The AWUS036AXML is "Dev 5" in the above tree. It has four interfaces, indeed as indicated by bNumInterfaces in the configuration descriptor. Interface 2 doesn't seem to have a driver claiming it.
Bluetooth: hci0: Opcode 0x c03 failed: -110
I wonder what this is.
I wonder too. That's why I included it in my kernel log excerpts. The AWUS036AXML is the only Bluetooth device in the system. We'd have to find out what opcode 0xc03 is. Error code 110 is ETIMEDOUT.
Particularly disappointing on this card is:
valid interface combinations:
* #{ managed } <= 4, #{ AP } <= 1,
total <= 4, #channels <= 1, STA/AP BI must match
Only one AP supported! :cry:
Indeed, when I try to run a secondary AP on the card, hostapd fails with:
Could not set interface wifi6-IoT flags (UP): Device or resource busy
The AWUS036AXML is the only Bluetooth device in the system. We'd have to find out what opcode 0xc03 is. Error code 110 is ETIMEDOUT.
Have you checked to see if it works?
Bluetooth has a lot of settings nd more than one manager. It depends on the distro. I am not an expert.
Port 3: Dev 5, If 3, Class=Vendor Specific Class, Driver=mt7921u, 480M ID 0e8d:7961 MediaTek Inc.
480M = USB2. Are you in a USB2 port?
Indeed, when I try to run a secondary AP on the card, hostapd fails...
I've never tried to run a secondary AP on one adapter so I am curious about your use case.
@morrownr
Have you checked to see if it works?
No. I have no interest in Bluetooth and do not have the software installed to make use of it.
480M = USB2. Are you in a USB2 port?
Yes. The info dumps were obtained on a Raspberry Pi Model B Rev 2, which does not have USB3.
I've never tried to run a secondary AP on one adapter so I am curious about your use case.
I have a primary subnet for trusted devices and a secondary subnet for untrusted devices, mainly IoT gadgets with opaque/unauditable firmwares. Both subnets are served by the same router, which is also the default gateway for both, but the router's firewall is configured to reject (i.e., not forward but rather reply with ICMP "administratively prohibited") connections from devices in the secondary subnet to devices in the primary subnet. The other direction (primary to secondary) is allowed so that my trusted devices can issue commands directly to IoT gadgets. I have a primary SSID (on both 2.4 GHz and 5 GHz) that is bridged to the primary subnet and a secondary SSID (on 2.4 GHz only) that is on the secondary subnet. (There is no wired infrastructure for the secondary subnet, so there is no Ethernet bridge needed.) I'm trying to upgrade my 2.4 GHz network from 802.11n to 802.11ax with this new AWUS036AXML, but it looks like I will have to continue using the old 802.11n radio for my secondary SSID since the AXML doesn't support multiple APs.
I have no interest in Bluetooth and do not have the software installed to make use of it.
The easy way to shut it down:
sudo rm /lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin
I have a primary subnet for trusted devices and a secondary subnet for untrusted devices...
I think this can be done with only one AP interface. I'll see what I can come up with.
- #{ managed } <= 4, #{ AP } <= 1, total <= 4, #channels <= 1, STA/AP BI must match
For what it is worth, that is not an issue with the AXML, that is a mt7921u issue. Alll adapters with the mt7921au and cards with the mt7921 or mt7921k will show the same thing. Maybe time to lobby the Mediatek devs?
I think this can be done with only one AP interface. I'll see what I can come up with.
@morrownr: I appreciate your enthusiasm, but I don't think it's possible to achieve similar results using a single SSID. For one thing, either I would have to maintain a "roster" of trusted/untrusted MAC addresses (which I'd prefer not to do), or I would have to switch to 802.1x authentication, which dumb IoT devices probably couldn't cope with anyway. And then, even if I could tell which devices were supposed to be on which subnet despite them all appearing on the same interface, there would be the issue that I want the untrusted devices to be unable to contact the trusted devices directly (i.e., without being routed). If everything is in the same broadcast domain, then the untrusted devices would be able to reach the trusted devices directly simply by adding themselves to the trusted subnet (i.e., without involving the DHCP server). If you can figure out a way to have the two tiers of devices be on separate broadcast domains despite being associated to the same AP, I'd be interested. (I think there may be a way to do it with AP isolation and ebtables, but again, I really don't want to have to maintain MAC rosters.)
Is it a hardware or driver limitation to one AP?
@bjlockie: "Both," with the caveat that these chipsets are largely software-defined radios, and it's the firmware blob that implements most of the logic, so possibly a new firmware could add multi-AP support to this chipset. Regardless, the driver is reporting that it supports only 1 AP:
static const struct ieee80211_iface_limit if_limits[] = {
{
.max = MT7921_MAX_INTERFACES,
.types = BIT(NL80211_IFTYPE_STATION)
},
{
.max = 1,
.types = BIT(NL80211_IFTYPE_AP)
}
};
https://github.com/morrownr/USB-WiFi/tree/main/home/iw_list
I guess maybe we should make chipset part of the filenames. The CF-951AX file has been there for some time and it shows only one AP capability. Interestingly, the mt7612u and the mt7610u chipsets have the 2 AP capability. They don't have AX capability.
@bjlockie Let me clarify the hardware vs driver limitation thing. You are seeing two answers and both are basically correct. I consider hardware to be what is in silicone or is otherwise fixed and unchangeable. The firmware, closed source, and driver, open source, in my mind, are not hardware. Maybe firmware that is on ROM and is located in the device should be considered hardware. In fact, I consider the firmware and driver as two parts of the driver as the consequence of one being missing is the same from a user perspective... the adapter won't work. Can the capability to have 2 APs be changed? The answer is highly likely to be yes.
Maybe the capability can happen. Unfortunately, the specific capabilities in this case simply do not exist in current USB adapter drivers. Realtek has this to say about it in their rtl8852bu driver:
interface combinations are not supported
For what it is worth, Linux is shutting Wireless Extentions WEXT support down starting with WiFi 7 and given that Intel and Mediatek are already adding WiFi 7 driver support to the kernel currently, I guess WiFi 7 is not that far off. It should not be the WiFi 6/WiFi 6e mess again but it will shut down Realtek and their WEXT drivers.
Maybe it's worth emailing the wireless mailing list to get the attention of the MediaTek devs. Maybe the driver is limited by what the hardware can do now but adding support in the firmware blob for multiple APs is doable.
Can you use the 7612u device for your iot stuff and the 7921au for your lan?
Can you use the 7612u device for your iot stuff and the 7921au for your lan?
@bjlockie: I might do that, but I was hoping to have 802.11ax on 2.4 GHz, which I can't do if the 7921 is serving the 5 GHz band.
I think what I'll actually end up doing is moving to a three-card setup: the 7921 serving 802.11ax on 2.4 GHz, the 7612 serving 802.11ac on 5 GHz, and a 7610 serving 802.11n on a different channel of the 2.4 GHz band. That'll let me use an AWUS036ACHM (high-power, long-range) to provide connectivity to IoT gadgets on a separate 2.4 GHz channel from my high-throughput 802.11ax network on 2.4 GHz. The 7612 is already working great on 5 GHz, and I'd like to leave it there rather than "wasting" its 802.11ac capability by running it on 2.4 GHz, where it can only provide 802.11n.
That'll let me use an AWUS036ACHM (high-power, long-range) to provide connectivity to IoT gadgets on a separate 2.4 GHz channel
That is what I was thinking but I did not know you had an achm. Darn thing can do range. It won't win races but IoT things seem to generally be low throughput.
I think what I'll actually end up doing is moving to a three-card setup
That is cool. This is on a Pi, right? Be careful with the usb subsystem power limitations.
This is on a Pi, right? Be careful with the usb subsystem power limitations.
Nah, I only used a Pi to get the information dumps because I knew its OS would have all the firmware blobs and every kernel option enabled. My actual router is a mini-ITX system with dual Ethernet ports and an extremely barebones software load, all compiled from source (including the kernel) by yours truly. It doesn't even have lsusb, so I couldn't conveniently get that dump on that system.
Thank you for the warning, though! I'm well aware of the Pi's power limitations. If I were going to be running multiple Wi-Fi adapters on a Pi, I'd use an externally powered USB hub.
when I try to run a secondary AP on the card, hostapd fails...
I was pondering this issue. I wonder if adding a new Main Menu item that is a list of features that we want added and bugs we want fixed would help. There are adapter makers and devs from chipset makers that stop by here and read up on the happenings. Consolidating that information in a single location might get results... not next week but in the long run.
Thoughts?
I wonder if adding a new Main Menu item that is a list of features that we want added and bugs we want fixed would help.
It couldn't hurt, but I'd expect the Linux Bugzilla would be a better place for bug reports about drivers. Bug reports and feature requests concerning hardware will fall on deaf ears regardless of where they're posted since there's just too much inertia in hardware to make any changes (within any existing product model). The only thing that might be beneficial to collect here would be bug reports and feature requests about the firmware, which would be useless to the kernel developers since they have no visibility into the firmware blobs but could be useful to the manufacturers since they can (and arguably should) improve their firmwares to gain more market share and better reputation.
Maybe a good way to do it would be to make a page for each chipset, enumerating the technical features of the chipset, such as supported interface combinations and ht_capab and vht_capab lines for hostapd configs, as well as a list of "Known Bugs." If I were a chip manufacturer, I would take an interest in seeing to it that a popular forum for disseminating information about Wi-Fi chipsets to technical users isn't advertising addressable shortcomings of my products. In other words, listing what's wrong with the chips here in an easily accessible format may motivate the manufacturers to do some "damage control."
@whitslack
https://www.spinics.net/lists/hostap/msg07723.html
https://www.spinics.net/lists/hostap/msg09571.html
Have you tried the multiple bssid support in hostapd?
##### Multiple BSSID support ################################################
#
# Above configuration is using the default interface (wlan#, or multi-SSID VLAN
# interfaces). Other BSSIDs can be added by using separator 'bss' with
# default interface name to be allocated for the data packets of the new BSS.
#
# hostapd will generate BSSID mask based on the BSSIDs that are
# configured. hostapd will verify that dev_addr & MASK == dev_addr. If this is
# not the case, the MAC address of the radio must be changed before starting
# hostapd (ifconfig wlan0 hw ether <MAC addr>). If a BSSID is configured for
# every secondary BSS, this limitation is not applied at hostapd and other
# masks may be used if the driver supports them (e.g., swap the locally
# administered bit)
#
# BSSIDs are assigned in order to each BSS, unless an explicit BSSID is
# specified using the 'bssid' parameter.
# If an explicit BSSID is specified, it must be chosen such that it:
# - results in a valid MASK that covers it and the dev_addr
# - is not the same as the MAC address of the radio
# - is not the same as any other explicitly specified BSSID
#
# Alternatively, the 'use_driver_iface_addr' parameter can be used to request
# hostapd to use the driver auto-generated interface address (e.g., to use the
# exact MAC addresses allocated to the device).
#
# Not all drivers support multiple BSSes. The exact mechanism for determining
# the driver capabilities is driver specific. With the current (i.e., a recent
# kernel) drivers using nl80211, this information can be checked with "iw list"
# (search for "valid interface combinations").
#
# Please note that hostapd uses some of the values configured for the first BSS
# as the defaults for the following BSSes. However, it is recommended that all
# BSSes include explicit configuration of all relevant configuration items.
#
#bss=wlan0_0
#ssid=test2
# most of the above items can be used here (apart from radio interface specific
# items, like channel)
#bss=wlan0_1
#bssid=00:13:10:95:fe:0b
# ...
#
# Multiple BSSID Advertisement in IEEE 802.11ax
# IEEE Std 802.11ax-2021 added a feature where instead of multiple interfaces
# on a common radio transmitting individual Beacon frames, those interfaces can
# form a set with a common Beacon frame transmitted for all. The interface
# which is brought up first is called the transmitting profile of the MBSSID
# set which transmits the Beacon frames. The remaining interfaces are called
# the non-transmitting profiles and these are advertised inside the Multiple
# BSSID element in the Beacon and Probe Response frames from the first
# interface.
#
# The transmitting interface is visible to all stations in the vicinity, however
# the stations that do not support parsing of the Multiple BSSID element will
# not be able to connect to the non-transmitting interfaces.
#
# Enhanced Multiple BSSID Advertisements (EMA)
# When enabled, the non-transmitting interfaces are split into multiple
# Beacon frames. The number of Beacon frames required to cover all the
# non-transmitting profiles is called the profile periodicity.
#
# Refer to IEEE Std 802.11-2020 for details regarding the procedure and
# required MAC address assignment.
#
# Following configuration is per radio.
# 0 = Disabled (default)
# 1 = Multiple BSSID advertisement enabled.
# 2 = Enhanced multiple BSSID advertisement enabled.
#mbssid=0
#
# The transmitting interface should be added with the 'interface' option while
# the non-transmitting interfaces should be added using the 'bss' option.
# Security configuration should be added separately per interface, if required.
#
# Example:
#mbssid=2
#interface=wlan2
#ctrl_interface=/var/run/hostapd
#wpa_passphrase=0123456789
#ieee80211w=2
#sae_pwe=1
#auth_algs=1
#wpa=2
#wpa_pairwise=CCMP
#ssid=<SSID-0>
#bridge=br-lan
#wpa_key_mgmt=SAE
#bssid=00:03:7f:12:84:84
#
#bss=wlan2-1
#ctrl_interface=/var/run/hostapd
#wpa_passphrase=0123456789
#ieee80211w=2
#sae_pwe=1
#auth_algs=1
#wpa=2
#wpa_pairwise=CCMP
#ssid=<SSID-1>
#bridge=br-lan
#wpa_key_mgmt=SAE
#bssid=00:03:7f:12:84:85
Okay, so this is not a work around. This lack of ability to support more than one AP is something that needs to be addressed.
Have you tried the
multiple bssidsupport in hostapd?
Yes, that's what I've been talking about. I don't know of any other way to run multiple APs concurrently on a single adapter. Do you?
Per my last post, I thought I had recalled that hostapd has a way around this but I was mistaken.
Should we put together a feature request and get it to the correct places?
Should we put together a feature request and get it to the correct places?
@morrownr: ~~Maybe let's get the thing working at all first before worrying about adding features.~~ Fixed.
Rokland customer support said they have contacts at MediaTek that they'll reach out to about the kernel crash that occurs when the MT7921U is used as a bridged AP.
@whitslack
Maybe let's get the thing working at all first before worrying about adding features.
You lost me. I thought the issue was about not having two ap's. So, what is the issue?
There are two separate issues. ~~I consider the crash bug to be a "bleeding from the neck" issue that needs addressing before any feature requests should be considered.~~ Fixed.
To all:
This lack of 2 AP's being available is simply a design choice by the Mediatek driver devs and they should be able to change that if we submit a feature request with a good explanation of why this is needed.
The crash from the other thread noted above is something that I have not been able to duplicate. That can be figured out. This message is coming via a RasPi4B setup as an AP using an adapter with the same chipset as the AXML. It is very stable. However, until such time as the RasPi devs release a fully updated RasPiOS that includes at least kernel 5.19 and various other more modern components, there are several components that we need to compile for the RasPiOS to support WiFi 6. Actually I should not say WiFi 6, I should say for any adapters that use the mt7921au chipset.
Here is a file showing how to upgrade the latest release of the RasPiOS to kernel 6.1:
Start with a fresh installation of RasPiOS: (the latest release was in Feb. but it is not as modern as we need yet to support the newer mt7921au chipset adapters.
https://www.raspberrypi.com/software/
I use the 64 bit version as it works on my Pi3B and my Pi4B. Those are the only 2 Pi's that I have.
Then upgrade to kernel 6.1 via the following guide:
The instructions for upgrading or adding the 2 required firmware files are shown as item 8 here in the Main Menu.
If running the Pi as an access point, you will need to compile a new version of hostapd:
If you need WPA3 support, you will also need to compile wpa_supplicant and I can post a guide for that as well on request.
The Raspberry Pi OS (RasPiOS) is not ready for the new WiFi6 and WiFi 6e adapters but we can get it up to speed for WiFi 6 with some work. Hopefully this changes after the new Debian is released around the middle of this year. RasPiOS and Kali would then soon rebase on the new Debian and things will be much better.
There is a reason that I say in Main Menu item 2 that if anyone needs plug and play, they need to skip on down to the AC1200 section. This is still true. There is light at the end of the tunnel for those that do not want to compile their way into the future:
I downloaded the Ubuntu Daily (testing version) yesterday, which will turn into Ubuntu 23.04 and will be released in April. I installed it and am happy to report that my adapter based on the mt7921au chipset was PLUG and PLAY. It was so cool. The light at the end of the tunnel is not a train.
I'll do my best to help anyone with the Alfa AXML, Netgear A8000, Comfast CF-953AX or any of the other adapters with the mt7921au chipset. Just keep in mind, this is the FIRST ever usb WiFi adapter chipset that has had a driver in the Linux kernel BEFORE the products started shipping. This is amazing progress but that does not mean that everything is immediately in place and things are working perfectly and this is not just a Linux issue. There are 3 MAJOR additions to the world of WiFi going on at the same time and all 3 are astoundingly complicated... WPA3, WiFi 6 and WiFi 6e.
If anyone thinks I need to add any of the guides I posted above to the Main Menu, let me know.
@morrownr
interesting problem ive just encountered with this adapter, im not sure if this is the problem to address it in but we can see and lll make a new request if necessary. Basically this device works perfectly on my amd64 build of kali, beautiful works great on a fresh install, now on my pinephone pro running kali arm64-6.1-rockchip it should work, its got all the drivers, but it only shows up in lsusb as "mediatek inc. wireless_device" (which it does also on my amd64 machine) and nowhere else, not in iw dev, not in ifconfig or iwconfig, just nowhere only lsusb. any thoughts?
just realized i havent attempted running it off of a powered usb hub, may try that soon when i can get my hands on one.
Hi @castr06
this device works perfectly on my amd64 build of kali
Good to hear this.
now on my pinephone pro running kali arm64-6.1-rockchip it should work, its got all the drivers
I believe you but let's go over the driver anyway:
In-kernel drivers have multiple parts. There is the file that we normally call the driver... mt7921u.ko. Also needed for wifi functionality for the mt7921au chipset is two more files that are commonly referred to as firmware. mt7921u.ko is part of the kernel. The firmware files are not part of the kernel, they are part of the distro.
It is the distro maintainers job to make sure the up to date firmware files are included in the distro. Regarding the amd64 Kali distro, it sounds like the maintainer is on the ball. Maybe it is time to see if the arm64 distro maintainer is on the ball and if not, maybe a bug report is in order.
You obviously know where USB-WiFi is so scroll down into the Main Menu and look for item 8. It goes over checking and installing firmware. The section you are looking for is section 2. The firmware for the mt7921 has been getting upgrades about once per month for the last 5-6 months as features are added and bugs are fixed so you might want to upgrade the amd64 install as well if it is needed.
Let us know if that helps... and I am still looking for someone to write a review on this adapter for the plug and play list.
@morrownr
@morrownr in regards to the review i'd be glad to help, i've got time tomorrow and can knock that out at least for Kali on hardware and some VM's etc. ill do some tests to make sure all is well, ive already made minor configurations to the way it runs on my machine to optimize performance, but i can make documentation about that as well. As for the firmware files I'll report back on that tomorrow as well.
Hello! @morrownr so i got around to installing the firmware as the guide describes, after reboot i plugged in the adapter directly into the phones USB-C port and checked dmesg, this was the output, unplugged then plugged in again. not super well versed in this level of software so i dont know what exactly anything means, but it seems there's not enough power or for some reason the internal hub (usb port, i guess?) keeps disconnecting the adapter (e.g. [ 1202.990024] usb usb5-port1: disabled by hub (EMI?), re-enabling...) but not entirely sure to be honest.
#dmesg Output on kali-rockchip-6.1 on Pinephone Pro:
[ 1138.467885] hub 6-0:1.0: USB hub found
[ 1138.467971] hub 6-0:1.0: 1 port detected
[ 1138.742013] usb 5-1: new high-speed USB device number 2 using xhci-hcd
[ 1138.894004] usb 5-1: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[ 1138.894039] usb 5-1: New USB device strings: Mfr=6, Product=7, SerialNumber=8
[ 1138.894055] usb 5-1: Product: Wireless_Device
[ 1138.894068] usb 5-1: Manufacturer: MediaTek Inc.
[ 1138.907418] usb 5-1: can't set config # 1, error -71
[ 1157.608917] rk818-bat: changed: dsoc=88, rsoc=87, v=4004, ov=4243 c=-581, cap=2352, f=2708, st=charge off, hotdie=0
[ 1157.608970] rk818-bat: dl=97, rl=94, v=4086, halt=0, halt_n=0, max=0, init=0, sw=0, calib=0, below0=0, force=0
[ 1179.479769] usb 5-1: USB disconnect, device number 2
[ 1179.491789] typec-extcon typec-extcon: extcon changed sdp=0 cdp=0 dcp=0 usb=0 usb_host=0 dp=0
[ 1179.492300] xhci-hcd xhci-hcd.2.auto: remove, state 4
[ 1179.492330] usb usb6: USB disconnect, device number 1
[ 1179.494931] xhci-hcd xhci-hcd.2.auto: USB bus 6 deregistered
[ 1179.495463] xhci-hcd xhci-hcd.2.auto: remove, state 1
[ 1179.495543] usb usb5: USB disconnect, device number 1
[ 1188.391282] hub 5-0:1.0: USB hub found
[ 1188.391359] hub 5-0:1.0: 1 port detected
[ 1188.392645] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[ 1188.392958] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01
[ 1188.392980] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1188.392996] usb usb6: Product: xHCI Host Controller
[ 1188.393009] usb usb6: Manufacturer: Linux 6.1-rockchip xhci-hcd
[ 1188.393022] usb usb6: SerialNumber: xhci-hcd.2.auto
[ 1188.394422] hub 6-0:1.0: USB hub found
[ 1188.394496] hub 6-0:1.0: 1 port detected
[ 1188.668970] usb 5-1: new high-speed USB device number 2 using xhci-hcd
[ 1188.810766] usb 5-1: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[ 1188.810792] usb 5-1: New USB device strings: Mfr=6, Product=7, SerialNumber=8
[ 1188.810804] usb 5-1: Product: Wireless_Device
[ 1188.810814] usb 5-1: Manufacturer: MediaTek Inc.
[ 1188.810824] usb 5-1: SerialNumber: 000000000
[ 1188.868637] usb usb5-port1: disabled by hub (EMI?), re-enabling...
[ 1188.883294] usb 5-1: USB disconnect, device number 2
[ 1199.075096] Bluetooth: hci1: Execution of wmt command timed out
[ 1199.081759] Bluetooth: hci1: Failed to send wmt patch dwnld (-110)
[ 1199.088874] Bluetooth: hci1: Failed to set up firmware (-110)