Hello, everyone! I am using a Cudy WR3000P (WR3000P_EU V1.0) with the official OpenWRT 24.10.5 firmware.
Once in a while, the router may suddenly restart. At one point, I connected a UART adapter to the router and started collecting logs. I got something like this: Full log here (pastebin.com)
This problem is either with the router's hardware or its driver? Unfortunately, I don't know how to reproduce this error again, and I was only able to get the current one after 15 days uptime, so I would like to know what you think about this.
Sounds reasonable.... Lets see if something dangerous is lurking around....
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 (red circle; this works best in the 'Markdown' composer view in the blue oval):
Remember to redact passwords, VPN keys, MAC addresses and any public IP addresses you may have:
Currently I tried to change my AC-DC adapter from Cudy's original to original adapter of Keenetic KN-1012 (mid-range routers in Russia; they doesn't skimp on the little things)
At the moment, I have almost 12 days of uptime, so most likely it was a power shortage (or a poor-quality original AC adapter) that caused the driver to crash. For now, I will mark this as a solution, and if it happens again in the future, I will come back to it.
It's sad to realize that it happened again. I haven't figured it out yet, because it's 5:21 AM and I want to sleep, but I'll leave the log below.
But the router didn't reboot immediately. At first, the newly connected Wi-Fi devices simply didn't work, and then, after attempts to set up a cable connection (after changing the operating frequency), it finally crashed.
Just for context:
[1221972.519998] Computer turned off; put into WoL standby mode
Here I realized that Wi-Fi was not working on my phone and laptop (other devices like IoT what has been connected before driver crash still has access to the internet)
[1222250.943755] Computer turned on
[1222286.825028] Operating system loaded on computer
After that I tried to restart wireless network / change the operating frequency and after this the driver crashed finally.
The problem recurs when you put a load on the WAN (at least on the Internet). When you run iperf within the local network (br-lan), everything works fine.
Over the weekend, I'll try to rework the network and place one of the iperf behind the WAN (I have a MikroTik there, so everything will be within the local network) to check this.
No. It's just that at the time of purchase, this router was available for purchase and I didn't see any better deals. PoE is just an optional feature that I don't use. Currently, the router is powered by a Keenetic AC adapter with 12V 2.5A (compared to the included Cudy AC adapter with 12V 1.5A, which also had problems).
The 2.5 Gbps port is not related either. The issue still reproduces even if one of the 1 Gbps ports (under the same bridge) is configured as WAN.
After installing a router with similar hardware and software (Cudy WBR3000UAX + OpenWrt 24.10.5) and copying the configuration from the main router, the problem persisted.
The problem appears if an iperf server is placed behind the WAN and tested from a computer using "iperf3 -c 192.168.88.50 -P 16 -t 1200 --bidir" while simultaneously trying to use Wi-Fi. I assume that due to NAT + Firewall processing the CPU reaches 100% load (indirectly confirmed by the fact that in br-lan the speed stays around 800 Mbps, while on WAN it drops to ~200 Mbps).
Two possibilities remain:
The MTK driver in OpenWrt has bugs when the CPU is at 100% load;
Cost-cutting on hardware design by Cudy across the router lineup.
I will try installing alternative firmware on the Cudy WBR3000UAX (including OpenWrt forks as well as non-OpenWrt firmware). I want to know if the problem reproduces on them.
Update:
ImmortalWrt (Cudy WBR3000UAX) works fine - iperf shows high performance, Wi-Fi doesn't die under load, but god, what is that a terrible firmware... Right after installation, it downloads something from GitHub, and in some places it outputs stack traces due to some internal utilities, not to mention that UI was spoiled by gradients. (Upd. Looks like I just downloaded a dirty compiled snapshot with someone authored changes)
I wonder if there are any OpenWrt forks that focus exclusively on providing proprietary drivers?