WRT3200ACM - OpenWrt/LuCI hang after a few minutes running

And what was the last output before it froze?

Ah I halted top... let me try again and get baack to you with the results

1 Like

My original thesis could be wrong. The procedure for troubleshooting was:

  • Connect with cable to lan1
  • turn on router
  • check if devices connect to 5ghz or 2.4ghz
  • yes devices (many small home automation appliances) do connect to 2.4ghz
  • no my laptop and my iphone refuse to connect to 5ghz and to 2.4ghz
  • unplug the cable because magically the laptop connected to the wifi
  • lose the connection because apparently the wifi wasn't really connected
    I simply lose the connection because I unplug the cable and once plugged back nothing happens.

Anyway when LuCI hangs this is the output:

PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
 1983     1 root     D     4072   1%   0% /usr/sbin/hostapd -s -g /var/run/hostapd/global
 1984     1 root     S     3944   1%   0% /usr/sbin/wpa_supplicant -n -s -g /var/run/wpa_supplicant/global
 2218     1 root     S     3688   1%   0% /usr/sbin/uhttpd -f -h /www -r OpenWrt -x /cgi-bin -u /ubus -t 60 -T 30 -k 20 -A 1 -n 3 -N 100 -R -p 0.0.0.0:80 -p [::]:80 -C /etc/uhttpd.crt
 4110  2218 root     S     2480   0%   0% {luci} /usr/bin/lua /www/cgi-bin/luci
 1684     1 root     D     2000   0%   0% /sbin/rpcd -s /var/run/ubus/ubus.sock -t 30
 2044     1 root     S     1600   0%   0% /sbin/netifd
    1     0 root     S     1396   0%   0% /sbin/procd
 2101     1 root     S     1252   0%   0% /usr/sbin/odhcpd
 3177     1 dnsmasq  S     1196   0%   0% /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf.cfg01411c -k -x /var/run/dnsmasq/dnsmasq.cfg01411c.pid
 3596  3555 root     R     1124   0%   0% top -d 1
 3555  3554 root     S     1116   0%   0% -ash
 2660     1 root     S<    1112   0%   0% /usr/sbin/ntpd -n -N -S /usr/sbin/ntpd-hotplug -p 0.openwrt.pool.ntp.org -p 1.openwrt.pool.ntp.org -p 2.openwrt.pool.ntp.org -p 3.openwrt.pool
 3122  2044 root     S     1108   0%   0% udhcpc -p /var/run/udhcpc-wan.pid -s /lib/netifd/dhcp.script -f -t 0 -i wan -x hostname:OpenWrt -V askey_HW_ES1_SW_0.00.67/dslforum.org -C -R
 1088     1 ubus     S     1040   0%   0% /sbin/ubusd
 1632     1 logd     S     1032   0%   0% /sbin/logd -S 64
 3554  1885 root     S      908   0%   0% /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 22 -K 300 -T 3
 1885     1 root     S      868   0%   0% /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 22 -K 300 -T 3
 1123     1 root     S      816   0%   0% /sbin/urngd
 1089     1 root     S      704   0%   0% /sbin/askfirst /usr/libexec/login.sh
   16     2 root     DW       0   0%   0% [kworker/1:0+ipv]
  220     2 root     IW       0   0%   0% [kworker/u4:3-ev]
  419     2 root     IW       0   0%   0% [kworker/0:1-eve]
    9     2 root     SW       0   0%   0% [ksoftirqd/0]
   10     2 root     IW       0   0%   0% [rcu_sched]
  806     2 root     SW       0   0%   0% [f1072004.mdio-m]
  888     2 root     IW       0   0%   0% [kworker/0:2-rcu]
 3663     2 root     DW       0   0%   0% [kworker/u4:0+ds]
   15     2 root     SW       0   0%   0% [ksoftirqd/1]
  992     2 root     SW       0   0%   0% [ubi_bgt1d]
 4078     2 root     IW       0   0%   0% [kworker/1:1-eve]
  874     2 root     SW       0   0%   0% [ubi_bgt0d]
  522     2 root     SW       0   0%   0% [scsi_eh_0]
  512     2 root     IW<      0   0%   0% [iscsi_eh]
  523     2 root     IW<      0   0%   0% [scsi_tmf_0]
  528     2 root     IW<      0   0%   0% [scsi_tmf_1]
  729     2 root     IW<      0   0%   0% [kworker/u5:0-MW]
  730     2 root     IW<      0   0%   0% [sdhci]
  731     2 root     SW       0   0%   0% [irq/43-mmc0]
  764     2 root     SW       0   0%   0% [irq/39-f1090000]
  321     2 root     IW<      0   0%   0% [kthrotld]
  256     2 root     SW       0   0%   0% [watchdogd]
  255     2 root     IW<      0   0%   0% [ata_sff]
  313     2 root     SW       0   0%   0% [kswapd0]
  527     2 root     SW       0   0%   0% [scsi_eh_1]

Are you able to connect back with ssh when you plug the cable in?

Nope it doesn't even ping

Connecting the same device via lan and wifi might trigger some broadcast storm. Leave the laptop connected on only one medium and keep monitoring the cpu utilization. Also leave a logread -f running on another window to check the logs before freezing. Include all the lines from top, like:

CPU:   0% usr   0% sys   0% nic 100% idle   0% io   0% irq   0% sirq
Load average: 0.04 0.05 0.01 3/95 4016

You may want to disable rebind protection if you keep getting pricate IP responses from upstream nameservers.

Regarding the utilization it seems still okayish. Maybe the others have a better idea how to identify the culprit.

Yeah the rebind protection is because of an unclosed tab on firefox that I forgot.

Maybe I should open another topic since we identified better the problem?

Similar topic: [FIXED] 21.02.0-rc2 WRT3200ACM wireless is broken
I tried to use that trick but it didn't work.

Where can I download an older version of the image of openwrt for my router?

https://firmware-selector.openwrt.org/

2 Likes

I tried to downgrade but it was unsuccessful

Don't keep the configuration files while flashing the new image.

Yes that's what I did but still no sucess.

On your 5 ghz wifi try lowering your transmit power to 15-18 dBm instead of using driver default and use 40Mhz band instead of 80Mhz.

Edit: And restart the radio after applying the new values.

Edit2: If it does not work try to use auto channel instead of manually channel 36. I had some issues on the newest firmware with radio compatibility where it only works on some channels ie. 36 and 149 but fails on all other channels on specific drivers.

Thank you @csensitive but unfortunately your settings did not work: I cannot even see the network now.

I just noticed that everything works smoothly until I add encryption to the network. Any clue on this?

It's WPA3 that breaks everything. I Sticked to wpa2 and things seem to work.

1 Like

mwlwifi not supporting (crashing hard) WPA3/ IEEE802.11w is a known bug in that driver/ firmware, which is unlikely to be fixable.