Archer AX21 v1.26 - Router (AP Mode) unresponsive after random amount of time, regardless of usage
As the title reads, my Archer AX21 hardware revision v1.26 (The Web UI says v1.20 but the bottom sticker on the router says v1.26 so I am putting v1.26 as it seems both revisions may use the same firmware which is why it is reporting v1.20 and not v1.26) in Access Point Mode will effectively die after an indeterminate amount of time (13 hours to 20 minutes) even with nothing going on.
What I mean by that is, the devices will get disconnected from the WiFi network and the web ui will not be able to be accessed until a restart is performed, I am able to monitor this by pinging the device and for my logging, it is pinged every 15 seconds and that is how I got the figures of 13 hours to ~20 minutes, it is important to note, the 20 minutes of runtime was after the previous 13 hour deadlock, it was in that state (deadlock) for 16 hours before being rebooted, firmware updated and then going down after 20 minutes of uptime, It is likely not my Router (running OPNsense) or Switch (running OpenWrt) as if that were the case, my ethernet devices would cease getting internet or have issues but it is only the Archer AX21 and furthermore, my switch is an Archer C7 v4 AC1750 and it works perfectly fine even now as both a Switch and an AP (when the issues arised, the WiFi was either not on, on the AX21 or the WiFi was disabled on my Archer C7 v4 so the Archer C7 should not be affecting anything).
Here is the ping history for the AX21 after having a few days of not being used:
Configuration: Router powered on and connected to internet via the WAN port (no 5G or 2.4G network enabled and no ethernet/switch devices connected, so it should be doing nothing):
Here is the ping history for the AX21 after being rebooted after 16 hours of being in the deadlocked state (as I am calling it) and getting a reflash of the firmware from TP-Link's website:
Configuration: Same as previous but the firmware was reflashed:
I am assuming it could be thermal related (and that in the deadlocked state, it may still be trying to do work but stuck (needs to be true for my thermal theory to be correct)) although unfortunately, it appears that the Web UI of the AX21 does not report CPU temperatures and even if it did, it seems that TP-Link does some annoying obfuscation/encryption so it is not easy to directly get the values from an http request so it can be easily monitored/logged. (My mistake for going for a device that does not seem to have good custom firmware support which makes it 100x harder to debug)