[Release] Asuswrt-Merlin 384.13 is now available

[WNorkle]

Updated my RT-AC87U this morning. Took 2 tries after removing the USB drive - which seems to be the new normal for me. The one odd thing is that after the upgrade completed, both WiFi radios were disabled. Not sure how/why that happened. After enabling them in the gui, everything seems to be working on 384.13

 

[Mistogan]

Known issue. Asus removed something (cpu idle) that was causing trouble and it caused the temp to increase about 10 centigrade, I have same as you and mine went up as well.

OK, waiting fix, thx.

 

[Mutzli]

Hmm, AX88U dirty update from 384.12 = +10° CPU temperature.

You can use the following code in your SSH console to enable it again if the temperature concerns you:

pwr config --cpuwait on

It will lower the temps within seconds of activating it. I didn't observe any issues yet. Have it active since beta1. You can always turn it off again with the following command: pwr config --cpuwait off

 

[Mistogan]

You can use the following code in your SSH console to enable it again if the temperature concerns you:

pwr config --cpuwait on

…

What is default value at new firmware on or off? It's a bug or not?

 

[Mutzli]

What is default value at new firmware on or off? It's a bug or not?

It's off

 

[Mistogan]

Thanks a lot. It's wery strange, why it put off.

 

[Mutzli]

Thanks a lot. It's wery strange, why it put off.

AFAIK Asus didn't release any info on why they turned it off.

 

[GHammer]

No problem with upgrading an 86U from 384.12
A few static DHCP assignments but otherwise plain vanilla config.
No factory reset was done, just a power cycle before and after.

 

[Mutzli]

I noticed that QoA configuration was not reset to its default values during this update. Was that fixed or was I just lucky?

 

[ionutz4u]

I`ve just updated my RT-AC87U from 384.12 to 384.13, but i`m still getting:

Aug 1 17:40:57 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use
Aug 1 17:42:01 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use
Aug 1 18:46:23 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use
Aug 1 18:46:25 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use


Is there any way to get rid of this 'error' ? What should i check/uncheck ?
Thanks.

 

[QuikSilver]

I noticed that QoA configuration was not reset to its default values during this update. Was that fixed or was I just lucky?

Must be lucky, both of my units 86u had to be redone.

 

[jsbeddow]

BTW @RMerlin, getting back to you on the OpenVPN server issue I raised yesterday in the 384.13 Beta thread (it would not startup, despite clearing the keys, defaulting the settings, then re-importing the settings ), after updating to the 384.13 final release version this morning AND formatting the JFFS partition, the problem was solved (I did not need to do a full factory default reset). My previous symptoms and syslog entries were exactly the same as this user posted a few months back over here in the VPN section:
OpenVPN server not starting on Merlin

One curious item I have been noticing lately: if a guest network is set to the normal default of blocking access to the "intranet" (ie: the LAN resources), and we are using Diversion/Skynet, it will also completely block some websites from loading. I have to specifically un-block/allow these guest networks to access to the "intranet" in order to regain access these sites. In a way, I understand what is happening, but it still seems to defeat the purpose of guest networks when we have to grant access to the local LAN resources.

 

[heysoundude]

ac86u dirty flash from 384.12 (why not? Lucky 13!)
All is well (so far) as far as I can tell...

 

[Wallace_n_Gromit]

downloaded and installed the latest firmware 384.13. While going through all the settings, I see in <Tools > Sysinfo> that my CPU temperature had bumped up over 30 degrees C. Scrambled to find a fan to cool it off. Still running very hot, normal operating temperature was about 75 degrees C +- 3 degrees.

 

[predatorz]

Dirty upgrade from 384.12 on AC88U.
Thanks for the hard work!

 

[Wallace_n_Gromit]

downloaded and installed the latest firmware 384.13. While going through all the settings, I see in <Tools > Sysinfo> that my CPU temperature had bumped up over 30 degrees C. Scrambled to find a fan to cool it off. Still running very hot, normal operating temperature was about 75 degrees C +- 3 degrees.

I have a RT-AC68U that definately overheats running at over 92 degrees C (without a active cooling solution), BUT I can definately tell because the outer case gets extremely hot to the touch. This one is showing temps of over 100 degrees C, YET I cannot feel the heat on the outer case to the touch. Is it possible that the CPU temp reading is false? How can I test for that?

 

[Butterfly Bones]

I have a RT-AC68U that definately overheats running at over 92 degrees C (without a active cooling solution), BUT I can definately tell because the outer case gets extremely hot to the touch. This one is showing temps of over 100 degrees C, YET I cannot feel the heat on the outer case to the touch. Is it possible that the CPU temp reading is false? How can I test for that?

EDIT - Only applies to AX-88U, sorry!

Read a few posts above and below this one.
https://www.snbforums.com/threads/release-asuswrt-merlin-384-13-is-now-available.57860/page-2#post-507546

There is an RMerlin posted possible workaround, what Asus did and why. Some searching will find it.

This CPU temp topic seems to post a few times a day over many forum topics.

 

[Wallace_n_Gromit]

Read a few posts above and below this one.
https://www.snbforums.com/threads/r...-13-is-now-available.57860/page-2#post-507546

There is an RMerlin posted possible workaround, what Asus did and why. Some searching will find it.

This CPU temp topic seems to post a few times a day over many forum topics.

Sorry, normally I would follow the posts. Because of the "extreme overheating" issue and thinking my router was about to bite the dust, I was scrambling for a solution and a active fan.

 

[Wallace_n_Gromit]

You can use the following code in your SSH console to enable it again if the temperature concerns you:

pwr config --cpuwait on

It will lower the temps within seconds of activating it. I didn't observe any issues yet. Have it active since beta1. You can always turn it off again with the following command: pwr config --cpuwait off

:/tmp/home/root# pwr config --cpuwait on
-sh: pwr: not found

I guess the "pwr" command isn't part of the default installs of amtm, diversion, or entware? how do I install "pwr"?

 

[dave14305]

:/tmp/home/root# pwr config --cpuwait on
-sh: pwr: not found

I guess the "pwr" command isn't part of the default installs of amtm, diversion, or entware? how do I install "pwr"?

Not applicable to an AC68U. You have a different yet troubling issue.