ASUS RT-AC86U firmware release 3.0.0.4.384.45149 12/05/2018

[RMerlin]

After many tests the problem of loss of IPv6 is if some of the devices that are connected to the network have an empty or not allowed hostname, in my case I have a samsung TV UN65JS8500 that has as hostname "localhost" and a tv sony KDL -55W800A that sometimes had an empty hostname

All these years, and Samsung's engineers still haven't fixed that stupid issue?

 

[universe83]

All these years, and Samsung's engineers still haven't fixed that stupid issue?

Yes, I know, I think they'll never fix it.

 

[Gitsum]

Why is it so hard to have a reliable client list?? Do other router manufactures have the same problems? I haven't tried any Linksys stuff in a while.

 

[SwampKracker]

Why is it so hard to have a reliable client list?? Do other router manufactures have the same problems? I haven't tried any Linksys stuff in a while.

What am I missing? Why is the client list so important? Are there features that rely on it?

 

[Gitsum]

What am I missing? Why is the client list so important? Are there features that rely on it?

The "feature" would be that you have a reliable list of all the devices connected to your network. ASUS is horrible at this task. I have a network extender and anything connected to it will not show up on the client list. Yes, you can look at the DHCP list but that does not tell you if they are currently connected or not or the connection status whether it be 2.4 or 5 or LAN.

 

[RMerlin]

The "feature" would be that you have a reliable list of all the devices connected to your network. ASUS is horrible at this task. I have a network extender and anything connected to it will not show up on the client list. Yes, you can look at the DHCP list but that does not tell you if they are currently connected or not or the connection status whether it be 2.4 or 5 or LAN.

The network client mapping relies on ARP to locate clients. If your extender/bridge doesn't pass ARP requests, then the router won't be able to see them.

 

[Gitsum]

The network client mapping relies on ARP to locate clients. If your extender/bridge doesn't pass ARP requests, then the router won't be able to see them.

It's an ASUS RT-N66U. Is that something that can be enabled?

 

[RMerlin]

It's an ASUS RT-N66U. Is that something that can be enabled?

It's not something that is controllable by the end-user, it's a matter of implementation.

 

[heidarren]

The "feature" would be that you have a reliable list of all the devices connected to your network. ASUS is horrible at this task. I have a network extender and anything connected to it will not show up on the client list. Yes, you can look at the DHCP list but that does not tell you if they are currently connected or not or the connection status whether it be 2.4 or 5 or LAN.

I think u need SNMP to see all the clients from network extender, I’m not sure how it works but it’s the solution u need


Sent from my iPhone using Tapatalk

 

[Tonycv51]

How did you spot the Sony empty hostname - was there something in the logs ?

On a separate note I have lots of the below messages with this firmware, though maybe they were there before - they happen every couple of seconds. My settings are default i.e. IPV6 is disabled, but have set QoS to game auto, and enabled AI Protection

Dec 16 12:51:53 kernel: net_ratelimit: 107 callbacks suppressed

 

[universe83]

How did you spot the Sony empty hostname - was there something in the logs ?

System log -> DHCP leases
or
System log -> IPv6

 

[hjzwiers]

Doesn't anyone know what is causing these frequent kernel crashes, several people seem to have the same issue. Usually the system has some kind of internal reset, but the longest logging I have seen for system to be up is 24 hours .....

Dec 8 10:10:48 kernel: pgd = ffffffc009b2c000
Dec 8 10:10:48 kernel: [00000000] *pgd=0000000010dc2003, *pud=0000000010dc2003, *pmd=0000000015763003, *pte=0000000000000000
Dec 8 10:10:48 kernel: CPU: 1 PID: 2713 Comm: dcd Tainted: P O 4.1.27 #2
Dec 8 10:10:48 kernel: Hardware name: Broadcom-v8A (DT)
Dec 8 10:10:48 kernel: task: ffffffc013d4d440 ti: ffffffc00c364000 task.ti: ffffffc00c364000
Dec 8 10:10:48 kernel: PC is at 0xf73f5f44
Dec 8 10:10:48 kernel: LR is at 0x1dc74
Dec 8 10:10:48 kernel: pc : [<00000000f73f5f44>] lr : [<000000000001dc74>] pstate: 600e0010
Dec 8 10:10:48 kernel: sp : 00000000ff90e278
Dec 8 10:10:48 kernel: x12: 000000000009ff10
Dec 8 10:10:48 kernel: x11: 00000000f66ff024 x10: 00000000000a02b4
Dec 8 10:10:48 kernel: x9 : 00000000f66ff990 x8 : 00000000000a076c
Dec 8 10:10:48 kernel: x7 : 00000000f66ff9c0 x6 : 00000000000a0766
Dec 8 10:10:48 kernel: x5 : 0000000000000000 x4 : 00000000f66ff974
Dec 8 10:10:48 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Dec 8 10:10:48 kernel: x1 : 000000000007c674 x0 : 0000000000000000

 

[hjzwiers]

Seems to be happening on all forms of ASUS hardware regardless of stock or Merlin. Must be the TrendMicro 2.100 signature version update.

Any indication that Trend Micro wil fix this?

 

[Pergola Fabio]

Any indication that Trend Micro wil fix this?

So it means older firmwares have the same issue? Didn't upgrade yet to this firmware , but the signature is updated to .100 on my 32799 version

 

[Gingernut]

Doesn't anyone know what is causing these frequent kernel crashes, several people seem to have the same issue. Usually the system has some kind of internal reset, but the longest logging I have seen for system to be up is 24 hours .....

Dec 8 10:10:48 kernel: pgd = ffffffc009b2c000
Dec 8 10:10:48 kernel: [00000000] *pgd=0000000010dc2003, *pud=0000000010dc2003, *pmd=0000000015763003, *pte=0000000000000000
Dec 8 10:10:48 kernel: CPU: 1 PID: 2713 Comm: dcd Tainted: P O 4.1.27 #2
Dec 8 10:10:48 kernel: Hardware name: Broadcom-v8A (DT)
Dec 8 10:10:48 kernel: task: ffffffc013d4d440 ti: ffffffc00c364000 task.ti: ffffffc00c364000
Dec 8 10:10:48 kernel: PC is at 0xf73f5f44
Dec 8 10:10:48 kernel: LR is at 0x1dc74
Dec 8 10:10:48 kernel: pc : [<00000000f73f5f44>] lr : [<000000000001dc74>] pstate: 600e0010
Dec 8 10:10:48 kernel: sp : 00000000ff90e278
Dec 8 10:10:48 kernel: x12: 000000000009ff10
Dec 8 10:10:48 kernel: x11: 00000000f66ff024 x10: 00000000000a02b4
Dec 8 10:10:48 kernel: x9 : 00000000f66ff990 x8 : 00000000000a076c
Dec 8 10:10:48 kernel: x7 : 00000000f66ff9c0 x6 : 00000000000a0766
Dec 8 10:10:48 kernel: x5 : 0000000000000000 x4 : 00000000f66ff974
Dec 8 10:10:48 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Dec 8 10:10:48 kernel: x1 : 000000000007c674 x0 : 0000000000000000

I get them quite frequently:

May  5 07:05:05 kernel: _ Reboot message ... _______________________________________________________
May  5 07:05:05 kernel: dhd_detach(): thread:dhd_watchdog_thread:254 terminated OKkthread_should_stop detected in wfddhd_detach(): thread:dhd_watchdog_thread:24e terminated OKBUG: recent printk recursion!FPM Pool 1: invalid token 0x23fd0000 freedFPM Pool 1: invalid token 0x21808000 freedFPM Pool 1: invalid token 0x23cb0000 freedFPM Pool 1: invalid token 0x20a20000 freedFPM Pool 1: invalid token 0x221f0000 freedFPM Pool 1: invalid token 0x22610000 freedFPM Pool 1: invalid token 0x20d78000 freedFPM Pool
May  5 07:05:05 kernel: FPM Pool 1: invalid token 0x20c78000 freedFPM Pool 1: invalid token 0x23b40000 freedFPM Pool 1: invalid token 0x20010000 freedFPM Pool 1: invalid token 0x212a0000 freedFPM Pool 1: invalid token 0x22ef0000 freedFPM Pool 1: invalid token 0x23598000 freedFPM Pool 1: invalid token 0x23088000 freedFPM Pool 1: invalid token 0x22190000 freedFPM Pool 1: invalid token 0x23748000 freedFPM Pool 1: invalid token 0x23e00000 freedFPM Pool 1: invalid token 0x213d0000 freed

Dec 17 08:03:17 kernel: httpd[7846]: unhandled level 3 translation fault (11) at 0x0042113c, esr 0x92000007
Dec 17 08:03:17 kernel: pgd = ffffffc0131b9000
Dec 17 08:03:17 kernel: [0042113c] *pgd=000000000a3a0003, *pud=000000000a3a0003, *pmd=00000000118a8003, *pte=0000000000000000
Dec 17 08:03:17 kernel: CPU: 1 PID: 7846 Comm: httpd Tainted: P           O    4.1.27 #2
Dec 17 08:03:17 kernel: Hardware name: Broadcom-v8A (DT)
Dec 17 08:03:17 kernel: task: ffffffc01504d440 ti: ffffffc00a360000 task.ti: ffffffc00a360000
Dec 17 08:03:17 kernel: PC is at 0xf70f4aa0
Dec 17 08:03:17 kernel: LR is at 0x26cd8
Dec 17 08:03:17 kernel: pc : [<00000000f70f4aa0>] lr : [<0000000000026cd8>] pstate: 20000010
Dec 17 08:03:17 kernel: sp : 00000000ffa32e18
Dec 17 08:03:17 kernel: x12: 000000000008c71c
Dec 17 08:03:17 kernel: x11: 00000000000791e4 x10: 0000000000000001
Dec 17 08:03:17 kernel: x9 : 0000000000408d68 x8 : 0000000000000000
Dec 17 08:03:17 kernel: x7 : 000000000040eef8 x6 : 00000000004198d0
Dec 17 08:03:17 kernel: x5 : 0000000000421130 x4 : 0000000000421130
Dec 17 08:03:17 kernel: x3 : 00000000ffffffff x2 : 00000000f6fa07a8
Dec 17 08:03:17 kernel: x1 : 0000000000000000 x0 : 0000000000421130

I've had them for months regardless and thought it was due to a failing connected hard drive, which I replaced, but still get them.

Could it possibly be caused by using Entware/Transmission?

 

[OzarkEdge]

Dec 17 08:19:13 kernel: pgd = ffffffc01253e000
Dec 17 08:19:13 kernel: [00000000] *pgd=00000000145fe003, *pud=00000000145fe003, *pmd=000000001579b003, *pte=0000000000000000
Dec 17 08:19:13 kernel: CPU: 1 PID: 14380 Comm: dcd Tainted: P           O    4.1.27 #2
Dec 17 08:19:13 kernel: Hardware name: Broadcom-v8A (DT)
Dec 17 08:19:13 kernel: task: ffffffc01e022180 ti: ffffffc01260c000 task.ti: ffffffc01260c000
Dec 17 08:19:13 kernel: PC is at 0xf754bf44
Dec 17 08:19:13 kernel: LR is at 0x1dc74
Dec 17 08:19:13 kernel: pc : [<00000000f754bf44>] lr : [<000000000001dc74>] pstate: 600e0010
Dec 17 08:19:13 kernel: sp : 00000000ffb0e978
Dec 17 08:19:13 kernel: x12: 000000000009ff10 
Dec 17 08:19:13 kernel: x11: 00000000f67ff024 x10: 00000000000a02b4 
Dec 17 08:19:13 kernel: x9 : 00000000f67ffa94 x8 : 00000000000a076c 
Dec 17 08:19:13 kernel: x7 : 00000000f67ffacc x6 : 00000000000a0766 
Dec 17 08:19:13 kernel: x5 : 0000000000000000 x4 : 00000000f67ffa78 
Dec 17 08:19:13 kernel: x3 : 0000000000000000 x2 : 0000000000000000 
Dec 17 08:19:13 kernel: x1 : 000000000007c674 x0 : 0000000000000000

My AiMesh 86U 45149 has many of the above entries (or similar). Doesn't seem to affect the uptime or anything.

OE

 

[universe83]

My RT-AC86U restarted unexpectedly last night, I also have problems with IPv6.
I am considering returning it to amazon and keep the RT-AC66U_B1 that works without problems.

 

[CriticJay]

Any indication that Trend Micro wil fix this?

I'm waiting for Trend Micro / ASUS to fix this issue, before I re-enable Adaptive QoS on my 86U / 45149.

Just to be clear, my 86U / 45149 currently has all Trend Micro services disabled (i.e. it hasn't prompted me with the "give your consent to Trend Micro" screen), and I do NOT get any kernel crashes for the Comm: dcd module.

I feel that the Comm: dcd module crashes caused my IPv6 to malfunction therefore I'll be leaving Trend Micro services disabled, until people on this forum confirm that the Comm: dcd crashes no longer occur.

 

[OzarkEdge]

I'm waiting for Trend Micro / ASUS to fix this issue, before I re-enable Adaptive QoS on my 86U / 45149.

Just to be clear, my 86U / 45149 currently has all Trend Micro services disabled (i.e. it hasn't prompted me with the "give your consent to Trend Micro" screen), and I do NOT get any kernel crashes for the Comm: dcd module.

I feel that the Comm: dcd module crashes caused my IPv6 to malfunction therefore I'll be leaving Trend Micro services disabled, until people on this forum confirm that the Comm: dcd crashes no longer occur.

I had AiProtection enabled. So I went to Administration\Privacy and withdrew to turn it OFF. This logged:

Dec 17 11:04:24 rc_service: httpd 2327:notify_rc restart_wrs;restart_qos;restart_firewall
Dec 17 11:04:26 kernel:  *** ERROR: [udb_shell_mod_exit:661] Udb static = 0, dynamic = 48
Dec 17 11:04:27 A.QoS: set_qos_off, ret=65280
Dec 17 11:04:27 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)

I'll report back if the Comm: dcd entries return.

Edit: Not seeing the Comm: dcd entries anymore... would have seen them by now.

OE

 

[Jedi2155]

Any gamers trying to use this firmware with AIMesh? It's most noticeable when you drop out in games. It's not as bad as previous versions where the drop out results in 3-8 minutes of no wifi. In the latest iteration, the drop appears to be more in the 5-20s range (which is still terrible for online games but less noticeable in streaming environments with buffering).

I have a desktop PC directly connected to the AiMesh Node, and when the signal goes out, I'm unable to access to the main router page (easiest sign that it was a router issue).