I started flashing my router collection to 23.05.0-rc4 with images from the Image Builder. I have two wired, dumb AP ubnt_unifiac-lites w/ VLANs and 4 WiFi SSIDs per radio and they are fine, as well as a tplink_archer-c7 v2 and ubnt_unifi-ap-lr that participate in a mesh w/ GRE tunnels as wired source/wireless dest.
Everything is fine so far. I'd like to highlight GRE tunnels not working in 23.05.0-rc# where basically the max length of an interface name changed between versions and now silently fails if the interface name is too long, which caused me quite a bit of grief and consternation when testing 23.05.0-rc#.
For my main router, I still suffer from the iptables incompatibility issues w/ fwknopd, mwan3, and pbr (the latter two documented in Implementing policy routing in (or compatible with) mwan3). Given that 21.02 is soon to no longer be supported, I'm wondering if anyone knows what fwknopd's and mwan3's plans are for working with OpenWrt going forward?
23.05.0 (final) has been tagged in GIT and it is being built. If no major issue is found during the build it is likely to be officially announced/released on this weekend or early next week.
BTW, this is just my own opinion based on what I've observed (git tag and draftrelease notes), it is nothing official.
I was able to use my Netgear WAX206 5GHz WiFi with 160 MHz channel width until 23.05.0-rc2, with rc3 (same settings) the channel width was reduced to 80 MHz and it stayed the same with rc4.
Does anyone else have the same issues with rc3 and rc4 and is there a possible way to fix this?
It's Germany and before I used automatic channel selection. With automatic channel selection it was using channel 104 with 80 MHz, now I changed it to the non DFS channel 36 that my WAX220 is using in the upper floor with 160 MHz channel width but it is still 80 MHz.
From what I found it should be allowed in the channels 36 to 64 and 100 to 128 in Germany but switching to channel 100 and waiting for 10 minutes also didn't make any difference.
Thanks for correcting me. According to the regulatory rules printed by iw reg get, 160 MHz bandwidth is only allowed in the 5 GHz band if the whole transmission (not just the center frequency) fits into the interval between 5470 and 5725 MHz. This means "channel 100".
I could not find anything in the output of iw phy that would have disallowed the 160 MHz operation.
Please try again, wait 10 minutes again, and provide the whole system log (logread) via the pastebin.
Thank you very much. The funny thing is that the WAX220 (my other Netgear device, also running rc4) is giving me the exatly same output for "iw reg get" but decides to open up a 5GHz WiFi with 160 MHz on channel 36 with automatic channel selection.
What exactly do you want me to do before waiting for another 10 minutes? The WAX206 is still on channel 100 and I just checked and it still provides 80 MHz of channel width.
For a good measure, please reboot it with the following settings (AFAIK, these are the same as the current ones): channel 100, bandwidth 160 MHz, mode ax, country DE. Then wait 10 minutes. Then provide the whole system log.
There is no smart or intelligent automatic channel selection at this time. This does stick to the lowest channel as long as there are no DFS events. I recommend to manually select a channel that fits the channel usage in your individual environment.
By the way this almost eliminates the usage of 160 MHz channels in dense city environments because you both receive interference from a lot of other 5G networks and generate interference for others at the same time. There is only one 160 MHz channel that does not interfere with weather radar in EU. Does not make sense if all SSIDs in one location try to talk to their stations on only one channel and you guarantee to collect the most interference from other SSIDs.
And yes 802.11ax coloring will help but more in the future where AX SSIDs and AX capable stations will get higher adoption rates.
Therefore, my gut feeling is that the downgrade to 80 MHz is a client-side issue.
Are you sure that the client supports 802.11ax? The not-so-recent change disabled 160 MHz bandwidth for 802.11ac clients, because this would break Apple 802.11ax clients. In any case, as already mentioned, the 160 MHz bandwidth on mt7915e is out-of-spec even for 802.11ax.
I would agree if it would be the same with rc2. I just downgraded to rc2 with keeping the settings, restarted and now my 5GHz WiFi is up and running with 160MHz channel wide again