WiFi 6 vs WiFi 6e

[morrownr]

2022-03-02 - Updated: 2022-03-05

WiFi 6 vs WiFi 6e

If you happen to be shopping for a new wifi router or wifi adapter or wifi card, you have probably run across the terms WiFi 6 and WiFi 6e in the ads. Many of the ads contain bad information. Even some articles I have read seem to do more to confuse the issue than to clarify it. Let me try to clarify a few things.

The difference between WiFi 6 and WiFi 6e is simple. WiFi 6e supports new, previously unused channels in the 6 GHz part of the radio spectrum. As wifi use has continued to increase, existing 2.4 GHz and 5 GHz channels have become more congested and since wifi technology is based on sharing, in areas where a lot of wifi routers and access points are located, things can slow down a lot. This seems to be particularly acute with 5 GHz due to the reality that there are very few channels to choose from. Many countries only allow the 36-48 channels as non-DFS channels and since many devices do not support DFS channels, and since it seems everyone wants 80 MHz channels width which takes all channels between 36 and 48, we effectively have only one channel to use. Even in countries that offer channels 149-165, that is really still only two channel options. I have questioned the wisdom of the EE's that wrote the WiFi specs going all the way back to the beginning but that is a topic for another day.

We have needed new channels for some time but no new channels were approved when WiFi 6 came to market. Now new channels have been approved and WiFi 6e adds the capability to use these new channels. My opinion is that WiFi 6 is mostly a waste of time and I will be waiting until WiFi 6e has matured more until I get serious about upgrading things around here. Sure, I have a new little laptop that is WiFi 6 capable. It has a Mediatek mt7921 chipset that is plug and play with the Ubuntu 21.10 that I installed on the laptop. Since I do not have a WiFi 6 or WiFi 6e capable router, it operates as WiFi 5, which is still several times faster that what I actually need.

So, what does all of this mean to your average home or small business internet user? If you are located in a highly congested area such as an apartment building, you will likely be happier waiting for WiFi 6e. If you are located in an area that is lightly congested or has no congestion at all, WiFi 4 likely meets or exceeds your needs and this talk of WiFi 6 and WiFi 6e is just noise.

Additional info:

Here is a link to remind you of a few good-to-know things about WiFi:

https://metis.fi/en/2017/10/txpower/

Since I maintain 5 repos for drivers and two primary informational repos, including this one, I get all kinds of questions. It seems that it is rare when a week goes by when I don't get ask about how to turn txpower up on an adapter. My experience is such that I have rarely seen increasing txpower with low cost, <$20 USD, wifi adapters do much good for range. Remember that this technology requires txpower and receive capability to both be in place to increase range. Most cheap adapters do not have the antenna quality to allow increasing txpower to be of much help. It costs to make an adapter that has very good range as the quality of the antenna and internal amp need to be good. An example of a good long range adapter is the ALFA ACHM, which costs around $40USD.

Should we expect WiFi 6e WiFi adapters to be available shortly? (update: see next paragraph). So far there has been only one WiFi 6 capable chipset made available for use in USB WiFi adapters. It is the rtl8832au. Realtek released an out-of-kernel driver for Linux but it is simply a terrible driver so I have not made it public because I don't want to encourage Linux users to buy adapters based on that chipset. Will we see Mediatek release WiFi 6e chipset for USB adapters soon? I don't know but am hoping for a mt7921ku chipset sometime this year. I hope it happens. The base driver is already in the kernel so adding USB support is all that is needed.

Edit: Update to the above paragraph: A driver for the Mediatek mt7921u chipset is now going into the kernel. This is great news and we should see information regarding new USB WiFi adapters soon. The mt7921 driver that has been in the kernel since v5.12 supports both WiFi 6 and WiFi 6e.

I hope this helps.

Regards,

Nick

[felicemastro]

Hi Nick,

I installed Kali Linux 2022.4 on an old Dell Inspiron 5566 laptop. It's got the required drivers as far as I can see.

I can see that Netgear AXE3000 - USB3.0 - 2.4 GHz, 5 GHz and 6 GHz (WiFi 6E) is published as a Tri Band USB WiFi Adapters that is supported with Linux in-kernel drivers.

In my case I can see it's detected, but driver isn't being loaded, output of lshw shows:

          *-usb:0 UNCLAIMED
               description: Generic USB device
               product: Wireless_Device
               vendor: MediaTek Inc.
               physical id: 3
               bus info: usb@1:3
               version: 1.00
               serial: 000000000
               capabilities: usb-2.10
               configuration: maxpower=100mA speed=480Mbit/s

lsusb shows:
Bus 001 Device 008: ID 0846:9060 NetGear, Inc. Wireless_Device

inxi -n shows:
Network:
Device-3: NetGear Wireless_Device type: USB driver: N/A

dmesg not showing any failures:
[ 6145.673338] usb 1-3: new high-speed USB device number 9 using xhci_hcd
[ 6145.823579] usb 1-3: New USB device found, idVendor=0846, idProduct=9060, bcdDevice= 1.00
[ 6145.823590] usb 1-3: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 6145.823596] usb 1-3: Product: Wireless_Device
[ 6145.823600] usb 1-3: Manufacturer: MediaTek Inc.
[ 6145.823604] usb 1-3: SerialNumber: 000000000

This is a super old laptop, I am guessing I need USB 3 support for this WiFi adaptor to work ?

Thanks,
Felice

[morrownr]

Hi Felice,

I added this adapter to the in-kernel list last week... with a warning:

Warning: This Netgear A8000 uses a device ID that is not yet in the Linux kernel driver, mt7921u, and until that happens, users will have to add the device ID (ID 0846:9060 NetGear, Inc) and compile the driver. This is not a trival task and should only be undertaken by experienced developers.

I guess I need to post it in a better place. Nevertheless...

So, the driver is there, the chipset is there, the firmware is there and the driver does not have the device ID yet which means the driver does not recognize the adapter.

An emergency fix is to compile the driver with a patch. If you are up for doing such, let me know. Maybe we can even submit the patch and become kernel devs.

Nick

[felicemastro]

Hi Nick,
I had a feeling I missed something :). Thanks for clarifying that. I'm up for giving driver fix a shot, but never messed with that before. If you can provide some tips and guidance I can give it a shot and see how it goes.
Regards,
Felice

[morrownr]

Hi again Felice,

Thanks for clarifying that.

That is just one of those things. Chipset makers have one or more default ID's that adapter makers can use and most do but some, in this case Netgear, do not. That is always the adapter makers choice but the adapter makers do not come back to, in this case Mediatek, and tell them to tell their kernel devs to add a new ID to the kernel. So the Mediatek kernels will only know if a user tells them. The way of telling them has to be in a specific format. However, before we go there, let see...

I'm up for giving driver fix a shot, but never messed with that before.

I think I can walk you through it. If we try to just compile the kernel, it can be more complicated so it might be better just to download, edit, compile and install the kernel. That might also make it easier to make a PATCH for the kernel devs so that we don't have to do this anymore once the patch is in.

Give a breakdown of what type of system you have. Is it x86_64 or ARM64? Also, what distro are you running?

Nick

[felicemastro]

Hi Nick, thanks again for demystifying this, I had no clue.

I was originally running Kali, then switched to Ubuntu thinking it would resolve the issue with this Netgear A8000 WiFi USB adapter.

When I saw exact same problem on Ubuntu I reached out on this forum. Glad I did :).

Here is the distro info currently running (basically installed Ubuntu on an old Dell Inspiron 5566 laptop):

$ sudo uname -a
Linux dell-ubuntu 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.1 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

By the way, I have WiFi 6E router to test with, ASUS GT-AXE11000.

Regards,
Felice

[morrownr]

Felice,

We can work with Ubuntu 22.04. Keep in mind that at some point this will not be necessary but until that point you might want to take notes.

Let me start you off with some homework. Your firmware will need to be upgraded. Remember that Linux in-kernel driver come in 2 parts: the firmware files that are not part of the kernel and the driver which is part of the kernel. Here is your homework:

Go to:

https://github.com/morrownr/USB-WiFi

and select menu item 8 or go directly there with:

https://github.com/morrownr/USB-WiFi/blob/main/home/How_to_Install_Firmware_for_Mediatek_based_USB_WiFi_adapters.md

Following the instructions for the mt7921 chipset. I think it is section 2. Be very careful with the details. After you finish, your firmware should be up to date.

Now for the driver part of things: Would you like to head on up to the latest LTS kernel? 6.1? We can pull it right from Linus' site get started.

I need to pause for now as I have to run take care of some things but I'll continue when able so do your homework and let me know what kernel you want to use. I will have a checklist for you to follow so don't worry.

Nick

[felicemastro]

Homework done lol.
Also pulled latest stable kernel from kernel.org:
linux-6.1.7.tar.xz

[morrownr]

Stop at item 6 so we can work it together:

Checklist-Compiling_Linux_Mainline_Kernel

Purpose: Facilitate Testing or Adding new Device IDs

2023-01-10

Prerequisites:

A system running Linux (only Ubuntu is tested).

Access to the terminal/command line.

A user account with sudo/root privileges.

12GB of available space on the hard drive.

-----

Note: This checklist has only been tested on Ubuntu 22.10
but will likely work, possibly with minor modifications,
on numerous distros, however you should check with your
distro to confirm.

-----

1. Download the Source Code tarball from:

https://www.kernel.org/

linux-6.2-rc2tar.xz

Note: The above name will change depending on the
version of the kernel you decide to compile. Adjust
accordingly.

Note: make a directory called `src` in my home directory
and that is what I download the file to. Anywhere in your
home directory should work.

-----

2. Extract the Source Code:

$ tar xvf linux-6.2-rc2.tar.xz

-----

3. Install Required Packages:

$ sudo apt-get install git fakeroot build-essential ncurses-dev xz-utils libssl-dev bc flex libelf-dev bison

Note: The above line is specific to Debian based distros such
as Ubuntu.

-----

4. Configure Kernel:

Navigate to the `linux-6.2-rc2` directory using the cd command:

$ cd linux-6.2-rc2

Copy the existing configuration file using the cp command:

$ cp -v /boot/config-$(uname -r) .config

To make changes to the configuration file, there are two options:

Option 1: Run make:

$ make menuconfig

The command launches several scripts that open the configuration menu.

The configuration menu includes options such as firmware, file system, network, and
memory settings. Use the arrows to make a selection or choose Help to learn more about the
options. When you finish making the changes, select Save, and then exit the menu.

Option 2: Edit .config directly with a text edition:

I use `geany`:

$ geany .config

If you are intested in turning on the new support
for the below listed new Mediatek driver, make sure
the following line is as below:

Search for `MT76`.

CONFIG_MT7921U=m

Save file and exit.

If you are intested in turning on the new support for the
below listed Realtek drivers:

Search for `RTW88`.

To turn on support for the rtl8822bu, rtl8812bu, rtl8821cu and rtl8811cu
chipsets, make sure the following lines are as below:

CONFIG_RTW88=m
CONFIG_RTW88_CORE=m
CONFIG_RTW88_USB=m
CONFIG_RTW88_8822B=m
CONFIG_RTW88_8821C=m
CONFIG_RTW88_8822BU=m
CONFIG_RTW88_8821CU=m

Save file and exit.
---

5. Prevent errors related to certs.

If you are compiling the kernel on Ubuntu or on any distros based on Ubuntu,
you may receive the following error that interrupts the building process:

No rule to make target 'debian/canonical-certs.pem

To prevent the above problem, disable the conflicting security certificates
by executing the two commands below:

$ scripts/config --disable SYSTEM_TRUSTED_KEYS
$ scripts/config --disable SYSTEM_REVOCATION_KEYS

-----

6. Now is the time to patch any files if you are going to test patches.

-----

7. Compile the kernel.

$ make -j$(nproc)

The process of compiling the Linux kernel takes some time to complete.

Note: If the compile stops, hit Enter until it starts again (this is
related to the cert stuff above).

---

8. Install the required modules:

$ sudo make modules_install

---

9. Install the kernel:

$ sudo make install

---

10. Reboot and check kernel:

$ uname -r

-----

For uninstalling the kernel installed from source, run:

$ sudo rm -rf /lib/modules/kernel_version
Example: $ sudo rm -rf /lib/modules/6.2.0-rc2

$ sudo rm -f /boot/vmlinuz-kernel_version*
Example: $ sudo rm -f /boot/vmlinuz-6.2.0-rc2*

$ sudo rm -f /boot/initrd.img-kernel_version*
Example: $ sudo rm -f /boot/initrd.img-6.2.0-rc2*

$ sudo rm -f /boot/config-kernel_version*
Example: $ sudo rm -f /boot/config-6.2.0-rc2*

$ sudo rm -f /boot/System.map-kernel_version*
Example: $ sudo rm -f /boot/System.map-6.2.0-rc2*

Finally, after uninstalling the kernel, run:

$ sudo update-grub

to clean the grub menu.

-----

Happy compiling!

[felicemastro]

Done.
I ended up fetching linux-6.2-rc4 from kernel.org and used this one instead of the one I previously stated.
I added this line to .config:
CONFIG_MT7921U=m

At step 6 now, waiting.

[morrownr]

Hold on... I just made it back home and have to fix dinner. I'll be back...

[morrownr]

I downloaded linux-6.2-rc4

We need to be on the same sheet of music.

The following is a recent post in linux-wireless to add an ID for the same chipset so we can use it as an example. As you can see below, the file that we need to modify is drivers/net/wireless/mediatek/mt76/mt7921/usb.c.

[PATCH] wifi: mt76: mt7921u: add support for Comfast CF-952AX

Comfast CF-952AX is a MT7921 based USB WiFi dongle with custom
VID/PID. Add an entry for it.

Signed-off-by: Chuanhong Guo <[email protected]>
---
 drivers/net/wireless/mediatek/mt76/mt7921/usb.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/net/wireless/mediatek/mt76/mt7921/usb.c b/drivers/net/wireless/mediatek/mt76/mt7921/usb.c
index 5321d20dcdcb..a0778ecdb995 100644
--- a/drivers/net/wireless/mediatek/mt76/mt7921/usb.c
+++ b/drivers/net/wireless/mediatek/mt76/mt7921/usb.c
@@ -15,6 +15,9 @@
 static const struct usb_device_id mt7921u_device_table[] = {
        { USB_DEVICE_AND_INTERFACE_INFO(0x0e8d, 0x7961, 0xff, 0xff, 0xff),
                .driver_info = (kernel_ulong_t)MT7921_FIRMWARE_WM },
+       /* Comfast CF-952AX */
+       { USB_DEVICE_AND_INTERFACE_INFO(0x3574, 0x6211, 0xff, 0xff, 0xff),
+               .driver_info = (kernel_ulong_t)MT7921_FIRMWARE_WM },
        { },
 };

--
2.39.0

Give me a chance to make the modification and pass it to you.

Nick

[felicemastro]

Ok.

[morrownr]

usb.c.tar.gz

There are 3 added lines, starting on line 18.

[felicemastro]

Hey Nick good news. Compiled kernel with your fix and now I see the A8000.
Not so good news is I cannot see my 6GHz SSID. I only see my 2.4/5 GHz SSIDs.
When I ran "make -j$(nproc)" I was prompted with tons of options (y/n) NEW sort of thing... I just kept pressing enter assuming default values were fine ... maybe there is some setting I missed for 6Ghz ? Not sure have not investigated yet ... wondering if you might know anything about it ?

[morrownr]

Hey Felice,

Compiled kernel with your fix and now I see the A8000.

That is good news. Kind of a pain in the backside but it will be corrected in time. Once you are satisfied that the ID fixed the problem, and it sounds like it did, we can work on a PATCH. You need to be on the books as a Linux kernel dev? Right?

Not so good news is I cannot see my 6GHz SSID. I only see my 2.4/5 GHz SSIDs.

That is likely an issue with regbd or country code and not an issue with the driver. I don't have a 6 GHz AP setup yet but maybe if you give me some of the settings for 6 GHz in your router, maybe we can figure something out. What do you get when you run:

$ iw reg get

There was another guy in one of these issues that told me last week he had the Netgear A8000 and it was working fine. He had already figured out the ID thing and knew how to compile but he did not mention if he tested 6 GHz.

When I ran "make -j$(nproc)" I was prompted with tons of options (y/n) NEW sort of thing... I just kept pressing enter assuming default values were fine ... maybe there is some setting I missed for 6Ghz ?

Doubt that has anything to do with 6 GHz. I remember a couple of options having to do with how Ubuntu does certs but not so much. Maybe I need to compile this baby and see.

Nick

[felicemastro]

Hi Nick,

Not sure what you mean by "you need to be on the books as a Linux kernel dev". Can you clarify please ?

$ 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)
/Felice

[felicemastro]

By the way, I see this 6GHz SSID with my Samsung Galaxy Tablet S8+. I'm confident the router side is ok.

[morrownr]

Not sure what you mean by "you need to be on the books as a Linux kernel dev". Can you clarify please ?

If you send in a patch that is accepted then your name is listed as a kernel dev.

By the way, I see this 6GHz SSID with my Samsung Galaxy Tablet S8+. I'm confident the router side is ok.

Understand.

(5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN

That is the 6 GHz. I don't understand what the problem could be. Have you checked to see if the other 2 bands are working well?

I'll see if I can find the other guy that had the A8000. If I can, I'll bring him into the conversation.

[felicemastro]

Ah yeah I am ok with my name listed. Looks good on CV, although not looking for a job LOL.

Yes I managed to connect with 5GHz SSID, no issues.

Thanks for reaching out to other guy.

[felicemastro]

Hi Nick,

Been digging a litte more. Still cannot understand why this bloody A8000 adapter isn't "seeing" my 6GHz SSID :-(.

Besides the Samsung Galaxt S8+ tablet, I managed to verify 6GHz connection with a Samsung Galaxy S22+ smartphone as well.

My ASUS GT-AXE11000 web GUI does not seem to have any settings for country selection, however I saw these nvram params:
fb_country=Canada
modem_country=
wl0_country_code=US
wl0_country_rev=699
wl1_country_code=US
wl1_country_rev=699
wl2_country_code=US
wl2_country_rev=699
wil_country_code=US
wl_country_rev=699

As you can see the "wl" entries have US setting. So they indeed should match country in regulatory "iw reg" setting.

Furthermore, adapter is showing "no IR" for this 6GHz band (better than disabled). Not sure whether this is expected ?

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)

[morrownr]

@felicemastro

Let me recommend that you post a new issue that includes a synopsis of the details thus far. The problem with the current location is that it is an old thread and may not be seen by many people. A new thread should help.

I hate not to dive in to research the issue but I have some things I have to knock out this weekend.

What I do know is that when I tried to set up 6 GHz in AP mode on my wifi router running OpenWRT, I had to set country as FR (France) or DE (Germany) and it appeared to work but I really had no way to test it since 2 dod not have 2 devices with 6 GHz capability yet. I will at some point but I am not there yet. There are some smart people running around this forum so maybe the answer can be found.

Nick

[felicemastro]

Sounds good, will do Nick.
Regarding your fix for A8000 adapter, you all good with that? You need anything from me ?

[bjlockie]

What channel is it on?

[felicemastro]

For the 6GHz SSID, Merlin web GUI shows:
Current Control Channel: 197

And here is the full output of "sudo iw list" from my Dell running Ubuntu with the A8000 USB WiFi 6E adaptor:

$ sudo 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: 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
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: 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
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: 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
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
* set_sar_specs
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 } <= 2, #{ AP } <= 1,
total <= 2, #channels <= 2
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

[felicemastro]

Hey bjlockie, thanks for giving me idea to check the channel. It was set to auto. I changed it to static setting ... channel # 37 and voila I was able to finally see my 6GHz SSID !

Still wondering though why the other channel not working, 197 is legit, right ?

One weird thing that happened though while trying to connect to this 6GHz SSID. For some reason iw reg get was showing 00 instead of US. I could swear it was US prior. I wasn't able to connect until I used iw reg set US and toggled wifi.

[bjlockie]

Seems like it should work:

* 6135 MHz [37] (12.0 dBm) (no IR)
* 6935 MHz [197] (12.0 dBm) (no IR)

Maybe something to do with reg. stuff which is really complicated under Linux.