Beta Asuswrt-Merlin 386.1 Beta is now available

[jorhett]

Everything works just fine with a self-signed certificate.

Certainly MitM is easiier

 

[jorhett]

Does Let's Encrypt work with custom ddns providers? Using a cloudflare custom script, and Let's encrypt is stuck at "authorizing". However, running /sbin/le_acme runs fine and generated all the certificates. UI still stuck at "authorizing".

Nothing about acme or Let's Encrypt in the logs.

I was seeing the same problem. I found that the LE certificate was properly generated in /jffs/.le/ so I manually removed /etc/cert.pem and /etc/key.pem and stuff, then redid the authorization from the panel and it worked.

Seems like there's something in the code that won't replace a valid certificate, even if you're switching from self-generated to LE...

 

[jorhett]

The MTU would be set as empty, which would stop all internet access.

...for people who had upgraded without a reset.

Sorry, my reply was subject to a thing that I see sometimes here where it seems to filter the view, and thus your later posts weren't visible to me. After I'd posted suddenly 10 more pages of comments appeared

Still-- the type of questions I posted would have helped people help you faster.

 

[GaselK]

RT-AX56U Beta 3 works as intended. No noticeable bugs or misbehavior.
I also get a hold on an RT-AX92U. WOW This router is a blast with 64bit Broadcom BCM4906 (1.8 GHz, 2 cores)/256-512/BCM4352 2x2/BCM43684 4x4/Tri-band. I wish there was a Merlin fw for it also...

 

[HearToLearn]

Dirty Update - RT-AX88u / RT-AC88u both working as expected in conjunction with RT-AX92u using the latest stock firmware and AiMesh 2.0.

Addons:

• diversion
• skynet (Suricata broke before the update)
• cake-qos

Note: initial startup time is long and looks like it failed to update. Just make a tea and try not to interfere (like I did .

 

[elorimer]

Running the command "pwr config --wait on" has re-enabled the CPU wait state.

Temps are slowly dropping towards 90 degrees now.

I ran this command and my temps dropped immediately from 95C to 85C. A little warmer than the 80C with Beta2.

This is in the open air in a room at 20C, nothing around it.

 

[Blacklistedcard]

cooking beta 4 now.....

 

[mbze430]

normally I have an USB fan blowing air into the AX88U it sits around 70-72. Now with Beta 3 it is sitting around 68-70

 

[shabbs]

As I suspected, this was a deliberate change by Asus in a recent GPL merge.

@@ -3613,6 +3701,9 @@ void init_others(void)
#ifdef GTAC2900
        update_cfe_ac2900();
#endif
+#if defined(RTAC86U) || defined(GTAC2900)
+       system("pwr config --wait off");
+#endif
#if defined(RTAX88U) || defined(RTAX92U)
        if(nvram_match("HwVer", "1.0")) {
                system("pwr config --cpuwait off");

No idea why, I can only assume it was to address a specific problem, like how they already do the same on earlier revisions of the RT-AX88U.

If your router is hitting the 100C threshold following this change, then it means it was already running hotter than it should. Make sure you do have some airflow around it (and that it's not in an enclosed cabinet), maybe give it a good dusting just to be sure.

If you still run into CPU throttling, I recommend you test again running Asus's stock 386_41535 firmware, reproduce the issue, then use the Feedback form to notify them.

Thanks for the root cause analysis @RMerlin. Will keep an eye on temps. No concerns on my two RT-AC86U's yet. Summer time will be an issue for the one in my garage though as the ambient temps get up there. Maybe I'll have a new router by then... heh.

I take it this is likely to stay in their GPL for a while? Unless there are a slew of issues reported and they revert?

 

[Blacklistedcard]

cooking beta 4 now.....

beta 4 looks good on my AX88U and AC86U.

 

[Wade Coxon]

Would guess that command could be run in a startup script on an AC86U pending a fix? Keep us posted on your Temps, please.

Ok, I have left my router in this state for most of the day, but as of 11pm, I have been gaming and watching videos etc, which has been keeping the router busy (with Cake QoS enabled), and temps were up at about 97 again even with the CPU wait state enabled.

As I was checking the stats and logs, I saw the CPU go into thermal overload, and only the one working core was showing on the main page CPU utilisation meter.

Doors are closed, so even though it is evening, I would say the room may still be around 30 degrees ambient. The router is sitting on a desk by a window, so the ventilation can't get much better.

I have had to roll back to beta 2, and immediately my temps are down at 90 degrees and falling. It appears that enabling the CPU wait state is not enough to offset the additional heat that beta 3 has introduced.

 

[heysoundude]

Ok, I have left my router in this state for most of the day, but as of 11pm, I have been gaming and watching videos etc, which has been keeping the router busy (with Cake QoS enabled), and temps were up at about 97 again even with the CPU wait state enabled.

As I was checking the stats and logs, I saw the CPU go into thermal overload, and only the one working core was showing on the main page CPU utilisation meter.

Doors are closed, so even though it is evening, I would say the room may still be around 30 degrees ambient. The router is sitting on a desk by a window, so the ventilation can't get much better.

I have had to roll back to beta 2, and immediately my temps are down at 90 degrees and falling. It appears that enabling the CPU wait state is not enough to offset the additional heat that beta 3 has introduced.

It seems someone at Asus may live in chillier climes, since they've added a space heater feature with this update. ;-p

 

[Clark Griswald]

RE AC86 Temps
Until now the only temperature issue my ac86u experienced is the setting is stuck on Canadian and won't stay on Foreigner

 

[shabbs]

RE AC86 Temps
Until now the only temperature issue my ac86u experienced is the setting is stuck on Canadian and won't stay on Foreigner

You mean the rest of the developed world?

METRIC FTW!

 

[RMerlin]

Certainly MitM is easiier

If you can be victim to a MitM attack within your own LAN, then you have a major problem already.

 

[bbunge]

Back on 386 beta 3. Did a services-start script file to run "pwr config --wait on" and the CPU temp is holding at 83-84 C. Cooling fan on order...

 

[jsbeddow]

Back on 386 beta 3. Did a services-start script file to run "pwr config --wait on" and the CPU temp is holding at 83-84 C. Cooling fan on order...

The big question is why did Asus feel the need to deliberately disable these CPU wait states on this firmware (presumably with full knowledge of the effect on CPU temps). Odd.

Edit: Unless it is related to this (and perhaps why we are seeing higher temps even after re-enabling of the CPU wait states): https://www.snbforums.com/threads/asuswrt-merlin-386-1-beta-is-now-available.68205/post-638759

 

[L&LD]

On 386.1 Beta 3 and RT-AC86U for most customers: temperatures haven't changed. 86C 'normal'. No fans needed. With many being in operation for a year or more.

 

[jsbeddow]

On 386.1 Beta 3 and RT-AC86U for most customers: temperatures haven't changed. 86C 'normal'. No fans needed. With many being in operation for a year or more.

Err..well, if you define "normal" as within operating specification, OK, yes that is true. However, these RT-AC86U units are definitely running at least 6-12C (or more) higher than on previous firmware releases.

Edit: For those that are seeing temperatures in excess of 99-100C along with throttling, or intermittent display of only one CPU core reported as operating, I would venture to guess that the heaksink/thermal pad interface is in need or attention and/or renewal. Obviously, the problem here is whether doing so might void any remaining warranty claim possible through Asus or your retailer, so it is a bit of a gamble or tradeoff to evaluate whether it would be worthwhile doing so. If your warranty has definitely expired, the choice is simpler.

 

[Wisiwyg]

FWIW, Asus dropped an update to the Official Beta today... 12/31/2020 in the 'Official' forum section.