What's new

[Release] Asuswrt-Merlin 384.16 (and 384.13_6) are now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
RT-AC86U w/384.16 shows these log entries every 30 minutes on the second:
Apr 13 00:16:32 RT-AC86U kernel: [tdts_shell_ioctl_stat:256] Recv ioctl req with op 2

I've seen a similar issue on the forum dated sometimes in 2018. @RMerlin requested the output of the following commands:

Code:
asmin@RT-AC86U:/tmp/home/root# lsmod | grep tdts
tdts_udbfw             45310  1
tdts_udb              202892  1 tdts_udbfw
tdts                  413315  2 tdts_udbfw,tdts_udb
bcm_enet             1072483  1 tdts_udbfw
pktflow               137274  2 tdts_udbfw,pktrunner
asmin@RT-AC86U:/tmp/home/root# dmesg | grep tdts
[tdts_shell_ioctl_stat:256] Recv ioctl req with op 2

I followed the thread but couldn't find the resolution. Any suggestion?
 
I had a bit of strangeness on my RT-AX56U yesterday.

In the log file it looks as if Linux was restarted (if I am reading it correctly)
874 lines of what looks like boot information (Virtual kernel memory layout, Remapping interrupts etc)/


Code:
Apr 12 19:39:42 dropbear[8016]: Exit (admin): Exited normally
Apr 12 19:40:02 dropbear[7949]: Exit (admin): Exited normally
Apr 12 19:42:52 wlceventd: wlceventd_proc_event(464): wl0.1: Deauth_ind xx:xx:xx:xx:xx:xx, status: 0, reason: Unspecified reason (1)
Apr 12 19:42:52 hostapd: wl0.1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
May  5 06:05:06 syslogd started: BusyBox v1.25.1
May  5 06:05:06 kernel: klogd started: BusyBox v1.25.1 (2020-04-05 13:37:05 EDT)
May  5 06:05:06 kernel: Booting Linux on physical CPU 0x0
May  5 06:05:06 kernel: Linux version 4.1.52 (merlin@ubuntu-dev) (gcc version 5.5.0 (Buildroot 2017.11.1) ) #2 SMP PREEMPT Sun Apr 5 15:12:07 EDT 2020
May  5 06:05:06 kernel: CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
May  5 06:05:06 kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
May  5 06:05:06 kernel: Machine model: Broadcom BCM947622
May  5 06:05:06 kernel: bootconsole [earlycon0] enabled
....
....
Apr 12 19:47:47 Samba_Server: smb daemon is stopped
Apr 12 19:47:47 ntpd: Initial clock set
Apr 12 19:47:47 avahi-daemon[1385]: Got SIGTERM, quitting.

Any idea what was going on?
 
Pretty vanilla dirty upgrade from 15 to 16. Up 3+ days without issues.
Thanks again for all the hard work.
 
This update is causing client password authentication issues. I have an 86U and use WPA2-Personal. The .15 release had this issue for me too. Keep having to revert back to .14_2 to resolve.

any ideas?
 
did you try forgetting the network on the client devices then re-adding it?
 
did you try forgetting the network on the client devices then re-adding it?
Not on this release. I quickly reverted back. But I’m pretty sure I tried this on .15 without fixing.

I have over 50 devices, owned by multiple people connecting to this router. It’s weird that reverting back to .14_2 fixes it without having to forget and re-add the network.

Thx for the idea. Will keep it in mind.
 
I had a bit of strangeness on my RT-AX56U yesterday.

In the log file it looks as if Linux was restarted (if I am reading it correctly)
874 lines of what looks like boot information (Virtual kernel memory layout, Remapping interrupts etc)/


Code:
Apr 12 19:39:42 dropbear[8016]: Exit (admin): Exited normally
Apr 12 19:40:02 dropbear[7949]: Exit (admin): Exited normally
Apr 12 19:42:52 wlceventd: wlceventd_proc_event(464): wl0.1: Deauth_ind xx:xx:xx:xx:xx:xx, status: 0, reason: Unspecified reason (1)
Apr 12 19:42:52 hostapd: wl0.1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
May  5 06:05:06 syslogd started: BusyBox v1.25.1
May  5 06:05:06 kernel: klogd started: BusyBox v1.25.1 (2020-04-05 13:37:05 EDT)
May  5 06:05:06 kernel: Booting Linux on physical CPU 0x0
May  5 06:05:06 kernel: Linux version 4.1.52 (merlin@ubuntu-dev) (gcc version 5.5.0 (Buildroot 2017.11.1) ) #2 SMP PREEMPT Sun Apr 5 15:12:07 EDT 2020
May  5 06:05:06 kernel: CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
May  5 06:05:06 kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
May  5 06:05:06 kernel: Machine model: Broadcom BCM947622
May  5 06:05:06 kernel: bootconsole [earlycon0] enabled
....
....
Apr 12 19:47:47 Samba_Server: smb daemon is stopped
Apr 12 19:47:47 ntpd: Initial clock set
Apr 12 19:47:47 avahi-daemon[1385]: Got SIGTERM, quitting.

Any idea what was going on?
That's a reboot, whether intentional or not. The clock resets to May 5 since there is no battery backup for the clock. Any power fluctuations last night? Someone vacuuming near the router cord? ;)
 
That's a reboot, whether intentional or not. The clock resets to May 5 since there is no battery backup for the clock. Any power fluctuations last night? Someone vacuuming near the router cord? ;)
No power fluctuations as far as I could tell. All the other equipment in the same power outlet didn't have a problem. I guess I need to check that it is plugged in securely.
 
Apr 12 19:39:42 dropbear[8016]: Exit (admin): Exited normally Apr 12 19:40:02 dropbear[7949]: Exit (admin): Exited normally Apr 12 19:42:52 wlceventd: wlceventd_proc_event(464): wl0.1: Deauth_ind xx:xx:xx:xx:xx:xx, status: 0, reason: Unspecified reason (1) Apr 12 19:42:52 hostapd: wl0.1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated May 5 06:05:06 syslogd started: BusyBox v1.25.1
Were you logged on via SSH (twice) at the times indicated? If you weren't, it may indicate some nefarious activity. Do have have SSH access from WAN enabled?
 
Were you logged on via SSH (twice) at the times indicated? If you weren't, it may indicate some nefarious activity. Do have have SSH access from WAN enabled?
SSH is LAN only. I had Putty and WinSCP open. I also had the router gui open as well.
 
Last edited:
I don't now 100% but does the AC88U only support LACP Layer2 and not Static LAG?

No idea.

I followed the thread but couldn't find the resolution. Any suggestion?

It's debugging output from the Trend Micro engine, it does not indicate a problem. Only Asus's engineers would know what it means. Just ignore it.
 
He won't add it for some reason. Only John's fork has it. It was great!
https://www.snbforums.com/threads/fork-asuswrt-merlin-374-43-lts-releases-v42e7.18914/

I find this as useful as the traffic meter. No offense intended to anyone.

hula girl.gif
 
Dirty upgrade from 384.13 on my RT-AC68U - no issues so far in standard router mode (no need to use it in wireless bridge mode, for which some users have reported random reboots). Thanks Eric for another smooth release!
 
I tried L&LD's firmware flashing method and his Nuclear Reset but I still can't manage to make the QoS work, stock firmware doesn't limit the bandwith either on my RT-AX56U.
Everything else is working properly, it's just the QoS that is giving me some headaches.
 
@axaro1 if the stock firmware and the RMerlin firmware both don't work, then Asus needs to fix it.

Look towards a hopefully near-future firmware changelog that hints at this needed functionality you want.
 
Status
Not open for further replies.

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top