Release ASUS RT-AC68U Firmware version 3.0.0.4.386.51665

[wouterv]

Too bad there is no feedback on the suggested settings.

 

[StrikerXXX]

Good morning! Guys, someone who is using this version is having constant loss of ipv6 when connected to the pc via a wired network?

Here lately I've noticed that I've been having constant ipv6 prefix losses using my pc, wired network, on the smartphone it's normal, ipv6 functional.

What is causing this problem, the pc losing ipv6 prefix constantly?

 

[Clarkbug]

Good morning everyone.

Long time lurker here, first time posting anything.

Logged into my router, and noticed that the client list was not updated. I have several devices that are working fine on my network, but they dont show up in the list. Im also seeing that one of my CPU cores is maxed out at 100%, while the other is between 3-5%. Sometimes the first will dip down to 70%, but when that happens the second picks up the slack to equal 100 again. A reboot seems to temporarily fix this problem.

Has anyone else seen this behavior on this latest firmware?

 

[L&LD]

Welcome to the forums @Clarkbug.

Are we to assume your router is the RT-AC68U (original)?

What firmware are you running on it? What features and options have you enabled?

 

[wouterv]

I can add that my RT-AC68U has an uptime now of 96 days with the latest firmware 3.0.0.4.386.51665.
If you scroll back you see some issues I have seen with this firmware, that are pretty sure related to bad "ahs JSON file" updates, the system log doesn't go back further than July 11, no more weird issues since and here the status, this is what I do see in average (RAM usuage depends on network activity, quite idle it shows 85 MB used):

A general advice for routers with issues:

• If there are, disconnect all USB devices.
• Install the latest available firmware version.
• Reset to factory defaults.
• Do not load an old configuration backup file, manual configure the router as outlined in the next step.
  • While making configuration changes: write them down so you do have a list of changes you made from factory defaults.
  • Restoring a configuration backup might bring back old issues, that is why the manual configuration is advised.
  • Whenever you restore a configuration backup: only restore the backup to exactly the same firmware branch and version as it was made with.
• Manual configure the router with the bare minimum, as:
  • Router Login Name.
  • Router Login Password.
  • WAN Connection Type, and what is required to connect to the Internet.
  • Wireless SSID's and WPA Pre-Shared Key's.
  • Leave everything else default.
• Test the router behavior.
• After the above works all well you can consider more manual router configuration changes.

 

[Clarkbug]

Welcome to the forums @Clarkbug.

Are we to assume your router is the RT-AC68U (original)?

What firmware are you running on it? What features and options have you enabled?

Thanks for the Welcome!

Yes, this is an original RT-AC68U. I am currently on the 3.0.0.4.386.51665 Firmware.

I dont have anything plugged into the USB ports, have a single guest network enabled, and have turned off airtime fairness based on some readthroughs here. Not currently using the traffic analyzer or any of the other options that you can opt into. Not sure what other features/options might make a difference here.

I also have not selected anything new since upgrading to this particular firmware, just did a flash through the GUI when it became available.

 

[wouterv]

A fresh start won't hurt anyway, see post #65.

 

[wouterv]

Just for the records

The router has a straight forward setup and connects to the fiber optic modem, the only thing "special" is the 16 GB USB stick that sits in there as intermediate network storage.
The wireless clients are iPhones, Windows laptops, a printer and a RT-AC1900U as Media Bridge.
Behind the Media Bridge is the TV set top box, due to interaction of my self the uptime of the RT-AC1900U is only 43 days.

 

[Clarkbug]

A fresh start won't hurt anyway, see post #65.

I gave things a fresh start, and everything seems to be happy, but Ill let it run for a few more weeks and see how things shake out.

Is it generally accepted that airtime fairness and both types of beamforming should be disabled?

 

[L&LD]

No, only implicit beamforming usually causes issues. Explicit beamforming is usually beneficial.

 

[tl3000]

Is it generally accepted that airtime fairness and both types of beamforming should be disabled?

Every operating environment is different. For my house and network configuration, one of my WiFi IoT clients fails to connect when implicit beamforming is disabled. Test and see what works best for your setup.

 

[L&LD]

Have you tried resetting the IoT client after disabling implicit beamforming, rebooting the router, and then re-associating that IoT client again with the router?

 

[banger]

Seeing this constantly in the log. Have rebooted but it's not going away. What is DCD?

Oct 30 23:37:27 kernel: dcd/14270: potentially unexpected fatal signal 6.
Oct 30 23:37:27 kernel: Pid: 14270, comm: dcd
Oct 30 23:37:27 kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)
Oct 30 23:37:27 kernel: PC is at 0x40336340
Oct 30 23:37:27 kernel: LR is at 0x4009d214
Oct 30 23:37:27 kernel: pc : [<40336340>] lr : [<4009d214>] psr: 60000010
Oct 30 23:37:27 kernel: sp : bddfa630 ip : 400a7e5c fp : 403931a0
Oct 30 23:37:27 kernel: r10: 000c3520 r9 : 00000000 r8 : 00000000
Oct 30 23:37:27 kernel: r7 : 00000025 r6 : 00000006 r5 : 000037be r4 : 400a8068
Oct 30 23:37:27 kernel: r3 : 400a8068 r2 : 00001406 r1 : 00000006 r0 : 00000000
Oct 30 23:37:27 kernel: Flags: nZCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Oct 30 23:37:27 kernel: Control: 10c53c7d Table: 06b4404a DAC: 00000015
Oct 30 23:37:27 kernel: dcd/14264: potentially unexpected fatal signal 6.
Oct 30 23:37:27 kernel: dcd/14262: potentially unexpected fatal signal 6.
Oct 30 23:37:27 kernel: Pid: 14262, comm: dcd

 

[Tech9]

TrendMicro Data Collection Daemon. Asus has to fix, broken. See 386.12 thread for more details.

 

[banger]

Ahhh thanks will have a look at 386.12.

 

[wouterv]

You and me reported the same dcd crash back in May.
For my router it appeared only very occasional and AiProtection is OFF since ever:

 

[banger]

If you want AiProtection on and not have a log full of tainted indicators, Merlin posted a work around.

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

Apply using SSH. Not sure if it survives reboot, probably not.

 

[banger]

Still getting a few errors in the log so turned off Trend Micro stuff by withdrawing from privacy agreement and now have a quiet log and 177mb RAM free.

 

[Tech9]

and now have a quiet log

And a faster more stable router. Number of issues in Asuswrt come from TrendMicro components.