Thanks but busybox is identical on both devices. Will hook a serial connection to see if I see anything.
Also, one more question, if someone can assist: if i create 2 AX WiFi network interfaces on RT3200, do i need to specify BSS and beamforming for both? Eg, the following in wireless conf:
option he_su_beamformee '1'
option he_bss_color '8'
Had anyone tried this?
Those options apply to the wireless radio, i.e wifi-device level of the /etc/config/wireless file. You would not place those within each wifi-iface (i.e. SSID).
The he_bss_color option only applies to 5ghz, specifically AX. The purpose of it is to allow multiple 5ghz radios (think multiple APs) to exist on the same channel in your environment. But the BSS color is what an AP will look at to know if a communication is intended for "him" or "the other guy" on the same channel.
In a typical home environment, generally there is not a high enough AP density to where multiple APs must exist on the same channel. But, for best practice, you certainly will be safe setting a unique BSS color value on each 5ghz radio of your APs.
2 Likes
Silly me. Thank you for this explanation, i have corrected my mistake.
just wondering if anybody had any experience with 160mhz AX and 802.11s mesh.
I cant seem to get it to work. all settings seem to apply but my other meshpoint (AX3600) doens't want to connect.
It connects on ch149 on 80mhz even with the settings set to 160mhz but im aware this is a regional issue. This is working wonderfully by the way, getting 750-800Mbit iperf3 speed.
when setting something like ch100 its not connecting. even after waiting half an houre for DFS scan to complete. The logs show no errorlogs or anything.
I have played with different regions, channels, compairing regions and channel restrictings and working within them but no luck so far.
I can live with 750Mbit speeds, just looking to get even more perfomance
It seems 160Mhz neither works with mesh nor actually facilitates improved bandwidth in general vs 80Mhz with this hardware. And WDS seems preferable to mesh unless I'm mistaken. 160Mhz works with WDS but there is no improvement.
2 Likes
Thanks! yeah i figured from reading some of the posts but just wanted to confirm.
ill see if WDS meets my needs and if it can be an improvement over mesh.
Im my experience having tried both WDS and mesh on my 3 e8450 as dumb AP, WDS is much more stable and gives better speed than mesh.
Mine plug along great and have for over a year and a half, one e8450 as WDS master, and the other 2 as WDS clients. I was going to run ethernet cables to the 2 clients and eliminate WDS but performance is good enougb that I havent bothered yet.
2 Likes
Wow, what is up with that? Mine only takes maybe 2 minutes to complete the scan when I bring the radio up... (US on channel 52.)
haha no no, it didnt scan for 30min, i only waited so long just to make sure DFS was not the issue.
1 Like
They are starting to build on the next stable release. The current stable release 22.03.4 produced some issues on devices with the ubi extension suffix, so please take due caution when using the software before an official announcement. I stumbled upon the build whilst looking for firmware on the firmware selector website for my X86 device.
Is it recommended to update RT3200 from 22.03.4 to 22.03.5 or the new release doesn't introduce significant improvements for this router?
22.03.5 fixes the upstream Linux UBI bug (that was introduced in 22.03.4) that may prevent booting depending on the exact size of the firmware and the UBI structure.
Some bugs were fixed too! If it means anything, upgrade completed successfully on my UBI RT3200. It took 3 min to download, checked sha256 sum and upgrade 
22.03.5 is not yet available via AUC right?
Cheers.
@aparcar likely knows about that.
2 Likes
Doesn't look like it.
https://sysupgrade.openwrt.org/
Added - enjoy
6 Likes
Sorry to bother you. What if from Linksys E8450 22.03.4 UBI, I accidentally tried to upgrade to 22.03.5 NON-UBI but failed? I am now stuck with 22.03.1 UBI with seemingly no ways to go to 22.03.3 even. I know I should have upgraded to 22.03.5 UBI, but I didn't pay attention to .bin vs. itb. Thanks.