WiFi is crashing during large file transfer through Ethernet or Wi-Fi and refusing connection until router is rebooted

_openwrtuser · February 13, 2025, 1:00am

Wi-Fi keeps crashing while transferring or downloading large files, e.g. 1-6 GB. The router is refusing Wi-Fi connection until it is rebooted. Not only that, I was testing using fast.com for 5 minutes through Ethernet and discovered Wi-Fi is crashed! I experience similar issue about a year ago, but it was later solved. Furthermore, I am not sure whether this issue is the same or not! Any help is appreciated. Thank you for the time.

Logs:
System:

Thu Feb 13 06:37:45 2025 kern.err kernel: [ 2896.523406] mt76x2e 0000:01:00.0: MCU message 1f (seq 10) timed out
Thu Feb 13 06:37:45 2025 kern.info kernel: [ 2896.722688] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
Thu Feb 13 06:37:45 2025 kern.info kernel: [ 2896.733677] mt76x2e 0000:01:00.0: Build: 1
Thu Feb 13 06:37:45 2025 kern.info kernel: [ 2896.741793] mt76x2e 0000:01:00.0: Build Time: 201607111443____
Thu Feb 13 06:37:45 2025 kern.info kernel: [ 2896.773470] mt76x2e 0000:01:00.0: Firmware running!
Thu Feb 13 06:37:45 2025 kern.info kernel: [ 2896.786785] ieee80211 phy1: Hardware restart was requested
Thu Feb 13 06:37:46 2025 kern.err kernel: [ 2897.803405] mt76x2e 0000:01:00.0: MCU message 02 (seq 13) timed out
Thu Feb 13 06:37:47 2025 kern.err kernel: [ 2898.603371] mt76x2e 0000:01:00.0: MCU message 1f (seq 14) timed out
Thu Feb 13 06:37:47 2025 kern.info kernel: [ 2898.774712] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
Thu Feb 13 06:37:47 2025 kern.info kernel: [ 2898.785677] mt76x2e 0000:01:00.0: Build: 1
Thu Feb 13 06:37:47 2025 kern.info kernel: [ 2898.793859] mt76x2e 0000:01:00.0: Build Time: 201607111443____
Thu Feb 13 06:37:47 2025 kern.info kernel: [ 2898.823402] mt76x2e 0000:01:00.0: Firmware running!
Thu Feb 13 06:37:47 2025 kern.info kernel: [ 2898.834506] ieee80211 phy1: Hardware restart was requested
Thu Feb 13 06:37:49 2025 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED [REDACTED]

Kernel:

[ 2896.523406] mt76x2e 0000:01:00.0: MCU message 1f (seq 10) timed out
[ 2896.722688] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
[ 2896.733677] mt76x2e 0000:01:00.0: Build: 1
[ 2896.741793] mt76x2e 0000:01:00.0: Build Time: 201607111443____
[ 2896.773470] mt76x2e 0000:01:00.0: Firmware running!
[ 2896.786785] ieee80211 phy1: Hardware restart was requested
[ 2897.803405] mt76x2e 0000:01:00.0: MCU message 02 (seq 13) timed out
[ 2898.603371] mt76x2e 0000:01:00.0: MCU message 1f (seq 14) timed out
[ 2898.774712] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
[ 2898.785677] mt76x2e 0000:01:00.0: Build: 1
[ 2898.793859] mt76x2e 0000:01:00.0: Build Time: 201607111443____
[ 2898.823402] mt76x2e 0000:01:00.0: Firmware running!
[ 2898.834506] ieee80211 phy1: Hardware restart was requested

Specifications:

Hostname	OpenWrt
Model	Netgear R6120
Architecture	MediaTek MT7628AN ver:1 eco:2
Target Platform	ramips/mt76x8
Firmware Version	OpenWrt 24.10.0 r28427-6df0e3d02a / LuCI openwrt-24.10 branch 25.037.68331~42f464c
Kernel Version	6.6.73

brada4 · February 13, 2025, 1:14am

Does it warm up under 5min long fast.com speed test?

_openwrtuser · February 13, 2025, 1:20am

No, not that noticeable but discovered that Wi-Fi is crashing even when I was testing using Ethernet!

psherman · February 13, 2025, 2:41am

I'm suspecting that you might have a failing power adapter (or power subsystem within the router itself).

Do you have a spare power adapter that supplies 12VDC @ 1.5A (or a higher current capacity is fine, too)?

But just to rule out any config issues, let's take a look at that:

Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:

Remember to redact passwords, MAC addresses and any public IP addresses you may have:

ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall

_openwrtuser · February 13, 2025, 3:22am

Thank you for the reply.

I need some time to collect one and test. The outputs of the commands are followed by,

ubus call system board

{
	"kernel": "6.6.73",
	"hostname": "OpenWrt",
	"system": "MediaTek MT7628AN ver:1 eco:2",
	"model": "Netgear R6120",
	"board_name": "netgear,r6120",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "24.10.0",
		"revision": "r28427-6df0e3d02a",
		"target": "ramips/mt76x8",
		"description": "OpenWrt 24.10.0 r28427-6df0e3d02a",
		"builddate": "1738624177"
	}
}

cat /etc/config/network

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fd56:16cb:1497::/48'
	option packet_steering '1'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'eth0.1'

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ipaddr '192.168.1.1'
	option netmask '255.255.255.0'
	option ip6assign '60'

config device
	option name 'eth0.2'
	option macaddr [REDACTED]

config interface 'wan'
	option device 'eth0.2'
	option proto 'pppoe'
	option username [REDACTED]
	option password [REDACTED]
	option ipv6 'auto'

config switch
	option name 'switch0'
	option reset '1'
	option enable_vlan '1'

config switch_vlan
	option device 'switch0'
	option vlan '1'
	option ports '0 1 2 3 6t'

config switch_vlan
	option device 'switch0'
	option vlan '2'
        option ports '4 6t'

cat /etc/config/network

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fd56:16cb:1497::/48'
	option packet_steering '1'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'eth0.1'

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ipaddr '192.168.1.1'
	option netmask '255.255.255.0'
	option ip6assign '60'

config device

cat /etc/config/wireless

config wifi-device 'radio0'
	option type 'mac80211'
	option path 'platform/10300000.wmac'
	option band '2g'
	option channel 'auto'
	option htmode 'HT20'
	option disabled '1'
	option country [REDACTED]
	option cell_density '0'

config wifi-iface 'default_radio0'
	option device 'radio0'
	option network 'lan'
	option mode 'ap'
	option ssid [REDACTED]
	option encryption [REDACTED]
	option key [REDACTED]
	option wpa_disable_eapol_key_retries '1'

config wifi-device 'radio1'
	option type 'mac80211'
	option path 'pci0000:00/0000:00:00.0/0000:01:00.0'
	option band '5g'
	option channel 'auto'
	option htmode 'VHT80'
	option country [REDACTED]
	option cell_density '0'

config wifi-iface 'default_radio1'
	option device 'radio1'
	option network 'lan'
	option mode 'ap'
	option ssid [REDACTED]
	option encryption [REDACTED]
	option key [REDACTED]
	option wpa_disable_eapol_key_retries '1'

cat /etc/config/dhcp

config dnsmasq
	option domainneeded '1'
	option boguspriv '1'
	option filterwin2k '0'
	option localise_queries '1'
	option rebind_protection '1'
	option rebind_localhost '1'
	option local '/lan/'
	option domain 'lan'
	option expandhosts '1'
	option nonegcache '0'
	option cachesize '1000'
	option authoritative '1'
	option readethers '1'
	option leasefile '/tmp/dhcp.leases'
	option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
	option nonwildcard '1'
	option localservice '1'
	option ednspacket_max '1232'
	option filter_aaaa '0'
	option filter_a '0'

config dhcp 'lan'
	option interface 'lan'
	option start '100'
	option limit '150'
	option leasetime '12h'
	option dhcpv4 'server'
	option dhcpv6 'server'
	option ra 'server'
	option ra_slaac '1'
	list ra_flags 'managed-config'
	list ra_flags 'other-config'

config dhcp 'wan'
	option interface 'wan'
	option ignore '1'

config odhcpd 'odhcpd'
	option maindhcp '0'
	option leasefile '/tmp/hosts/odhcpd'
	option leasetrigger '/usr/sbin/odhcpd-update'
        option loglevel '4'

cat /etc/config/firewall

config defaults
	option syn_flood '1'
	option input 'REJECT'
	option output 'ACCEPT'
	option forward 'REJECT'

config zone
	option name 'lan'
	option input 'ACCEPT'
	option output 'ACCEPT'
	option forward 'ACCEPT'
	list network 'lan'

config zone
	option name 'wan'
	option input 'REJECT'
	option output 'ACCEPT'
	option forward 'REJECT'
	option masq '1'
	option mtu_fix '1'
	list network 'wan'

config forwarding
	option src 'lan'
	option dest 'wan'

config rule
	option name 'Allow-DHCP-Renew'
	option src 'wan'
	option proto 'udp'
	option dest_port '68'
	option target 'ACCEPT'
	option family 'ipv4'

config rule
	option name 'Allow-Ping'
	option src 'wan'
	option proto 'icmp'
	option icmp_type 'echo-request'
	option family 'ipv4'
	option target 'ACCEPT'

config rule
	option name 'Allow-IGMP'
	option src 'wan'
	option proto 'igmp'
	option family 'ipv4'
	option target 'ACCEPT'

config rule
	option name 'Allow-DHCPv6'
	option src 'wan'
	option proto 'udp'
	option dest_port '546'
	option family 'ipv6'
	option target 'ACCEPT'

config rule
	option name 'Allow-MLD'
	option src 'wan'
	option proto 'icmp'
	option src_ip 'fe80::/10'
	list icmp_type '130/0'
	list icmp_type '131/0'
	list icmp_type '132/0'
	list icmp_type '143/0'
	option family 'ipv6'
	option target 'ACCEPT'

config rule
	option name 'Allow-ICMPv6-Input'
	option src 'wan'
	option proto 'icmp'
	list icmp_type 'echo-request'
	list icmp_type 'echo-reply'
	list icmp_type 'destination-unreachable'
	list icmp_type 'packet-too-big'
	list icmp_type 'time-exceeded'
	list icmp_type 'bad-header'
	list icmp_type 'unknown-header-type'
	list icmp_type 'router-solicitation'
	list icmp_type 'neighbour-solicitation'
	list icmp_type 'router-advertisement'
	list icmp_type 'neighbour-advertisement'
	option limit '1000/sec'
	option family 'ipv6'
	option target 'ACCEPT'

config rule
	option name 'Allow-ICMPv6-Forward'
	option src 'wan'
	option dest '*'
	option proto 'icmp'
	list icmp_type 'echo-request'
	list icmp_type 'echo-reply'
	list icmp_type 'destination-unreachable'
	list icmp_type 'packet-too-big'
	list icmp_type 'time-exceeded'
	list icmp_type 'bad-header'
	list icmp_type 'unknown-header-type'
	option limit '1000/sec'
	option family 'ipv6'
	option target 'ACCEPT'

config rule
	option name 'Allow-IPSec-ESP'
	option src 'wan'
	option dest 'lan'
	option proto 'esp'
	option target 'ACCEPT'

config rule
	option name 'Allow-ISAKMP'
	option src 'wan'
	option dest 'lan'
	option dest_port '500'
	option proto 'udp'
	option target 'ACCEPT'

Hope I didn't leak any data that should have been redacted.

psherman · February 13, 2025, 3:43am

You're all good.

I don't see any issues with the configuration. I'd recommend trying a replacement power adapter.

_openwrtuser · February 13, 2025, 8:28pm

Thank you for the review. I tested the power using an alternative power port in my power supply as well as another adapter rated at 12VDC-1.5A. However, I am still getting the following,
System log:

Fri Feb 14 06:49:44 2025 kern.err kernel: [  444.891853] mt76x2e 0000:01:00.0: MCU message 1f (seq 5) timed out
Fri Feb 14 06:49:45 2025 kern.info kernel: [  445.750890] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
Fri Feb 14 06:49:45 2025 kern.info kernel: [  445.763703] mt76x2e 0000:01:00.0: Build: 1
Fri Feb 14 06:49:45 2025 kern.info kernel: [  445.773106] mt76x2e 0000:01:00.0: Build Time: 201607111443____
Fri Feb 14 06:49:45 2025 kern.info kernel: [  445.859872] mt76x2e 0000:01:00.0: Firmware running!
Fri Feb 14 06:49:46 2025 kern.info kernel: [  446.845223] ieee80211 phy1: Hardware restart was requested
Fri Feb 14 06:49:57 2025 user.notice firewall: Reloading firewall due to ifupdate of wan_6 (pppoe-wan)

Kernel log:

[  444.891853] mt76x2e 0000:01:00.0: MCU message 1f (seq 5) timed out
[  445.750890] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
[  445.763703] mt76x2e 0000:01:00.0: Build: 1
[  445.773106] mt76x2e 0000:01:00.0: Build Time: 201607111443____
[  445.859872] mt76x2e 0000:01:00.0: Firmware running!
[  446.845223] ieee80211 phy1: Hardware restart was requested

Could you please tell me which entry in the log indicated a power issue? I guess I will have to look for another device or make a router using Raspberry Pi.

psherman · February 14, 2025, 6:50am

There wasn't a specific entry, but rather the symptoms described. The hardware restart in the logs could also support the power theory, but it sounds like it was not the culprit after all.

IMEVER · February 14, 2025, 8:51am

The same question.
My device: Phicomm k2g

_openwrtuser · February 14, 2025, 8:24pm

You did mention,

Do you think that is the case and it's time for a replacement? Could it be a bug?

psherman · February 14, 2025, 8:27pm

Either are possible. If you're comfortable opening your router, you can look at the capacitors which are a common failure point in the power system... often if they've gone bad, you'll see bulging and/or leaking electrolyte.

To rule in/out a bug, you could try 23.05.5 and see if the same config and tests produce the same result.

_openwrtuser · February 14, 2025, 8:27pm

Did you experience it in the earlier version? I had this issue on 23.05.5 too!

psherman · February 14, 2025, 8:35pm

I don't have your device, so my experiences aren't relevant... but on the devices that I have, no, I haven't had these issues on any version.

_openwrtuser · February 14, 2025, 8:49pm

I will open it and take a look. If the capacitor went bad, then I might be able to replace it. Thanks for the hint.

It was same with 23.05.5, but it had no problem while using 23.05.3 as far as I can remember. I will give it a try too.

_openwrtuser · February 14, 2025, 8:51pm

Sorry, the reply was for IMEVER

Marcelo.Barros · February 14, 2025, 9:07pm

Hi, @_openwrtuser

Please..
Can you try to disable, must be off at luci, both wifi and to the same tests using only rj45?

This test... will give a light about

Is the wireless the guilt?
Power supply?

_openwrtuser · February 14, 2025, 9:49pm

Yes, I disabled 2.4 GHz and 5 GHz and did the following,

Ran test using https://fast.com for 300 seconds
Transferred 4.26 GB using Local Send from Laptop to Desktop

It did not trigger reset or create any issue during and after those tests.

Marcelo.Barros · February 14, 2025, 9:52pm

nice..

Now... let test with one wifi enable only? 5GHz?

I can be wrong... but just one radio enable, maybe not affect too deep the power needs.

IF with only one radio enable (5GHz) pass your test... The wifi driver it is not a issue.

But...
Can be the power supply or hardware temperature of the device!

_openwrtuser · February 14, 2025, 10:01pm

Yes, the issue triggers even with just 5 GHz enabled (I don't use 2.4 GHz anyway). I tried changing the adapter but did not help.

Is there any package can report the temperature?

Marcelo.Barros · February 14, 2025, 10:10pm

Maybe there is an software at library... But the hardware of your device must need to have a temperature sensor. (cpu or ???)

Looking some pictures...

And... we need a confirmation from a openwrt developer...
Everything (network, Software, wifi, etc.. ) is handle by the cpu of the device and not have any kind of "water mark" to protect the cpu when goes to 100% usage and it is become hot! like CPU Throttling limits CPU consumption by lowering the clock rate.

crazy idea?
Can you put the device at side of a fan... so the wind go from right to left, passing inside of the device?

This will check for temperature... I knows... crazy...
but will help to reduce the temperature of the cpu.

updating... leave the fan at the back of your device.