[Beta] Asuswrt-Merlin 384.14 Beta is now available

[scjr]

Did a dirty flash over 384.13 yesterday evening CET. This morning the DHCP was not working, the router indicated internet was down and the CPU usage was constantly high. Did a reboot and everything was working again. Now it's evening again and had the same issue. Reverted back to 384.13. Log did not indicate crashes while there was a high CPU usage. Router model is RT-AC86U.

I had an issue with “Internet status: Disconnected” when I flashed over 384.13.

https://www.snbforums.com/threads/internet-status-disconnected.59830/

I ended up resetting to factory default and loaded all my settings manually. I’ve had no issues since. It’s been nearly 3 weeks. Might want try a reset.

 

[RacerRon]

Did a dirty flash over 384.13 yesterday evening CET. This morning the DHCP was not working, the router indicated internet was down and the CPU usage was constantly high. Did a reboot and everything was working again. Now it's evening again and had the same issue. Reverted back to 384.13. Log did not indicate crashes while there was a high CPU usage. Router model is RT-AC86U.

I had the same thing happen with my AX88u master with two AC88u mesh nodes on stock Asus. I did not have time to reset and reconfigure so, am back on .13 and all is well for now.

Sent from my Pixel 4 XL using Tapatalk

 

[nlurker]

It is also caused by enabling Traffic Analyzer - Statistic. When I turn that and AiProtection off, no more crashes cluttering up the log.

I disabled that now and I will see if the crashes stop. It is too bad because I like the Traffic Analyzer - Statistic feature.

 

[nlurker]

Did a dirty flash over 384.13 yesterday evening CET. This morning the DHCP was not working, the router indicated internet was down and the CPU usage was constantly high. Did a reboot and everything was working again. Now it's evening again and had the same issue. Reverted back to 384.13. Log did not indicate crashes while there was a high CPU usage. Router model is RT-AC86U.

This exact situation has happened to me many times over the last year with every merlin release during that time. The only pattern I have noticed is it has happened a few times at the exact moment I opened my laptop (on ethernet). But it has also happened at other random times, like in the middle of the night when I was doing nothing. Along with no DHCP and high CPU usage, the light on my USB stick was constantly flashing and felt hot.

 

[krgck]

I am using pretty minimal settings so no jffs scripts etc. No issues that i can report.

Some lines that im not sure was they in 384.13

Wlan: (likely smart connect?) Lines like these pop often, default settings used.
acsd: selected channel spec: 0x1002 (2)
acsd: Adjusted channel spec: 0x1002 (2)
acsd: selected channel spec: 0x1002 (2)
acsd: acs_set_chspec: 0x1002 (2) for reason APCS_CSTIMER

No oddities with QOS

Turning leds off and on from webui does work, but when unplugging wan cable, the wan led turns off instead lighting red. It will come back normal white when plugging back.

So far so good thanks!

Using AC88U

 

[FLA_NL]

I ended up resetting to factory default and loaded all my settings manually. I’ve had no issues since. It’s been nearly 3 weeks. Might want try a reset.

I had the same thing happen with my AX88u master with two AC88u mesh nodes on stock Asus. I did not have time to reset and reconfigure so, am back on .13 and all is well for now.

This exact situation has happened to me many times over the last year with every merlin release during that time. The only pattern I have noticed is it has happened a few times at the exact moment I opened my laptop (on ethernet). But it has also happened at other random times, like in the middle of the night when I was doing nothing. Along with no DHCP and high CPU usage, the light on my USB stick was constantly flashing and felt hot.

I mostly do dirty flashes, but this is the first time that I experienced this. I don't use USB devices on the router. If I have to do a factory reset and manual configuration, I probably wait for the release.

 

[rgnldo]

@RMerlin

AC86U device - FW 384.13

UPGRADE - FW 384.14 (beta1)

Procedure:
- Firefox with cache cleared
- backup current configuration;
- backup JFFS;
- reset to previous FW 384.13;
- Firefox with cache cleared;
- upgrade new FW beta;
- reset FW beta installed;
- Firefox with cache cleared
- FW and JFFS configuration recovery.

FW beta fully functional.

Otherwise, these were the only records I found. If it is functional, ignore it.

Nov  9 07:56:39 modprobe: module ip6t_REJECT not found in modules.dep
Nov  9 07:56:39 modprobe: module ip6t_ROUTE not found in modules.dep
Nov  9 07:56:39 modprobe: module ip6t_LOG not found in modules.dep

May  5 02:05:18 modprobe: module ext3 not found in modules.dep
May  5 02:05:18 modprobe: module ext4 not found in modules.dep
May  5 02:05:18 modprobe: module ext2 not found in modules.dep

 

[sanchez13]

@RMerlin: 3.0.0.4.384.81219 for RT-AC5300 has been released.
https://www.asus.com/sk/Networking/RT-AC5300/HelpDesk_BIOS/

Can be used for 384.14 (RT-AC5300) version ?

S.

 

[octopus]

@RMerlin: 3.0.0.4.384.81219 for RT-AC5300 has been released.
https://www.asus.com/sk/Networking/RT-AC5300/HelpDesk_BIOS/

Can be used for 384.14 (RT-AC5300) version ?

S.

Have to wait for source code to get anything to compile.

 

[nlurker]

It is also caused by enabling Traffic Analyzer - Statistic. When I turn that and AiProtection off, no more crashes cluttering up the log.

I have disabled both AIProtection and Traffic Analyzer Statistics, and rebooted. The DCD crashes continue unabated. Is there anything else to disable?

 

[taffeys]

Uptime of 24 hours, no issues noticed or logged.

 

[cmkelley]

I disabled that now and I will see if the crashes stop. It is too bad because I like the Traffic Analyzer - Statistic feature.

Why? There is zero harm from dcd crashing and restarting itself over and over, other than a bit of clutter in the log file, which there are a couple methods to either scrape those messages from the log file or send them to their own file (scribe). If you never looked at the system log, you'd never know it was happening, as it has no affect on the operation of the router.

 

[dosborne]

Can you test to see if the LED button has the same behaviour as the webui setting?

I believe so. Will test when I get a chance.

Usually when I see the sole WAN LED on, I press the button to turn them on, then again to turn them (until the next WAN failure,)

 

[Striker317]

@RMerlin

AC86U device - FW 384.13

UPGRADE - FW 384.14 (beta1)

Procedure:
- Firefox with cache cleared
- backup current configuration;
- backup JFFS;
- reset to previous FW 384.13;
- Firefox with cache cleared;
- upgrade new FW beta;
- reset FW beta installed;
- Firefox with cache cleared
- FW and JFFS configuration recovery.

FW beta fully functional.

Otherwise, these were the only records I found. If it is functional, ignore it.

Nov  9 07:56:39 modprobe: module ip6t_REJECT not found in modules.dep
Nov  9 07:56:39 modprobe: module ip6t_ROUTE not found in modules.dep
Nov  9 07:56:39 modprobe: module ip6t_LOG not found in modules.dep

May  5 02:05:18 modprobe: module ext3 not found in modules.dep
May  5 02:05:18 modprobe: module ext4 not found in modules.dep
May  5 02:05:18 modprobe: module ext2 not found in modules.dep

Your last step rendered every step previous to be redundant. You might as well have done a dirty flash.

 

[Sanna1967]

@RMerlin

AC86U device - FW 384.13

UPGRADE - FW 384.14 (beta1)

Procedure:
- Firefox with cache cleared
- backup current configuration;
- backup JFFS;
- reset to previous FW 384.13;
- Firefox with cache cleared;
- upgrade new FW beta;
- reset FW beta installed;
- Firefox with cache cleared
- FW and JFFS configuration recovery.

FW beta fully functional.

Otherwise, these were the only records I found. If it is functional, ignore it.

Nov  9 07:56:39 modprobe: module ip6t_REJECT not found in modules.dep
Nov  9 07:56:39 modprobe: module ip6t_ROUTE not found in modules.dep
Nov  9 07:56:39 modprobe: module ip6t_LOG not found in modules.dep

May  5 02:05:18 modprobe: module ext3 not found in modules.dep
May  5 02:05:18 modprobe: module ext4 not found in modules.dep
May  5 02:05:18 modprobe: module ext2 not found in modules.dep

https://www.snbforums.com/threads/384-14_alpha-builds-testing-all-variants.59019/page-16#post-524154

 

[ChatmanR]

Upgrade RT-AC86U from V38413 to V384.14_beta1 via dirty firmware upgrade. 52 devices and all appears to be working. Let's Encrypt doesn't work?

 

[Sanna1967]

Let's Encrypt doesn't work?

Post #2 of this thread
https://www.snbforums.com/threads/beta-asuswrt-merlin-384-14-beta-is-now-available.60037/#post-524837

 

[kernol]

Dirty upgrade from 384.13 to 384.14Beta1 on RT-AC86U - all stable - LED's on/off via webgui works.
Add-ons per signature fully functional and stable - but noticed that WLC events now reappear in System Messages instead of in wlceventd.log under Syslog-ng ... but probably something for @cmkelley to fix in his scribe script. [Description of event change in firmware log output?]

 

[LimJK]

I updated to 384.14_beta1 over 384.14_alpha2
Have been running without trouble yet for 2 days Thank You!

 

[FLA_NL]

I ended up resetting to factory default and loaded all my settings manually. I’ve had no issues since. It’s been nearly 3 weeks. Might want try a reset.

Didn't have the patience to wait for the release, so I did a factory reset and manually configured everything again. Now see how it runs.