Release Asuswrt-Merlin 386.12 is now available for AC models

[drinkingbird]

That`s because bandwidth stats uses the bwdpi engine to identify traffic type, so that just reverts back to enabling the engine again.


The issue is unrelated to the signature update.

I never said it was a GOOD theory.

 

[RMerlin]

Since there is no news and the issue is still there, I'm just gonna leave this here. You guys do what you will with that...

echo "#!/bin/sh" > /tmp/fakedcd
echo "sleep 365d" >> /tmp/fakedcd
chmod a+rx /tmp/fakedcd 
killall dcd || mount -o bind /tmp/fakedcd /usr/sbin/dcd

 

[bscabl]

Since there is no news and the issue is still there, I'm just gonna leave this here. You guys do what you will with that...

echo "#!/bin/sh" > /tmp/fakedcd
echo "sleep 365d" >> /tmp/fakedcd
chmod a+rx /tmp/fakedcd
killall dcd || mount -o bind /tmp/fakedcd /usr/sbin/dcd

If I am reading this right... it will allow me to re-enable my traffic analyzing and remove the process causing the crashes?

 

[heysoundude]

Since there is no news and the issue is still there, I'm just gonna leave this here. You guys do what you will with that...

echo "#!/bin/sh" > /tmp/fakedcd
echo "sleep 365d" >> /tmp/fakedcd
chmod a+rx /tmp/fakedcd
killall dcd || mount -o bind /tmp/fakedcd /usr/sbin/dcd

I'm interested in seeing how long it is before Asus updates itself with exactly this script, or if they come up with a fix/better solution...

 

[Master3395]

It seems that AC 88U, has problems with the leasing time with this version.
I have the standard 86400 seconds set on the leasing time.

But my devices, keep getting disconnected after 6 minutes, then starts Access time from 0 and counts up again.
Are there any suggestions, on how to prevent that?

 

[RMerlin]

But my devices, keep getting disconnected after 6 minutes, then starts Access time from 0 and counts up again.

This is a wifi issue, this has nothing to do with DHCP. Your devices are getting disconnected from wifi if the access time reverts back to 0.

 

[Master3395]

This is a wifi issue, this has nothing to do with DHCP. Your devices are getting disconnected from wifi if the access time reverts back to 0.

Is it related to my ISP, or is it a setting within the router, that I have messed up somehow?
I mostly use things as default as possible, the only added feature is yazFi, I even disabled diversion.

Any suggestions to what or where I can diagnose the access time issue?

 

[RMerlin]

Is it related to my ISP, or is it a setting within the router, that I have messed up somehow?

Has nothing to do with the ISP.

If only wifi clients are affected, then it`s something with wifi. Could be interference, using a DFS channel that forces you to vacate it due to radar activity being detected, Look at the numerous posts and guides on the forums on how to troubleshoot wifi related issues.

If Ethernet clients are also losing connectivity, then check the router`s uptime on the System Log page to see if it`s crashing/rebooting itself.

 

[Squall Leonhart]

Not really. Your browser's Safe Browsing engine is more effective than AiProtection and blocks malicious content faster. You have to disable Safe Browsing to trigger eventual AiProtection response. AiProtection can't see anything encrypted, only URLs. Your browser can.

no it isn't.

 

[ttgapers]

Does CakeQos work even with Trend Micro's EULA consent revoked and the AiProtection engine disabled?

Yep it does!

 

[WRobertE]

rt-ac88u
upgraded from 386.11 -> 386.12

I noticed that a few devices on the lan>dhcp server page lost their icons and say "New device" instead of their previous info.
Win10 wtih firefox 119, when clicking icon for the saved entry to fix and apply. its failing to actually update, tosses up a browser console error:

Uncaught TypeError: manually_dhcp_list_array[clientIP] is undefined
    showdhcp_staticlist http://192.168.0.1/Advanced_DHCP_Content.asp:328
    success http://192.168.0.1/client_function.js:1356
    jQuery 6
    updateClientListObj http://192.168.0.1/client_function.js:1345
    card_confirm http://192.168.0.1/client_function.js:1404
    setTimeout handler*card_confirm http://192.168.0.1/client_function.js:1338
    jQuery 8
    popClientListEditTable http://192.168.0.1/client_function.js:655
    jQuery 2
Advanced_DHCP_Content.asp:328:17

Try clearing your browser cache.

 

[zoggy]

Try clearing your browser cache.

ty, worked

 

[UncleDin]

I need help. After installing the new Firmware version:386.12, a lot of errors began to pour into the System Log - General Log. What to do????


Oct 25 21:47:20 kernel: CPU: 1 Tainted: P (2.6.36.4brcmarm #1)
Oct 25 21:47:20 kernel: PC is at 0x40358890
Oct 25 21:47:20 kernel: LR is at 0x40182ee4
Oct 25 21:47:20 kernel: pc : [<40358890>] lr : [<40182ee4>] psr: 60000010
Oct 25 21:47:20 kernel: sp : beea0c20 ip : 4018cde8 fp : beea0cc4
Oct 25 21:47:20 kernel: r10: beea0cc8 r9 : 0000dafc r8 : 0000a620
Oct 25 21:47:20 kernel: r7 : 000000a2 r6 : 00000008 r5 : beea0c68 r4 : beea0c68
Oct 25 21:47:20 kernel: r3 : 00000000 r2 : 00000258 r1 : beea0c68 r0 : fffffdfc
Oct 25 21:47:20 kernel: Flags: nZCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Oct 25 21:47:20 kernel: Control: 10c53c7d Table: 9913804a DAC: 00000015
Oct 25 21:47:20 kernel: dcd/9970: potentially unexpected fatal signal 6.
Oct 25 21:47:20 kernel: Pid: 9970, comm: dcd
Oct 25 21:47:20 kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)
Oct 25 21:47:20 kernel: PC is at 0x40358890
Oct 25 21:47:20 kernel: LR is at 0x40182ee4
Oct 25 21:47:20 kernel: pc : [<40358890>] lr : [<40182ee4>] psr: 60000010
Oct 25 21:47:20 kernel: sp : be3ffdf8 ip : 4018cde8 fp : be3ffe6c
Oct 25 21:47:20 kernel: r10: 40191020 r9 : 401913dc r8 : 00000000
Oct 25 21:47:20 kernel: r7 : 000000a2 r6 : beea0c44 r5 : be3ffe40 r4 : be3ffe40
Oct 25 21:47:20 kernel: r3 : 00000000 r2 : 00000230 r1 : be3ffe40 r0 : fffffdfc
Oct 25 21:47:20 kernel: Flags: nZCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Oct 25 21:47:20 kernel: Control: 10c53c7d Table: 9913804a DAC: 00000015
Oct 25 21:47:20 kernel: dcd/9968: potentially unexpected fatal signal 6.
Oct 25 21:47:20 kernel: Pid: 9968, comm: dcd
Oct 25 21:47:20 kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)
Oct 25 21:47:20 kernel: PC is at 0x403590dc
Oct 25 21:47:20 kernel: LR is at 0xcc9c
Oct 25 21:47:20 kernel: pc : [<403590dc>] lr : [<0000cc9c>] psr: 20000010
Oct 25 21:47:20 kernel: sp : be7ffda0 ip : 403590cc fp : be7ffe6c
Oct 25 21:47:20 kernel: r10: 40191020 r9 : 401913dc r8 : 00000000
Oct 25 21:47:20 kernel: r7 : 000000b1 r6 : beea0c40 r5 : 4018cd74 r4 : be7ffea0
Oct 25 21:47:20 kernel: r3 : 00000008 r2 : be7ffdc4 r1 : be7ffdcc r0 : fffffffc
Oct 25 21:47:20 kernel: Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Oct 25 21:47:20 kernel: Control: 10c53c7d Table: 9913804a DAC: 00000015
Oct 25 21:47:20 kernel: Pid: 9971, comm: dcd
Oct 25 21:47:20 kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)
Oct 25 21:47:20 kernel: PC is at 0x40358890
Oct 25 21:47:20 kernel: LR is at 0x40182ee4
Oct 25 21:47:20 kernel: pc : [<40358890>] lr : [<40182ee4>] psr: 60000010
Oct 25 21:47:20 kernel: sp : be1ffdf8 ip : 4018cde8 fp : be1ffe6c
Oct 25 21:47:20 kernel: r10: 40191020 r9 : 401913dc r8 : 00000000
Oct 25 21:47:20 kernel: r7 : 000000a2 r6 : beea0c44 r5 : be1ffe40 r4 : be1ffe40
Oct 25 21:47:20 kernel: r3 : 00000000 r2 : 00000230 r1 : be1ffe40 r0 : fffffdfc
Oct 25 21:47:20 kernel: Flags: nZCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Oct 25 21:47:20 kernel: Control: 10c53c7d Table: 9913804a DAC: 00000015

 

[ColinTaylor]

I need help. After installing the new Firmware version:386.12, a lot of errors began to pour into the System Log - General Log. What to do????

This is the dcd crash that has been discussed at length in this thread.

Release - Asuswrt-Merlin 386.12 is now available for AC models

This is the expected default wifi password on recent firmware/models. This is incorrect. The default password along with other core default values is stored in a separate part of flash memory. It is independent of the firmware version that's installed. From what I can see this default psk only...

www.snbforums.com

Either withdraw from the TrendMicro licence agreement or revert to the previous firmware until it's fixed.

EDIT: See post #241.

 

[KrypteX]

This is the dcd crash that has been discussed at length in this thread.

Either withdraw from the TrendMicro licence agreement or revert to the previous firmware until it's fixed.

Reverting to previous firmware 386.11 doesn't solve the issue, as @RMerlin said: https://www.snbforums.com/threads/a...lable-for-ac-models.86647/page-11#post-870905
"Asus confirmed that the issue also occurs even with older firmware versions."

I'm not sure I'm following you guys...

 

[ColinTaylor]

Reverting to previous firmware 386.11 doesn't solve the issue, as @RMerlin said: https://www.snbforums.com/threads/a...lable-for-ac-models.86647/page-11#post-870905
"Asus confirmed that the issue also occurs even with older firmware versions."

I'm not sure I'm following you guys...

But RMerlin then said "The issue is unrelated to the signature update". So while it may effect previous versions of stock firmware it may not effect the previous version of Merlin's firmware. I don't see any reports of this problem for 386.11 (but maybe I just missed them).

 

[RMerlin]

But RMerlin then said "The issue is unrelated to the signature update". So while it may effect previous versions of stock firmware it may not effect the previous version of Merlin's firmware. I don't see any reports of this problem for 386.11 (but maybe I just missed them).

Release - Asuswrt-Merlin 386.12 is now available for AC models

How do you disable that trend stuff thing? I see DCD crashes too, but everything still works for me? What are the effects of DCD crashing? Go to Administration >> Privacy tab. DCD crashes cause temporary slowdown in router while process(es) restart.

www.snbforums.com

 

[ColinTaylor]

Release - Asuswrt-Merlin 386.12 is now available for AC models

How do you disable that trend stuff thing? I see DCD crashes too, but everything still works for me? What are the effects of DCD crashing? Go to Administration >> Privacy tab. DCD crashes cause temporary slowdown in router while process(es) restart.

www.snbforums.com

Yes that's what my original reply was referring to. It was unclear to me whether Asus saying "older firmware versions" meant only stock firmware or your previous firmware as well. Like I said, I don't see any reports of this problem with 386.11 (but maybe I just missed them).

 

[KrypteX]

@ColinTaylor With all due respect, please don't confuse people. I linked @RMerlin's response, then he himself did again, but you're still splitting hairs...
If I'm wrong, I'm listening - I'd like to understand what is really going on. Until the problem is solved, I just don't enable TrendMicro.

 

[RMerlin]

I don't see any reports of this problem with 386.11 (but maybe I just missed them).

Probably because there`s no real reason for anyone to still be on 386.11, so probably a very small installed userbase.

The issue mostly manifest itself by filling up the system log, so most people aren`t even aware of the issue. Asus tested a specific older stock firmware which also had the issue, however neither of us started going further back in time, as we already knew enough - that the issue wasn`t from a regression, and was on Trend Micro`s side.