MT7612u (Netgear A6210) 5ghz Issues #412
Comments
|
Try a different channel. |
|
Hi @localboast
Interesting. The A6210 supports 80 MHz channel width and VHT. Not sure what is going on with that.
Channel 149 is not a DFS channel in the US. 52 - 144 are the DFS channels in the US. I use DFS channel 116, 160 MHz width on my primary router (I am in the US also).
I agree with @bjlockie . Try changing your channel to 36 for testing, then report. FYI: I have an A6210 and can test it if needed. |
Using channel 36 for debugging is good advice. However channel 149 should work oob though, the extended 5ghz doesn't start until channel 166. If a usb adapter is 802.11ac it should support it.There is the possibility that 80mhz is not enabled in the driver properties, so you may have to enable it. |
|
Usually driver files for editing properties are in |
You are correct, I had to chuckle a little as you used the word
The mt7612u driver is a modern mac80211, standards compliant, in-kernel driver. It only has one module parameter that is unlikely to be the cause of the problem in this case. Older Realtek out-of-kernel, non standards compliant drivers did use a lot of module parameters. The mt7612u driver is very stable and time tested. I suspect the cause could be a setting or bug in the AP/router. I think testing other channels is a good place to start. I have multiple adapters that use the mt7921u driver. It should just work but the variability in the code to support wifi can cause issues to come up. |
That's a good point about the AP settings. |
|
Wow, thanks for the immediate responses! Apologize about stating 149 was DFS, my mistake. I'm hoping to not have to switch channels as I guess out of principal I shouldn't have to for a single malfunctioning device haha. I'll try taking a look at the properties as mentioned. My network has tons of different wireless and IoT clients all without issue for literal years, so I don't think it's anything on my Unifi network's end. 2.4 works but is painfully slow, maybe 25ish feet from AP. Using WPA2 still. Anywho I'll experiment with what everyone has suggested here tomorrow and report back. I have seen whispers in other threads that folks only got 5ghz working on channels in the 30s and lower with this adapter. |
I had time so I connected my A6210. This message is brought to you by my A6210 connected to channel 116 DFS, 80 MHz channel width and... using WPA3. My distro is Debian 12. I guess maybe tomorrow I can change my primary wifi router to channel 149 and see what happens. I've done a lot of testing on WPA3. My testing has shown that the chipset has little to do with WPA3 support. The driver and some parts of the distro do have a lot to do with it. I have very old adapters with WiFi 4 chipsets that support WPA3. All in-kernel drivers that I have tested support WPA3 but it would not hurt to turn it off in the wifi router just as a test.. |
|
Couldn't help myself: My Alfa ACM with the same chipset can do over 400 Mbps but it has a tx power of 20 whereas Netgear decided the A6210 only needed tx power of 18 plus the ACM probably has antennas that help. I have 2 walls to the AP so this is not bad. The A6210 is a cool little adapter, especially for going on the road. |
I've haven't heard of drivers backporting WPA3 to older/less capable devices, thats pretty cool. Advertising for the 7612u mentions WPA2 and before, but not WPA3, my bad. |
|
Alright I'm back. Moved to channel 36 on 40mhz and it's good! To be honest should have looked at this (in Ubiquiti Wifiman app) a while ago as I'm better here anyway, and do not need 80mhz throughput. Less congested here. @morrownr thank you for testing this along side me, verdict is still out on this adapter supporting 149+. One thing I'll mention is that in Arch Network settings, I am in Infastructure mode and it's grabbing 5ghz now. However if I change to Adhoc, my only Band option is A for 5ghz. If i select this and channel 36 (which I'm currently on), it will not connect. I have to remain in Infastructure and let it "auto" grab 5ghz. Your results may vary here I imagine, based on distro, no idea. Looking at the image in the first comment on this post, perhaps this adapter doesn't like UNII-3? I'll wait until someone else tries their luck inthat range, but it did not work for me. At least we know 80mhz and WPA3 is supported as well. |
I changed my main wifi router to channel 149 this morning. It worked fine and with 80 MHz range. It is highly likely that your A6210 is identical to mine. There is little difference in capability between different adapters if they use the same chipset. Makers can select and use their own antennas, amps and various materials to make the physical adapter but the chipset is what gives the capability so not much variance. In this case, given the same maker and model, the adapters are likely identical. So, while your jury may still be deliberating, mine is back and their verdict was that the A6210 is innocent of all charges related to its failure to connect to channel 149. If you had another wifi router to test with, that would be great. If you don't, do you have a spare RasPi and another usb wifi adapter? What you could do is try channel 157 with both 40 and 80 widths in the router to see what you get. I've seen a lot of variety in the coding of routers . If your router supports DFS, you could try channels 100 or 116 to see if either of both is good to use in your area and if all of your 5 GHz clients work with DFS, you might as well use it as there will likely be no congestion. |
|
That's great news! You can close this issue, as it sounds like it's something to do with my setup specifically. I may experiment some more in the future, but for now I'm happy. Many thanks for everyone's input! |
If the driver uses mac80211, which is the case here, it gets WPA3 support automatically, even if the chip itself is not capable. |
|
__
How does the driver work around the previous incapability of using WPA3? |
|
If the chip doesn't support WPA3, the driver tells this to mac80211, which will handle the encryption in software. The advertising may be based on what the manufacturer's driver can do. I think Mediatek produces out-of-kernel drivers too, like Realtek, in addition to developing the in-kernel drivers. |
Hello,
I'm at a loss here, scoured the internet and cannot find a solution. I'm on Arch linux (6.8.1-arch1-1). For the life of me, I cannot get this adapter to connect to 5ghz. My network is Ubiquiti AP > DFS 149 > 80mhz. Any ideas at all would be helpful, I have installed wireless-regdb and enabled only US in /etc/conf.d/wireless-regdom as I am in the US.
dmesg | grep -i firmware
mt76x2u 1-5:1.0: Firmware Version: 0.0.00dmesg
[ 28.580004] wlan0: 80 MHz not supported, disabling VHT [ 29.446140] wlan0: authenticate with e0:63:da:23:f3:9e (local address=b0:39:56:98:b5:fa) [ 29.446147] wlan0: send auth to e0:63:da:23:f3:9e (try 1/3) [ 29.449037] wlan0: authenticated [ 29.450251] wlan0: associate with e0:63:da:23:f3:9e (try 1/3) [ 29.454556] wlan0: RX AssocResp from e0:63:da:23:f3:9e (capab=0x1411 status=0 aid=11) [ 29.647086] wlan0: associated [ 29.647125] wlan0: Limiting TX power to 27 (27 - 0) dBm as advertised by e0:63:da:23:f3:9e [ 31.983366] warning: `ThreadPoolForeg' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211 [ 69.379554] wlan0: deauthenticating from e0:63:da:23:f3:9e by local choice (Reason: 3=DEAUTH_LEAVING) [ 97.485482] wlan0: Trigger new scan to find an IBSS to join [ 111.401932] wlan0: Creating new IBSS network, BSSID 46:49:cb:35:c0:ad [ 176.986299] wlan0: authenticate with e2:63:da:33:f3:9f (local address=b0:39:56:98:b5:fa) [ 176.986306] wlan0: send auth to e2:63:da:33:f3:9f (try 1/3) [ 176.988530] wlan0: authenticated [ 176.990780] wlan0: associate with e2:63:da:33:f3:9f (try 1/3) [ 176.993726] wlan0: RX AssocResp from e2:63:da:33:f3:9f (capab=0x1111 status=0 aid=17) [ 177.187262] wlan0: associated [ 246.818630] wlan0: deauthenticating from e2:63:da:33:f3:9f by local choice (Reason: 3=DEAUTH_LEAVING) [ 359.692008] wlan0: 80 MHz not supported, disabling VHT [ 360.555686] wlan0: authenticate with e0:63:da:23:f3:9e (local address=b0:39:56:98:b5:fa) [ 360.555692] wlan0: send auth to e0:63:da:23:f3:9e (try 1/3) [ 360.558595] wlan0: authenticated [ 360.560752] wlan0: associate with e0:63:da:23:f3:9e (try 1/3) [ 360.573104] wlan0: RX AssocResp from e0:63:da:23:f3:9e (capab=0x1411 status=0 aid=11) [ 360.762652] wlan0: associated [ 360.875611] wlan0: Limiting TX power to 27 (27 - 0) dBm as advertised by e0:63:da:23:f3:9eiw 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)iw phy phy0 channels
Band 1: * 2412 MHz [1] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40+ * 2417 MHz [2] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40+ * 2422 MHz [3] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40+ * 2427 MHz [4] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40+ * 2432 MHz [5] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40- HT40+ * 2437 MHz [6] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40- HT40+ * 2442 MHz [7] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40- HT40+ * 2447 MHz [8] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40- * 2452 MHz [9] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40- * 2457 MHz [10] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40- * 2462 MHz [11] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40- * 2467 MHz [12] (disabled) * 2472 MHz [13] (disabled) * 2484 MHz [14] (disabled) Band 2: * 5180 MHz [36] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40+ VHT80 * 5200 MHz [40] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40- HT40+ VHT80 * 5220 MHz [44] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40- HT40+ VHT80 * 5240 MHz [48] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40- HT40+ VHT80 * 5260 MHz [52] Maximum TX power: 18.0 dBm Radar detection Channel widths: 20MHz HT40- HT40+ VHT80 DFS state: usable (for 635 sec) DFS CAC time: 60000 ms * 5280 MHz [56] Maximum TX power: 18.0 dBm Radar detection Channel widths: 20MHz HT40- HT40+ VHT80 DFS state: usable (for 635 sec) DFS CAC time: 60000 ms * 5300 MHz [60] Maximum TX power: 18.0 dBm Radar detection Channel widths: 20MHz HT40- HT40+ VHT80 DFS state: usable (for 635 sec) DFS CAC time: 60000 ms * 5320 MHz [64] Maximum TX power: 18.0 dBm Radar detection Channel widths: 20MHz HT40- VHT80 DFS state: usable (for 635 sec) DFS CAC time: 60000 ms * 5500 MHz [100] Maximum TX power: 18.0 dBm Radar detection Channel widths: 20MHz HT40+ VHT80 DFS state: usable (for 635 sec) DFS CAC time: 60000 ms * 5520 MHz [104] Maximum TX power: 18.0 dBm Radar detection Channel widths: 20MHz HT40- HT40+ VHT80 DFS state: usable (for 635 sec) DFS CAC time: 60000 ms * 5540 MHz [108] Maximum TX power: 18.0 dBm Radar detection Channel widths: 20MHz HT40- HT40+ VHT80 DFS state: usable (for 635 sec) DFS CAC time: 60000 ms * 5560 MHz [112] Maximum TX power: 18.0 dBm Radar detection Channel widths: 20MHz HT40- HT40+ VHT80 DFS state: usable (for 635 sec) DFS CAC time: 60000 ms * 5580 MHz [116] Maximum TX power: 18.0 dBm Radar detection Channel widths: 20MHz HT40- HT40+ VHT80 DFS state: usable (for 635 sec) DFS CAC time: 60000 ms * 5600 MHz [120] Maximum TX power: 18.0 dBm Radar detection Channel widths: 20MHz HT40- HT40+ VHT80 DFS state: usable (for 635 sec) DFS CAC time: 60000 ms * 5620 MHz [124] Maximum TX power: 18.0 dBm Radar detection Channel widths: 20MHz HT40- HT40+ VHT80 DFS state: usable (for 635 sec) DFS CAC time: 60000 ms * 5640 MHz [128] Maximum TX power: 18.0 dBm Radar detection Channel widths: 20MHz HT40- HT40+ VHT80 DFS state: usable (for 635 sec) DFS CAC time: 60000 ms * 5660 MHz [132] Maximum TX power: 18.0 dBm Radar detection Channel widths: 20MHz HT40- HT40+ VHT80 DFS state: usable (for 635 sec) DFS CAC time: 60000 ms * 5680 MHz [136] Maximum TX power: 18.0 dBm Radar detection Channel widths: 20MHz HT40- HT40+ VHT80 DFS state: usable (for 635 sec) DFS CAC time: 60000 ms * 5700 MHz [140] Maximum TX power: 18.0 dBm Radar detection Channel widths: 20MHz HT40- HT40+ VHT80 DFS state: usable (for 635 sec) DFS CAC time: 60000 ms * 5720 MHz [144] Maximum TX power: 18.0 dBm Radar detection Channel widths: 20MHz HT40- VHT80 DFS state: usable (for 635 sec) DFS CAC time: 60000 ms * 5745 MHz [149] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40+ VHT80 * 5765 MHz [153] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40- HT40+ VHT80 * 5785 MHz [157] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40- HT40+ VHT80 * 5805 MHz [161] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40- HT40+ VHT80 * 5825 MHz [165] Maximum TX power: 18.0 dBm Channel widths: 20MHz HT40- HT40+ VHT80 * 5845 MHz [169] Maximum TX power: 18.0 dBm No IR Channel widths: 20MHz HT40- HT40+ VHT80 * 5865 MHz [173] Maximum TX power: 18.0 dBm No IR Channel widths: 20MHz HT40- HT40+ VHT80 * 5885 MHz [177] Maximum TX power: 18.0 dBm No IR Channel widths: 20MHz HT40- VHT80iw list
Wiphy phy0 wiphy index: 0 max # scan SSIDs: 4 max scan IEs length: 2243 bytes max # sched scan SSIDs: 0 max # match sets: 0 Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Device supports RSN-IBSS. 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: * IBSS * managed * AP * AP/VLAN * monitor * mesh point * P2P-client * P2P-GO Band 1: Capabilities: 0x1ff 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: 3839 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 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.0 MHz [1] (18.0 dBm) * 2417.0 MHz [2] (18.0 dBm) * 2422.0 MHz [3] (18.0 dBm) * 2427.0 MHz [4] (18.0 dBm) * 2432.0 MHz [5] (18.0 dBm) * 2437.0 MHz [6] (18.0 dBm) * 2442.0 MHz [7] (18.0 dBm) * 2447.0 MHz [8] (18.0 dBm) * 2452.0 MHz [9] (18.0 dBm) * 2457.0 MHz [10] (18.0 dBm) * 2462.0 MHz [11] (18.0 dBm) * 2467.0 MHz [12] (disabled) * 2472.0 MHz [13] (disabled) * 2484.0 MHz [14] (disabled) Band 2: Capabilities: 0x1ff 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: 3839 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 (0x318001b0): Max MPDU length: 3895 Supported Channel Width: neither 160 nor 80+80 RX LDPC short GI (80 MHz) TX STBC 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: not supported 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.0 MHz [36] (18.0 dBm) * 5200.0 MHz [40] (18.0 dBm) * 5220.0 MHz [44] (18.0 dBm) * 5240.0 MHz [48] (18.0 dBm) * 5260.0 MHz [52] (18.0 dBm) (radar detection) * 5280.0 MHz [56] (18.0 dBm) (radar detection) * 5300.0 MHz [60] (18.0 dBm) (radar detection) * 5320.0 MHz [64] (18.0 dBm) (radar detection) * 5500.0 MHz [100] (18.0 dBm) (radar detection) * 5520.0 MHz [104] (18.0 dBm) (radar detection) * 5540.0 MHz [108] (18.0 dBm) (radar detection) * 5560.0 MHz [112] (18.0 dBm) (radar detection) * 5580.0 MHz [116] (18.0 dBm) (radar detection) * 5600.0 MHz [120] (18.0 dBm) (radar detection) * 5620.0 MHz [124] (18.0 dBm) (radar detection) * 5640.0 MHz [128] (18.0 dBm) (radar detection) * 5660.0 MHz [132] (18.0 dBm) (radar detection) * 5680.0 MHz [136] (18.0 dBm) (radar detection) * 5700.0 MHz [140] (18.0 dBm) (radar detection) * 5720.0 MHz [144] (18.0 dBm) (radar detection) * 5745.0 MHz [149] (18.0 dBm) * 5765.0 MHz [153] (18.0 dBm) * 5785.0 MHz [157] (18.0 dBm) * 5805.0 MHz [161] (18.0 dBm) * 5825.0 MHz [165] (18.0 dBm) * 5845.0 MHz [169] (18.0 dBm) (no IR) * 5865.0 MHz [173] (18.0 dBm) (no IR) * 5885.0 MHz [177] (18.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 * probe_client * set_noack_map * register_beacons * start_p2p_device * set_mcast_rate * connect * disconnect * channel_switch * set_qos_map * set_multicast_to_unicast * set_sar_specs software interface modes (can always be added): * AP/VLAN * monitor valid interface combinations: * #{ IBSS } <= 1, #{ managed, AP, mesh point, P2P-client, P2P-GO } <= 2, total <= 2, #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 low priority scan. Device supports scan flush. Device supports AP scan. 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) Driver/device bandwidth changes during BSS lifetime (AP/GO mode) Device supports configuring vdev MAC-addr on create. max # scan plans: 1 max scan plan interval: -1 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: * [ VHT_IBSS ]: VHT-IBSS * [ RRM ]: RRM * [ 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 * [ SCAN_RANDOM_SN ]: use random sequence numbers in scans * [ SCAN_MIN_PREQ_CONTENT ]: use probe request with only rate IEs in scans * [ AIRTIME_FAIRNESS ]: airtime fairness scheduling * [ AQL ]: Airtime Queue Limits (AQL) * [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support * [ DEL_IBSS_STA ]: deletion of IBSS station support * [ SCAN_FREQ_KHZ ]: scan on kHz frequency support * [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support * [ POWERED_ADDR_CHANGE ]: can change MAC address while upThe text was updated successfully, but these errors were encountered: