When you initially replied:
-
I was already on firmware version 4.1.0beta3; I switched to it before your reply:
-
I followed your instructions and removed the previous crash log.
-
I disabled my repeater:
-
I obtained the /etc/config/wireless config file at that time.
wireless.zip (883 Bytes)
The only WiFi clients that were connected at that time were my iPhone 12 Pro and my Roku TV (made by Element Electronics, model E4FAA43R). My iPhone 12 Pro uses randomized MAC address (called Private Address in settings). My 2022 13" M2 Macbook Air laptop is also connected, but through Ethernet, not WiFi.
For other things nearby that may be important, there is a microwave and wireless LED lights connected to an Alexa in my room.
While I was using repeater at the time, I said before that I disabled my repeater. However, if the information is really necessary, I was connected to my college’s WiFi network, through Cisco Aironet 3800 Series Wi-Fi Access Point (AIR-AP3802I-B-K9). It connects through WPA2 Enterprise, with a username and password.
Today, after 3 days of stable behavior, the router crashed again.
For context, I was coming back to my room, and my phone tried to connect to the router while I was nearby. Then, my phone suddenly disconnected, and I check the admin page and see that the router had crashed.
Here is the exported log after this most recent crash:
logread(1).tar.zip (28.7 KB)
Here is also the most up-to-date /etc/config/wireless config file:
wireless.zip (866 Bytes)
Here is what is currently connected:
I feel that the relatively increased stability may be in part due to the custom fan temperatures I set: I followed this information and the temperatures have been consistently at 60F and the router didn’t crash for about 3 days.
However, if you would like, I could reflash the router with 4.10 again and wait for a crash just to prove that my modifications have not contributed to the crash. The router was already crashing before that fan modification anyways.
Another thing that I was trying to do earlier was SSH using VSCode. It consistently failed to connect, but I suspect it is due to an OpenWRT/CPU architecture issue, not the router itself (see this for more information). Apparently VSCode attempts to puts a directory called vscode-server onto the remote server when you SSH into it, but when I checked through SSH later, it did not seem to be there (likely because the connection kept failing).