Multiple people have reported good results with 160 MHz in 5 gigabit band with ax on mt7915. See here:
mt7915 is 4x4 with 80 MHz, 2x2 with 160 MHz and 2x2 with 80 MHz dbdc. 160 MHz dbdc is not supported.
that's correct, but the device (and hence analog parts in the RF path) are meant to be used with 80 MHz channel bandwidth in 4T4R mode. What you got here is btw. MT7915+MT7975PN supposedly. DBDC would be different frontend types, so this is not supported on the RT3200 which uses the built-in 2.4GHz radio of the MT7622 SoC (which is more like MT7615)
Does anyone know why RT3200 5GHz radio power is limited to 23 dBm on U-NII-1 channels (36-48), even though on U-NII-3 channels (149-165) radio power up to 27 dBm is supported with country code set to US? Up to 30 dBm is allowed in the US on U-NII-1 and U-NII-3 channels.
Radio power is limited to 24 dBm on U-NII-2 channels (52-144), as expected with country code set to US.
I think it just uses the wireless-regdb which says 23 except for the comment which I guess is not processed.
# 5.15 ~ 5.25 GHz: 30 dBm for master mode, 23 dBm for clients
(5150 - 5250 @ 80), (23), AUTO-BW
https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/tree/db.txt#n1741
Thank you - I would never have found that. The RT3200 is the first OpenWrt target I've used that with country code set to US could not set transmit power up to 30 dBm on 2.4 GHz channels 1-11 (RT3200 limited to 28 dBm), U-NII-1 channels 36-48 (RT3200 limited to 23 dBm) and U-NII-3 channels 149-165 (RT3200 limited to 27 dBm).
I've experimented with more OpenWrt targets than I care to admit over the years that could set tx power up to 30 dBm: TP-Link Archer C7, Linksys EA6350v3 and EA8500, Askey RT4230W, Dynalink DL-WRX36. I half suspected the RT3200 amplifiers were just not capable of a full watt. Looks like it is the defaults used for the OpenWrt builds instead.
Updated to SNAPSHOT r22235-a03076cc39 last night and noticed the 160MHz width setting has been restored.
I set my 5Ghz to channel 120 @ 160MHz width and WOW does it fly on Belkin RT3200! Speedtest was straight up 200Mbps faster than on 80Mhz, on a Pixel 6 Pro.
iw reg get from the terminal prompt on my DL-WRX36 initially lists the same txpower limits as on my RT3200, but on the DL-WRX36 additional self-managed sections are listed with limits that correspond (correctly) to the US txpower limits. The same command run on my RT3200 is missing the self-managed sections and displays incorrect (too low) US txpower limits for channels 36-48. As noted above 1-11 are limited to 28 dBm, 36-48 to 23 dBm and 149-165 to 27 dBm on the RT3200 versus US limit of 30 dBm in these ranges.
Seems like a bug in the RT3200 limits to me. As I mentioned, the RT3200 is the only target of many I have used that enforces lower txpower limits than allowed in the US.
root@WRX36-2:~# 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)
phy#1 (self-managed)
country US: DFS-FCC
(2402 - 2472 @ 40), (6, 30), (N/A)
(5170 - 5250 @ 80), (6, 30), (N/A), AUTO-BW
(5250 - 5330 @ 80), (6, 24), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (6, 24), (0 ms), DFS, AUTO-BW
(5735 - 5835 @ 80), (6, 30), (N/A), AUTO-BW
phy#0 (self-managed)
country US: DFS-FCC
(2402 - 2472 @ 40), (6, 30), (N/A)
(5170 - 5250 @ 80), (6, 30), (N/A), AUTO-BW
(5250 - 5330 @ 80), (6, 24), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (6, 24), (0 ms), DFS, AUTO-BW
(5735 - 5835 @ 80), (6, 30), (N/A), AUTO-BW
root@WRX36-2:~#
root@RT3200-1:~# 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)
root@RT3200-1:~#
I jumped from 22.03.2 (22.03.3 was not stable for me) to SNAPSHOT (r22241-acb189179c)
5GHz is performing much better (without changing anything).
However I can no longer get into luci.
I do get redirected to 192.168.1.1/cgi-bin/luci/ as expected, but I get the generic unavailable / too busy browser page.
Snapshot doesn't come with Luci. You have to install it manually or get yourself an image here and add Luci:
https://firmware-selector.openwrt.org/?version=SNAPSHOT&target=mediatek%2Fmt7622&id=linksys_e8450-ubi
You can install Luci by running
opkg update
opkg install luci
But beware that with snapshot packages will only be available for a short period of time. So I recommend to install packages right after a snapshot upgrade.
Hi, I was looking at the documentation for beamforming and BSS coloring on https://openwrt.org/toh/linksys/e8450 Is beam forming only applicable to the 5ghz radio1? Also, if I have multiple APs but on different frequencies (e.g., channel 36 and 149) should they have the same BSS code or different ones? I assume since they are on different frequencies then BSS code serves no purpose. Thanks
Hi, I was 1 week away from home and when I returned home, I saw the router being factory reset...asking to setup a password, no additional packages, etc... As I have an wired AP we still had internet at home, but no Wifi from the router. When I started setting it up again after 2 soft restarts, I tryed to upload the latest snapshot, the router did accepted it but didn't flashed it. Then I did unpluged the power for 30 sec. and the router returned to the previose stage- all packages available, network was setup ok. I am running SNAPSHOT r22235-a03076cc39. If it will be in interest of the developers, I can support any debugging.
Regards
K.
Hi all. I obtained this router today and i wanted to ask if i understood the process for " Upgrading to the latest OpenWrt release" correctly (link):
auc
Correct? I read all posts here but it took a few days and some things are a blur now. I would not even ask this question since i can see ubi and non-ubi builds on OpenWrt Firmware selector portal and i observed above one post where it was confirmed you can download *.itb and upgrade from Luci (or curl to /tmp and then sysupgrade i guess) unless i saw this on instructions page:
[...]
Login http://192.168.1.1, then navigate to System -> Backup / Flash Firmware and save a copy of each of themtdblock. Resist the temptation to flash anything from this page! You will likely need serial console access to repair the device.
[...]
I plan on converting to ubi and use stable release. Backup is in place and i have prepared all files in advance 
Correct you can use auc or firmware selector.If you use auc, then you will get automaticaly the correct version UBI or NON UBI.
Regards
K
Before flashing OpenWrt sysupgrade you need to run the installer image, ie. follow the instructions all the way to the end. That's why the warning above is there, because if you flash something before running the actual installer, it will not work.
Of course, i have prepared everything and did exactly what was instructed on Github repo (and after reading most of posts here in this sea of comments). In a nutshell it is quite easy due to good explanation on Github therefore i expected (nearly) zero troubles. One note tho: my router arrived with 1.0.01.101415 firmware. It was obtained from UAE Amazon.
Conversion completed successfully, i had zero troubles. Sysupgrade to 22.03.3, downloaded from firmware selector, completed as well. I guess it is post-release configuration and testing time. Will migrate manually my config from another 2 openwrt routers and will report how it works.
Thank you so far for all the work.
I've run into that problem (sysupgrade not "taking") with the DL-WRX36, but not RT3200. Still, you might try the same fix by adding:
option disabled '1'
to every SSID section in /etc/config/wireless. Then reboot, try sysupgrade again, and change the disabled option from "1" to "0" - might as well leave the text in-line so it's easier to disable again later.
You can do it with LuCI too, but that gets tiresome fast with if you have many SSID's.