RT-AX88U Pro every one or two days is blocked.

[atorcha]

I have an AiMesh with an RT-AC86U as node and RT-AX88U Pro as a main router.

I use VPN wireguard. and I have a NAS with UNRAID to my media files and server for home purpose.

Every one or two days I have witch off RT-AX88U Pro because I lost connection with internet. Now I am out of my house and my wife has to do it manually.

I dont Understand why it happend.

 

[Digilog]

I swear sometimes I think they get interns to program and no one checks their work.
In the error message, it looks like it is going into a sleep state. which is a kernel misconfiguration.
I would try flashing the firmware to the latest, as I would think someone would have caught this mistake by now.
I can't believe they didn't even bother writing the error traps so even settings not configured throw an error in the logs.

 

[atorcha]

It has the last Marlin firmware...

 

[Listedguru2]

I swear sometimes I think they get interns to program and no one checks their work.
In the error message, it looks like it is going into a sleep state. which is a kernel misconfiguration.
I would try flashing the firmware to the latest, as I would think someone would have caught this mistake by now.
I can't believe they didn't even bother writing the error traps so even settings not configured throw an error in the logs.

I am going to be buying a new Asus router soon and the AX88U Pro is at the top of my list. Is this issue something I should be worried about or does it have something to do with using the Aimesh features?

 

[Tech9]

Is this issue something I should be worried about

Since you are buying this new Asus router for quite some time and worry about things in advance - yes, you can start worrying about this issue too. It may potentially happen to you along with other unexpected things around it... where did positivity go in your life? People come here with issues and ask questions. This doesn't mean every RT-AX88U Pro user goes through hell with this device. There are thousands out there...

 

[Digilog]

I am going to be buying a new Asus router soon and the AX88U Pro is at the top of my list. Is this issue something I should be worried about or does it have something to do with using the Aimesh features?

I can't remember if it was this forum or an OS development one, but we had a discussion of BSD kernel bugs that were out there in the wild and how sleep mode is configured for ACPI instead of generic always on parameters, and embedded equipment OEMs compiled with this turned on and are now having intermittent power state issues. Because they didn't look how the kernel profile was set before compiling. Good news is there a kernel configuration file that can be altered.

 

[ColinTaylor]

I dont Understand why it happend.

Neither do we because your log file contains no useful information since the change you made to the router's logging on October 21st. But it has nothing to do with sleep states or kernel configuration .

I suggest you change "Log only messages more urgent than" on the System Log - General Log page to "all" and then we might be able to see some actual error messages when the problem next occurs.

 

[Digilog]

Look in /boot/loader.conf

the code should have:

hw.pci.enable_msix: 0
hw.pci.enable_msi: 1

if not set like this, change this as this is your fix for the OS.

 

[ColinTaylor]

Look in /boot/loader.conf

This file doesn't exist on his router. It is an embedded device not a BSD distro. Please stop making irrelevant comments about a device you obviously know nothing about.

 

[Digilog]

This file doesn't exist on his router. It is an embedded device not a BSD distro. Please stop making irrelevant comments about a device you obviously know nothing about.

There are other places where those parameters can be passed. I'll download thier firmware and probably use binwalk or something like that to look at it.
Because its obvious to me this junk router has an incorrect OS settings and I can additionally tell you what else is wrong with it.

 

[Tech9]

It's obvious to me you have no idea what are you talking about in this specific case.

 

[Digilog]

It's obvious to me you have no idea what are you talking about in this specific case.

Well, let's review the log:

Completed , but ran into errors:
Oct 21 19:25:46 kernel: ^[[0;33;40mRunner DHD Offload initialization complete^[[0m
Could not find configuration even though parameter is set:
Oct 21 19:25:46 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_inet6addr_event,148: Could not rdpa_system_ipv6_host_address_table_find ret=-5^[[0m
Virtial interface went to sleep and woke up in passive monitor mode. Should have never went to sleep.
Oct 21 19:25:46 kernel: br0: port 1(eth1) entered disabled state
Oct 21 19:25:46 kernel: device eth1 entered promiscuous mode
Wake on lan is enabled in OS, but hardware does not have or support such mode.
Oct 21 19:25:46 kernel: CFG80211-ERROR) wl_allocate_wowl_config :
Oct 21 19:25:46 kernel: Wowl not supported (-23)

The rest of the errors are cause from above in the log I do believe.
So there are issue here with the OS part of their firmware.

 

[Tech9]

Again - this is an embedded device running custom OS, not Linux or BSD distro. It runs on stripped down older kernel with only what the device needs. The firmware is the OS and fits in 70MB size along with ton of extra modules and bloatware. Troubleshooting is device specific.

 

[Digilog]

Again - this is an embedded device running custom OS, not Linux or BSD distro. It runs on stripped down older kernel with only what the device needs. The firmware is the OS and fits in 70MB size along with ton of extra modules and bloatware. Troubleshooting is device specific.

They don't run like a distro like what is on a hard drive installation. But its definitely a BSD kernel of some kind due to the format of the error messages.

 

[ColinTaylor]

Well, let's review the log:

Completed , but ran into errors:
Oct 21 19:25:46 kernel: ^[[0;33;40mRunner DHD Offload initialization complete^[[0m
Could not find configuration even though parameter is set:
Oct 21 19:25:46 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_inet6addr_event,148: Could not rdpa_system_ipv6_host_address_table_find ret=-5^[[0m
Virtial interface went to sleep and woke up in passive monitor mode. Should have never went to sleep.
Oct 21 19:25:46 kernel: br0: port 1(eth1) entered disabled state
Oct 21 19:25:46 kernel: device eth1 entered promiscuous mode
Wake on lan is enabled in OS, but hardware does not have or support such mode.
Oct 21 19:25:46 kernel: CFG80211-ERROR) wl_allocate_wowl_config :
Oct 21 19:25:46 kernel: Wowl not supported (-23)

The rest of the errors are cause from above in the log I do believe.
So there are issue here with the OS part of their firmware.

Those are normal startup messages and not the cause of any "errors". But again, you would know that if you were familiar with these devices.

They don't run like a distro like what is on a hard drive installation. But its definitely a BSD kernel of some kind due to the format of the error messages.

This has nothing to do with BSD. Asuswrt is based on Linux.

 

[Digilog]

This has nothing to do with BSD. Asuswrt is based on Linux.

regardless of OS, you don't run power management on a router. That is going to put network connections to sleep and they don't wake up on lan. Because that function is not supported. They supposed to be always on. There is only small differences between the two Os systems to begin with, because BSD was derived from Linux.

My /var/log/ files are different. That is what threw me off to believe it was BSD.

Also, I find it odd and uncommon that they turn on promiscuous mode on a router. Because its not needed for any firewall packet inspection program.

 

[ColinTaylor]

regardless of OS, you don't run power management on a router. That is going to put network connections to sleep. They supposed to be always on.

You don't understand the messages you're looking at, they're nothing to do with power management. This conversation is irrelevant to the issue the OP has.

 

[Digilog]

You don't understand the messages you're looking at, they're nothing to do with power management. This conversation is irrelevant to the issue the OP has.

Do you work for Asus? Because you are determined to defend their misconfigured OS.

Since most of the issues are from WOL, turn it off by logging into a root console, and type:

ethtool -s <interface_name> wol d

Of course you can get the names of your interfaces by:

ip link show

If you don't know the names for them.

 

[ColinTaylor]

Do you work for Asus? Because you are determined to defend their misconfigured OS.

No I don't work for Asus and I'm not defending anything. But if you continue to post factually incorrect or irrelevant statements you should expect to be corrected.

Since most of the issues are from WOL,

No they're not.

 

[Tech9]

This AiMesh setup most likely has some issues around the node. Most of the log messages are node MAC address related. Second RT-AC86U router runs on a different base firmware and is known for above average failure rate. I would remove the node first and observe the logs and behavior, eventually reset and reconfigure the main router to stabilize it, experiment adding the node back later.