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.
21 posts were split to a new topic: Mt76 wireless driver debugging
A post was split to a new topic: Issue starting Adblock on Snapshot
5 posts were split to a new topic: Questions about Linksys E8450 and ASU as well as Beamforming
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):
aucCorrect? 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.
Thanks, however I fixed the issue by just unpluging the power cord for 30 secs. The real issue is why the router went in "fake" factory reset. In this state the router didn't accepted sys upgrades.
PS: or maybe it was a recovery, however luci didn't reported that it was entered recovery.
I think there's something on this in one of the preceding million posts on this thread, but...
If the router has a kernel crash, it writes some crash log files to ram disk in /sys/fs/pstore/. Upon reboot, if those files exist, then the bootloader goes into recovery mode. But, if you delete the files explicitly, or wipe the ram disk by powering off the device for say 30 seconds, then the router will come back up in "normal" mode and boot from the last image you installed.
I have completed everything and it works okay so far. I have enabled ondemand and bss coloring however i havent enabled wed (will wait for this to be enabled upstream, i can wait).
My setup is quite simple:
a2:xy:xy:xy:xy range, same for WiFi) I have added luci-app-stat for stats but i will remove it. Luci is disabled, i do stuff via ssh for monitoring etc however i start uthhpd to test Luci if i have to change something.Since i do most of my chores via Luci, i have noticed something: if Luci is started via ssh and and i select to restart AX WiFi of do wifi [down|up] then i cannot connect to Luci anymore and i got the following in logread:
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.727135] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.735034] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.742579] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.750958] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.758851] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.767152] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.774781] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.782319] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.790652] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:43 2023 kern.warn kernel: [ 1237.603593] print_req_error: 31338 callbacks suppressed
Sun Mar 19 12:26:43 2023 kern.err kernel: [ 1237.603604] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:43 2023 kern.err kernel: [ 1237.620659] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.631422] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.642969] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.653751] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.665241] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.676027] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.687426] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.698184] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.709652] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.warn kernel: [ 1237.723539] buffer_io_error: 31338 callbacks suppressed
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.723999] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.737136] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.745529] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.753138] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.761547] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.769200] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.777081] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.785098] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.792670] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.800740] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:48 2023 kern.warn kernel: [ 1242.613526] print_req_error: 31136 callbacks suppressed
Sun Mar 19 12:26:48 2023 kern.err kernel: [ 1242.613537] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:48 2023 kern.err kernel: [ 1242.630399] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.641583] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.653100] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.663962] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.675446] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.686291] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.698007] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.708868] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.720485] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.warn kernel: [ 1242.733526] buffer_io_error: 31130 callbacks suppressed
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.733532] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.746805] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.754531] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.762153] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.770570] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.778473] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.786845] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.794474] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.802012] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.810447] Buffer I/O error on dev mtdblock2, logical block 32, async page read
I rarely see issues on my other routers because i mostly use default openwrt with default settings and some adjustments of existing stuff so you can say i am quite a boring user . If i can try something, please let me know so you can gather more data but be aware that this RT3200 is my main router from today and all tests can be executed after working hours.
I have discovered another weirdness, unsure what is happening but WiFi reconnects all clients if you open channel analysis. Problem and how to reproduce it:
Log shows very little:
Mon Mar 20 09:57:04 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: authenticated
Mon Mar 20 09:57:05 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 6)
Mon Mar 20 09:57:05 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 6)
Mon Mar 20 09:57:07 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy WPA: pairwise key handshake completed (RSN)
Mon Mar 20 09:57:07 2023 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED xy:xy:xy:xy:xy:xy
Mon Mar 20 09:57:10 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 1)
Mon Mar 20 09:57:10 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 1)
Mon Mar 20 09:57:11 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy WPA: pairwise key handshake completed (RSN)
Mon Mar 20 09:57:11 2023 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED xy:xy:xy:xy:xy:xy
Mon Mar 20 09:57:12 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: authenticated
Mon Mar 20 09:57:18 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: authenticated
Mon Mar 20 09:57:19 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 6)
Mon Mar 20 09:57:19 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 6)
Mon Mar 20 09:57:20 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 1)
Mon Mar 20 09:57:20 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 1)
Mon Mar 20 09:57:20 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: authenticated
Mon Mar 20 09:57:20 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 5)
Mon Mar 20 09:57:20 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy WPA: pairwise key handshake completed (RSN)
Mon Mar 20 09:57:20 2023 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED xy:xy:xy:xy:xy:xy
Mon Mar 20 09:57:21 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy WPA: pairwise key handshake completed (RSN)
Mon Mar 20 09:57:21 2023 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED xy:xy:xy:xy:xy:xy
Mon Mar 20 09:57:21 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy WPA: pairwise key handshake completed (RSN)
Mon Mar 20 09:57:21 2023 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED xy:xy:xy:xy:xy:xy
Mon Mar 20 09:57:21 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: authenticated
dmesg shows no changes. If you stay in Luci, connections drop from time to time. While this is not a problem for regular "consumer" devices, it is for working @ home. I dont think i would even notice this if i was not working from home today. Maybe some AX weirdness, cannot tell really. I rarely open this section in Lucu so it is not big a deal.
This is the expected behavior: If you open the Channel Analysis tab the 5 GHz radio has to hop over and scan all channels. As the clients expect the AP to constantly send beacons on the same channel, this is forcefully lead to disconnect all clients -- unless there is an additional antenna and receiving radio intended only for scanning, which is not present on the RT3200. But you can find this in professional access points such as the UniFi 6 LR which is otherwise very similar to the RT3200. I'm not even sure if we support congruent scanning in software even in case of a scanning-radio/antenna being present.