Release Asuswrt-Merlin 386.1 is now available

[bbunge]

Got a RT-AC86U(main) and a RT-AC68U (mesh), after upgrading to 386.1 my main router reboots if there is to much traffic - any ideas?
It was stabile on 384.18 (did a clean flash on both routers).

portforwarding, ipv6 and ddos protection is enabled.

DoS Protection does not add overhead or cause issues o n my AC86U. Check the CPU temperature. AC86U still seems to have a heating problem on some hardware versions although Merlin firmware is better than Asus factory firmware.

 

[Deleted member 72428]

Anyone know what/why this is?

Feb 15 08:07:32 kernel: potentially unexpected fatal signal 11.
Feb 15 08:07:32 kernel: CPU: 1 PID: 12940 Comm: dcd Tainted: P O 4.1.52 #2
Feb 15 08:07:32 kernel: Hardware name: Broadcom-v8A (DT)
Feb 15 08:07:32 kernel: task: ffffffc03e93e100 ti: ffffffc027464000 task.ti: ffffffc027464000
Feb 15 08:07:32 kernel: PC is at 0xf723539c
Feb 15 08:07:32 kernel: LR is at 0x1dd58
Feb 15 08:07:32 kernel: pc : [<00000000f723539c>] lr : [<000000000001dd58>] pstate: 600f0010
Feb 15 08:07:32 kernel: sp : 00000000ff97dbf8
Feb 15 08:07:32 kernel: x12: 00000000000a2050
Feb 15 08:07:32 kernel: x11: 00000000f64ff024 x10: 00000000000a23c4
Feb 15 08:07:32 kernel: x9 : 00000000f64ff91c x8 : 00000000000a287c
Feb 15 08:07:32 kernel: x7 : 00000000f64ff954 x6 : 00000000000a2876
Feb 15 08:07:32 kernel: x5 : 0000000000000000 x4 : 00000000f64ff900
Feb 15 08:07:32 kernel: x3 : 0000000000000000 x2 : 00000000ff97dbd4
Feb 15 08:07:32 kernel: x1 : 000000000007d652 x0 : 0000000000000000

 

[ATLga]

Anyone know what/why this is?

Feb 15 08:07:32 kernel: potentially unexpected fatal signal 11.
Feb 15 08:07:32 kernel: CPU: 1 PID: 12940 Comm: dcd Tainted: P O 4.1.52 #2
Feb 15 08:07:32 kernel: Hardware name: Broadcom-v8A (DT)
Feb 15 08:07:32 kernel: task: ffffffc03e93e100 ti: ffffffc027464000 task.ti: ffffffc027464000
Feb 15 08:07:32 kernel: PC is at 0xf723539c
Feb 15 08:07:32 kernel: LR is at 0x1dd58
Feb 15 08:07:32 kernel: pc : [<00000000f723539c>] lr : [<000000000001dd58>] pstate: 600f0010
Feb 15 08:07:32 kernel: sp : 00000000ff97dbf8
Feb 15 08:07:32 kernel: x12: 00000000000a2050
Feb 15 08:07:32 kernel: x11: 00000000f64ff024 x10: 00000000000a23c4
Feb 15 08:07:32 kernel: x9 : 00000000f64ff91c x8 : 00000000000a287c
Feb 15 08:07:32 kernel: x7 : 00000000f64ff954 x6 : 00000000000a2876
Feb 15 08:07:32 kernel: x5 : 0000000000000000 x4 : 00000000f64ff900
Feb 15 08:07:32 kernel: x3 : 0000000000000000 x2 : 00000000ff97dbd4
Feb 15 08:07:32 kernel: x1 : 000000000007d652 x0 : 0000000000000000

dcd tainted goes way back, aiProtection being on if I recall. Have you done a complete reset and installed from scratch, not backups.

 

[torjohron]

DoS Protection does not add overhead or cause issues o n my AC86U. Check the CPU temperature. AC86U still seems to have a heating problem on some hardware versions although Merlin firmware is better than Asus factory firmware.

46 °C - 53 °C - 75 °C
Does not go over 80 when max-ing the line.

 

[Deleted member 72428]

dcd tainted goes way back, aiProtection being on if I recall. Have you done a complete reset and installed from scratch, not backups.

Ugh... I did just that when I installed 386.1... I wonder why it got screwed up... Kicking kids and wife off the internet for a few hours not going to go well... sigh

 

[torjohron]

It rebooted again - What should i have on "Default message log level" and "Log only messages more urgent than"? - need to figure out why it's rebooting.

 

[ATLga]

It rebooted again - What should i have on "Default message log level" and "Log only messages more urgent than"? - need to figure out why it's rebooting.

Debug will give you a boat load of info

 

[Kees17760]

Got a RT-AC86U(main) and a RT-AC68U (mesh), after upgrading to 386.1 my main router reboots if there is to much traffic - any ideas?
It was stabile on 384.18 (did a clean flash on both routers).

portforwarding, ipv6 and ddos protection is enabled.

Check the CPU temp. See you already did that. Don't have any further ideas, posted this message before refreshing my browser

 

[ATLga]

Ugh... I did just that when I installed 386.1... I wonder why it got screwed up... Kicking kids and wife off the internet for a few hours not going to go well... sigh

The alternative is to just turn off the aiProtection. Withdraw from the privacy tab will do that quickly for you (Administration / Privacy). This will also turn off the other Trend Micro settings too so think about it first if you use those.

 

[ATLga]

Check the CPU temp.

OP posted the temps above your post: 46 °C - 53 °C - 75 °C
Does not go over 80 when max-ing the line.

NM; See you noticed.

 

[Kees17760]

OP posted the temps above your post: 46 °C - 53 °C - 75 °C
Does not go over 80 when max-ing the line.

NM; See you noticed.

Had not refreshed my browser.

 

[CaptnDanLKW]

Anyone having issues with Chromecasts disappearing off the network? A few of mine go AWOL off the Google Home app, but are still visible in the network list on the router.

IIRC, you need to enable IGMP snooping (Wireless --> Professional). This setting is per band, so set it on both to be safe. Not sure if those devices do both 2.4 and 5.

 

[torjohron]

Could this be the problem?

Feb 15 15:35:14 dnsmasq[1944]: nameserver 2a02:fe0:1:2:1:0:1:110 refused to do a recursive query

Removing ipv6 now, maybe that's the problem.

 

[dazedandlost]

The problem in palemoon disappeared after completely clearing the cookies. Flushing the cache was insufficient.

My comment was quite a while ago, but I've been wondering off and on about this. I know nothing, really, about these cookies, collectively or individually: what specific trigger is responsible for setting them, what information they contain, how and by what and for what they are used, etc.

There sure are a bunch of them tho; 15 by my count. I am confident all of them are both necessary and innocent.

But the possibility hasn't been ruled out in my mind that, depending on a bunch of other things which I also know nothing about, there could be an explanation lurking in there somewhere as to why some people see fw u/g's succeed only after some number of attempts.

Going back to sleep now.

 

[RMerlin]

Hi, the upgrade from 384.19 to 386.1 on RT-AC5300 Missing Game Mode. In the new version 386.1_2 still Missing Game Mode on RT-AC5300

Asus does not support Game Mode on that model, that's why it's enabled in my firmware either.

 

[JohnD5000]

Maybe a random glitch but I think I haven't seen this before:

Spoiler: Something missing in GUI

View attachment 30765

Logged in with MS Edge and Firefox. Same result. I have rebooted the router at least twice after updating to 386.1_2 and router uptime was only 16 hours when I noticed the problem. Refreshing the browser didn't affect the situation. Had to reboot the router. After that the GUI was OK again.

I've seen this frequently for quite a while. Just have another tab open in browser, close the Merlin tab and open a new tab to the router. The GUI will open completely and you will also not need to log back in (as long as you have another tab open so that your browser doesn't close). It is easy to solve, and happens randomly (and seems to only happen when Ibhave not gone into GUI for a long time) so it is very hard to diagnose.

 

[Digimite]

Ugh... I did just that when I installed 386.1... I wonder why it got screwed up... Kicking kids and wife off the internet for a few hours not going to go well... sigh

I think I read that the error does not affect the functioning of the router, so you can just ignore it (at least that's what I do). Lots of other threads on that subject here, so you can search it up if you'd like.

 

[MarkyPancake]

My AC86U router is still on 384.19, but a few days ago I decided to update my AC68U node from 384.19 to 386.1 and then to Asus' 9.0.0.4.386.41994, to see how it performed.

After reading some posts about slightly increased heat on the new Asus codebase, I decided to check my AC68U by touch this morning. The ambient temperature of the room was cold and the AC68U was warmer to the touch than I've ever noticed before for any Asus routers I've used. It hadn't really been working much overnight either, with the few devices connected to it mainly idle, as people were sleeping.

I put 384.19 back on the node and checked it by touch again and it's noticeably cooler now, even after actually getting worked today by the devices connected to it.

I'm going to stay away from this new Asus codebase until the higher operating temps issue has been addressed.

 

[ATLga]

My AC86U router is still on 384.19, but a few days ago I decided to update my AC68U node from 384.19 to 386.1 and then to Asus' 9.0.0.4.386.41994, to see how it performed.

After reading some posts about slightly increased heat on the new Asus codebase, I decided to check my AC68U by touch this morning. The ambient temperature of the room was cold and the AC68U was warmer to the touch than I've ever noticed before for any Asus routers I've used. It hadn't really been working much overnight either, with the few devices connected to it mainly idle, as people were sleeping.

I put 384.19 back on the node and checked it by touch again and it's noticeably cooler now, even after actually getting worked today by the devices connected to it.

I'm going to stay away from this new Asus codebase until the higher operating temps issue has been addressed.

It was addressed

 

[torjohron]

My AC86U router is still on 384.19, but a few days ago I decided to update my AC68U node from 384.19 to 386.1 and then to Asus' 9.0.0.4.386.41994, to see how it performed.

After reading some posts about slightly increased heat on the new Asus codebase, I decided to check my AC68U by touch this morning. The ambient temperature of the room was cold and the AC68U was warmer to the touch than I've ever noticed before for any Asus routers I've used. It hadn't really been working much overnight either, with the few devices connected to it mainly idle, as people were sleeping.

I put 384.19 back on the node and checked it by touch again and it's noticeably cooler now, even after actually getting worked today by the devices connected to it.

I'm going to stay away from this new Asus codebase until the higher operating temps issue has been addressed.

It's way cooler on 386.1_2