Joined: 21 Jan 2017 Posts: 1783 Location: Illinois Moderator
Posted: Thu Dec 16, 2021 17:37 Post subject:
Loaded 47853, finally showed up on the nightly server for R9000....
Cleared browser cache, loaded wifi page, qam was on, turned it off, cleared the cache again, refreshed the page, off status and still showing the line.
So it seems to have resolved itself on the R9000. I'll keep an eye on it.
@Joker, what else have you found missing across windows?
Are they back after 47849 builds? _________________ FORUM RULES
Was wondering if TurboQAM (QAM256) support even worked as I've posted previously about experiencing 2.4GHz clients failing to connect repeatedly whenever I enabled the option with the following error in the log:
Dec 16 20:10:57 Linksys EA8500 daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx MLME: auth request, signal -51 (Accepted)
Dec 16 20:10:57 Linksys EA8500 daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Dec 16 20:10:57 Linksys EA8500 daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx MLME: assoc request, signal -49 (Accepted)
Dec 16 20:10:57 Linksys EA8500 daemon.notice hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: Could not set STA to kernel driver
As stated previously, this issue appeared for me after build 02-06-2021-r45690.
Doing a bit more research just now and I found this issue was reported with OpenWRT and the fix was to disable 802.11w management frame protection. Of course, on my EA8500 this option was already disabled...
However, I changed 802.11w management frame protection to Auto and now all is well!
Joined: 21 Jan 2017 Posts: 1783 Location: Illinois Moderator
Posted: Fri Dec 17, 2021 1:55 Post subject:
sumbuddie wrote:
However, I changed 802.11w management frame protection to Auto and now all is well!
802.11W is totally broken, afaik, and should not be used at all, especially in conjunction with 802.11r above it.
My EA8500's have never had issues with qam 256 and clients like you report, but I never touched 802.11w either. All three of my deployments are off-site so I cannot test it on that hardware... maybe someone else can chime in to better test things out... _________________ FORUM RULES
Joined: 21 Jan 2017 Posts: 1783 Location: Illinois Moderator
Posted: Fri Dec 17, 2021 5:00 Post subject:
sumbuddie wrote:
Doing a bit more research just now and I found this issue was reported with OpenWRT and the fix was to disable 802.11w management frame protection. Of course, on my EA8500 this option was already disabled...
However, I changed 802.11w management frame protection to Auto and now all is well!
Why can’t my mobile device connect to the MFP 802.11w enabled infrastructure device?
There are certain restrictions for some wireless clients to communicate with MFP-enabled infrastructure devices. MFP adds a long set of information elements to each probe request or SSID beacon. Some wireless clients such as PDAs, smartphones, barcode scanners, and so forth have limited memory and Central Processing Unit (CPU). So, you are not able to process these requests or beacons. As a result, you fail to see the SSID entirely, or you are not able to associate with these infrastructure devices, due to a misunderstanding of SSID capabilities. This issue is not specific to MFP. This also occurs with any SSID that has multiple information elements (IEs). It is always advisable to test MFP-enabled SSIDs on the environment with all your available client types before you deploy it in real time. _________________ FORUM RULES
802.11W is totally broken, afaik, and should not be used at all, especially in conjunction with 802.11r above it.
My EA8500's have never had issues with qam 256 and clients like you report, but I never touched 802.11w either. All three of my deployments are off-site so I cannot test it on that hardware... maybe someone else can chime in to better test things out...
Had some time to tinker with it and in my case regardless of setting 802.11w Management Frame Protection to either Enabled or Disabled with TurboQAM enabled and my 2.4GHz clients struggle to connect.
Furthermore, setting the option back to Auto no longer fixes it either.
The more I tinkered with the options, eventually my EA8500 crashed completely (both Wi-Fi channels disappeared and Web GUI was inaccessible)... (had to disconnect/reconnect power to bring it back online)
Disabled TurboQAM and all is well again.
I've got 802.11r (FT) support disabled - reading up on this now...
Again, I started experiencing this issue after build v.02-06-2021-r45690 - was fine prior. Others have posted similar issues when TurboQAM is enabled.
Are you following all the guidelines laid out in the best qca wifi settings sticky?
Yep - have gone over that multiple times (and read your sticky as well - Thanks!). In my case, I don't think there's any benefit to enabling 802.11r (FT) support.
blkt wrote:
Using Firmware Type DD-WRT or VANILLA? Remember an issue about enabling qam256 with dd-wrt fw type.
(had to disconnect/reconnect power to bring it back online)