Belkin RT3200/Linksys E8450 WiFi AX discussion

Latrina · June 30, 2021, 8:53am

I have been using OpenWrt snapshot on this Belink RT3200 for about 3 months now and it has been an absolute dog. Clients connected via wireless suddenly get disconnected and re-connecting to it is impossible until router is restarted. Restarting the network service from cli doesn't restore wireless. This wireless issue happens at least twice a week.

I have been upgrading the snapshot version via auc on a weekly basis and had this issue since the beginning really. Any suggestions will be much appreciated.

alleyu2 · June 30, 2021, 9:45am

I have applied the this "11a HE80 (add htmode HE80 to /etc/config/wireless - 1200 Mbit link speed)" to my configuration as mentiond in the op. I am not facing any disconnection issues on my 5G band.

alleyu2 · June 30, 2021, 9:48am

Experiencing high bufferbloat (+147ms) on wifi with SQM enabled. However, zero bufferbloat on LAN with SQM enabled. Is this normal?

Latrina · June 30, 2021, 9:57am

Okay I am going to try it. I had option htmode 'VHT80'.

Fiouz · June 30, 2021, 2:58pm

LuCI support for 802.11ax should be working fine since luci^4286c84825c15f4d36f294b2ea28071667a4be7e.

deathisinevitable · June 30, 2021, 11:17pm

guys, I have the another trouble:


root@OpenWrt:~# opkg install luci
Installing luci (git-20.074.84698-ead5e81) to root...
Downloading https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/luci/luci_git-20.074.84698-ead5e81_all.ipk
Collected errors:
 * pkg_hash_check_unresolved: cannot find dependency libubus20210603 for uhttpd-mod-ubus
 * pkg_hash_fetch_best_installation_candidate: Packages for uhttpd-mod-ubus found, but incompatible with the architectures configured
 * pkg_hash_check_unresolved: cannot find dependency libubus20210603 for rpcd
 * pkg_hash_fetch_best_installation_candidate: Packages for rpcd found, but incompatible with the architectures configured
 * pkg_hash_check_unresolved: cannot find dependency libubus20210603 for rpcd-mod-file
 * pkg_hash_fetch_best_installation_candidate: Packages for rpcd-mod-file found, but incompatible with the architectures configured
 * pkg_hash_check_unresolved: cannot find dependency libubus20210603 for rpcd-mod-luci
 * pkg_hash_fetch_best_installation_candidate: Packages for rpcd-mod-luci found, but incompatible with the architectures configured
 * pkg_hash_check_unresolved: cannot find dependency libubus20210603 for cgi-io
 * pkg_hash_fetch_best_installation_candidate: Packages for cgi-io found, but incompatible with the architectures configured
 * pkg_hash_check_unresolved: cannot find dependency libubus20210603 for rpcd-mod-iwinfo
 * pkg_hash_fetch_best_installation_candidate: Packages for rpcd-mod-iwinfo found, but incompatible with the architectures configured
 * pkg_hash_check_unresolved: cannot find dependency libubus20210603 for rpcd-mod-rrdns
 * pkg_hash_fetch_best_installation_candidate: Packages for rpcd-mod-rrdns found, but incompatible with the architectures configured
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for luci:
 *      libubus20210603
 * opkg_install_cmd: Cannot install package luci.

What can I do with it?

hnyman · July 1, 2021, 6:11am

Wait until buildbot has built the updated packages. Ubus was updated yesterday, and the Luci package did not yet know about the new version when you tried installing it. (Ubus is built along kernel and images by phase1 buildbot, while LuCI is built later by the phase2 packages buildbot)

(Not related to e8450 specifically)

ex-git · July 4, 2021, 3:52am

Using the latest trunk version. Ping modem from router will have ping spike after the router up for couple hours. Not using SQM. Disabled both WiFi won't help. Ping will go from 2ms to about 150ms every couple seconds. Reboot will fix it for couple hours. Anyone has that issue?

Dopam-IT_1987 · July 4, 2021, 11:50am

i have really zero problem with the router, you use the ubi version or version sysupgrade classic

i' am on 5.10.46 actually and all work perfectly

alleyu2 · July 4, 2021, 4:13pm

I am using the non-ubi version and no problems with Wifi. I have noticed that I don't get A+ rating on wifi with SQM and cake on dslr site. I get A+ rating on LAN.

ex-git · July 5, 2021, 2:52am

I use ubi version. 5.10.46 trunk. Ping spike is like below. The address is the modem. Shouldn't have over 3ms ping.

PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: seq=0 ttl=64 time=1.875 ms
64 bytes from 192.168.1.1: seq=1 ttl=64 time=1.371 ms
64 bytes from 192.168.1.1: seq=2 ttl=64 time=1.576 ms
64 bytes from 192.168.1.1: seq=3 ttl=64 time=2.141 ms
64 bytes from 192.168.1.1: seq=4 ttl=64 time=1.939 ms
64 bytes from 192.168.1.1: seq=5 ttl=64 time=2.411 ms
64 bytes from 192.168.1.1: seq=6 ttl=64 time=231.462 ms
64 bytes from 192.168.1.1: seq=7 ttl=64 time=142.249 ms
64 bytes from 192.168.1.1: seq=8 ttl=64 time=2.103 ms
64 bytes from 192.168.1.1: seq=9 ttl=64 time=1.242 ms
64 bytes from 192.168.1.1: seq=10 ttl=64 time=1.539 ms

alleyu2 · July 5, 2021, 3:37am

Yes you are right I am getting the same when pinging the gateway on wifi. That's why I am getting bad rating on SQM. Log is attached below. No issues on lan. Openwrt snapshot "r17073". Any developer can help?

Reply from 192.168.31.1: bytes=32 time=1ms TTL=64
Reply from 192.168.31.1: bytes=32 time=1ms TTL=64
Reply from 192.168.31.1: bytes=32 time=1ms TTL=64
Reply from 192.168.31.1: bytes=32 time=1ms TTL=64
Reply from 192.168.31.1: bytes=32 time=1ms TTL=64
Reply from 192.168.31.1: bytes=32 time=3ms TTL=64
Reply from 192.168.31.1: bytes=32 time=1ms TTL=64
Reply from 192.168.31.1: bytes=32 time=27ms TTL=64
Reply from 192.168.31.1: bytes=32 time=137ms TTL=64
Reply from 192.168.31.1: bytes=32 time=6ms TTL=64
Reply from 192.168.31.1: bytes=32 time=5ms TTL=64
Reply from 192.168.31.1: bytes=32 time=606ms TTL=64
Reply from 192.168.31.1: bytes=32 time=32ms TTL=64
Reply from 192.168.31.1: bytes=32 time=268ms TTL=64
Reply from 192.168.31.1: bytes=32 time=12ms TTL=64
Reply from 192.168.31.1: bytes=32 time=107ms TTL=64
Reply from 192.168.31.1: bytes=32 time=65ms TTL=64
Reply from 192.168.31.1: bytes=32 time=136ms TTL=64
Reply from 192.168.31.1: bytes=32 time=6ms TTL=64
Reply from 192.168.31.1: bytes=32 time=1ms TTL=64
Reply from 192.168.31.1: bytes=32 time=62ms TTL=64
Reply from 192.168.31.1: bytes=32 time=607ms TTL=64
Reply from 192.168.31.1: bytes=32 time=599ms TTL=64
Reply from 192.168.31.1: bytes=32 time=519ms TTL=64
Reply from 192.168.31.1: bytes=32 time=38ms TTL=64
Reply from 192.168.31.1: bytes=32 time=190ms TTL=64
Reply from 192.168.31.1: bytes=32 time=7ms TTL=64
Reply from 192.168.31.1: bytes=32 time=145ms TTL=64
Reply from 192.168.31.1: bytes=32 time=30ms TTL=64

Pings from google on Wifi

Reply from 142.250.77.46: bytes=32 time=63ms TTL=119
Reply from 142.250.77.46: bytes=32 time=413ms TTL=119
Reply from 142.250.77.46: bytes=32 time=71ms TTL=119
Reply from 142.250.77.46: bytes=32 time=1506ms TTL=119
Reply from 142.250.77.46: bytes=32 time=507ms TTL=119
Reply from 142.250.77.46: bytes=32 time=2036ms TTL=119
Reply from 142.250.77.46: bytes=32 time=321ms TTL=119
Reply from 142.250.77.46: bytes=32 time=308ms TTL=119
Reply from 142.250.77.46: bytes=32 time=361ms TTL=119
Request timed out.
Reply from 142.250.77.46: bytes=32 time=1359ms TTL=119
Reply from 142.250.77.46: bytes=32 time=196ms TTL=119
Reply from 142.250.77.46: bytes=32 time=499ms TTL=119
Reply from 142.250.77.46: bytes=32 time=294ms TTL=119
Reply from 142.250.77.46: bytes=32 time=824ms TTL=119
Reply from 142.250.77.46: bytes=32 time=127ms TTL=119
Reply from 142.250.77.46: bytes=32 time=279ms TTL=119
Reply from 142.250.77.46: bytes=32 time=1877ms TTL=119
Reply from 142.250.77.46: bytes=32 time=130ms TTL=119
Reply from 142.250.77.46: bytes=32 time=395ms TTL=119
Reply from 142.250.77.46: bytes=32 time=3ms TTL=119
Reply from 142.250.77.46: bytes=32 time=321ms TTL=119
Reply from 142.250.77.46: bytes=32 time=18ms TTL=119
Reply from 142.250.77.46: bytes=32 time=10ms TTL=119
Reply from 142.250.77.46: bytes=32 time=82ms TTL=119
Reply from 142.250.77.46: bytes=32 time=161ms TTL=119
Reply from 142.250.77.46: bytes=32 time=94ms TTL=119
Reply from 142.250.77.46: bytes=32 time=252ms TTL=119
Reply from 142.250.77.46: bytes=32 time=121ms TTL=119

ex-git · July 5, 2021, 4:26am

I am sending ping from router to modem got that ping spike. So shouldn't related to WiFI IMO. Fresh boot/reboot won't have that issue. Only happen when router has been running for couple hours.
Developer help is needed.

alleyu2 · July 5, 2021, 6:07am

I have changed the wifi 5ghz channel from "173" to "auto" and now the pings on wifi have reduced to 3-5 ms. I also changed the Country Code from "India" to "driver default". Hope this is useful to others.

nazarewk · July 7, 2021, 3:01am

So i had a really weird issue, my belkin rt3200:

reset itself to stock openwrt at night
it did not see the 5Ghz interface
powering off briefly did nothing
powering off for a few minutes got it back to previously configured state with both 5 GHz and 2.4GHz wifi configured and working
i had read-only filesystem after that (couldn't update packages)

After i've tried reflashing openwrt-mediatek-mt7622-linksys_e8450-ubi-squashfs-sysupgrade.itb (i used installer then this file to set it up 2 days ago) i'm stuck on 2 solid orange/amber LEDs and cannot snap the router out of it, i've tried:

powering off for 10 minutes
holding reset button on powered device
holding reset button while powering on the device

It looks like it responds to ping 192.168.1.1 but otherwise i can't do anything with it.
Do you have any idea how to recover from it?

Update: I read anything could be fixed through JTAG? What kind of hardware and linux software do i need to work with it? Note: i've RPi 512 MB and RPi4

alleyu2 · July 7, 2021, 5:38am

Have you tried this?

Post OpenWRT "recovery mode" process

Hold down the "reset" button below the "WPS" button whilst powering on the device.

Release the button once the power LED turns a orange/yellow color.

This will remove any user configuration errors and allow restoring or upgrading from ssh/http/tftp.

Source: https://github.com/dangowrt/linksys-e8450-openwrt-installer

nazarewk · July 7, 2021, 6:25am

Yes i tried the reset button while powering on, nothing happened (still both leds solid orange and not exposing any service - ssh/http)

Actually I did follow loading recovery from TFTP and it worked.

alleyu2 · July 7, 2021, 6:42am

Glad it did.

nazarewk · July 7, 2021, 8:07am

Is it normal that you cannot run opkg upgrade ... due to read-only filesystem?

alleyu2 · July 7, 2021, 8:38am

I read this somewhere so maybe someone can confirm.

As far as I can tell the correct answer to this question is that there is no equivalent for apt upgrade on OpenWrt and no set of commands that will create equivalent functionality. OpenWrt repos aren't maintained with the intention of keeping end user's packages updated (you're expected to move from release to release by flashing) and opkg does not handle or even check dependencies.