That's not possible, since beta2 for the RT-BE92U only contains webui changes.
As others pointed out, that thread was to gather feedback specifically on the stock firmware, to determine if the GPL version used in that stock firmware contained the sames issues or different ones.
Placebo. The only changes between beta1 and beta2 are at the webui level, and a bugfix related to Wireguard (which does not impact the RT-BE92U).
21d30a367f Bumped revision to 3006.102.7 final
7b6810ec20 Updated documentation
2bc9ee0923 rc: refresh wireguard BLOG bypass when refreshing VPN...
The problem is specific to Brazil. Due to a large number of recent attecks from Brazilian IP ranges, my provider had to block these ranges. Myself, I also encountered something similar on my own server this morning, where a bunch of Brazilian IP addresses were flooding my customers websites...
Seems to be country-specific then.
I opened a ticket with the hosting provider, having already confirmed on my end that the issue isn't caused by Cloudflare.
The weights could possibly be adjusted, but I doubt it's a priority for @thiggins . Personally I never even noticed there was a Trending widget on the forums until mentionned here.
Trends are probably global, which means none of the newer threads are getting enough views and new replies to get higher on the list.
The forums did get quieter these past few weeks.
I was only able to reproduce the RTC reset with Asuswrt-Merlin, I couldn't reproduce it when running the stock firmware after trying for about 3-4 days, which indicates the issue was only with the GPL version that Asuswrt-Merlin was using.
My provider seems to be doing server updates and breaking stuff along the way. A few days ago they made a change that removed the PHP handler I was using, I had to switch to a different PHP handler.
Ran some tests with them, the most major stability issues seem specific to the GPL version that I am using. I also tried to gather user feedback on the forums, apparently all those people who claimed their RT-BE92U was totally unusable have disappeared, the feedback received from current users...
Recent 3006 releases completely changed the way wireless networks are stored in nvram. If your script was designed for 3004 or early 3006, then that script will no longer work.