asd is an Asus service, not a TrendMicro service.Makes perfect sense considering everything that is known about TM issues on BE routers.
As your second crash, it's the networkmap service that crashed.
asd is an Asus service, not a TrendMicro service.Makes perfect sense considering everything that is known about TM issues on BE routers.
HW ver 5.1Sorry that's still an issue. Documentation suggests that latest firmware resolves issues on the 2.4ghz band mostly. What HW version are you using?
I have 2, which ran fine for ~4 years.Many folks around don’t have old RT-AC86U routers because many of them died young.
[SIZE=4]dcd[/SIZE] (something to to with the Trend Micro part?) keeps crashing on the parent nodebut it doesn't seem to cause any issue.Apr 5 12:00:25 kernel: potentially unexpected fatal signal 11.
Apr 5 12:00:25 kernel: ===DDD===
Apr 5 12:00:25 kernel: 00010000 - 00092000, [dcd]
Apr 5 12:00:25 kernel: f6cd0000 - f6cd9000, [libnss_files.so.2]
Apr 5 12:00:25 kernel: f75f5000 - f7725000, [libc.so.6]
[SIZE=4]asd[/SIZE] has (just once) done that same thing on the secondary RT-AC86U.You could disable it, but clients on the 5 GHz and especially 6 GHz band should be able to deal just fine with Wifi 7 support being enabled, as these clients will have a fairly modern networking stack. It's largely stuff that deals with the 2.4 GHz band that might have issues with any modern feature.I have a question, since MLO is really no good, i don't have anything Wifi 7...so it network settings i have the 3 bands, click on 1 and it says Wifi 7 Mode and it's enabled, anything happen if i should disable it since i don't use MLO?
You could create a 2.4ghz SSID only band and turn off wifi 7 on that directly. That way you wouldn't have any issues with the 2.4ghz at all.Thank-You very much!
drive.google.com
drive.google.com
Is this including for backhaul?MLO seems to be a can of worms so far, regardless of the router model. Since so far that technology seem to underdeliver on its initial promises, I recommend just keeping it disabled. It's probably one of those features that would be nice if all clients played nicely with it. I suspect many older clients won't.
I'm considering asking Asus for some sort of credit towards a better more reliable unit. I think the RT-BE96U seems to not have these sorts of issues but it's also 2x the price and frankly I don't think I would benefit from it's extra features, if we assume reliability is not an extra feature lol.Hi all,
I recently purchased a RT-BE92U and am experiencing some of the crashing issues discussed on the forum. The hardware revision is 1.
When I received the router, I did the following:
1. Updated to latest stock firmware.
2. Flashed latest Merlin.
3. Perform factory reset.
4. Setup as normal, with some different configuration such as primary network and a 2.4Ghz only Guest network for IoT devices.
5. I do have multiple aimesh routers that are connected wirelessly.
What I am experiencing is basically a disconnect from the router, I pulled the logs after a turn off/on, and it appears the router was stull running. I have tried different setting such as disabling MLO, enabling MLO, disable WPS, etc. with no luck.
Linked below is the log and cfg file from the router on my Google Drive. Please let me know if there is a better way to provide this to you.
I am considering returning it and either getting a different model or hoping to get a newer hardware revision, but I have not saw much evidence a newer hardware revision will fix much.
I put the system log through Gemini and it found some things but I am not sure what it means.
![]()
Config:
Settings_RT-BE92U 07-APR-2026.CFG
drive.google.com
Log:
syslog RT-BE92U 07-APR-2026.txt
drive.google.com
MLO in general appear problematic.Is this including for backhaul?
They should pull them from the shelves, honestly.I'm considering asking Asus for some sort of credit towards a better more reliable unit. I think the RT-BE96U seems to not have these sorts of issues but it's also 2x the price and frankly I don't think I would benefit from it's extra features, if we assume reliability is not an extra feature lol.
I do apologize for not reading the the full initial post.Hi all,
I recently purchased a RT-BE92U and am experiencing some of the crashing issues discussed on the forum. The hardware revision is 1.
When I received the router, I did the following:
1. Updated to latest stock firmware.
2. Flashed latest Merlin.
3. Perform factory reset.
4. Setup as normal, with some different configuration such as primary network and a 2.4Ghz only Guest network for IoT devices.
5. I do have multiple aimesh routers that are connected wirelessly.
What I am experiencing is basically a disconnect from the router, I pulled the logs after a turn off/on, and it appears the router was stull running. I have tried different setting such as disabling MLO, enabling MLO, disable WPS, etc. with no luck.
Linked below is the log and cfg file from the router on my Google Drive. Please let me know if there is a better way to provide this to you.
I am considering returning it and either getting a different model or hoping to get a newer hardware revision, but I have not saw much evidence a newer hardware revision will fix much.
I put the system log through Gemini and it found some things but I am not sure what it means.
![]()
Config:
Settings_RT-BE92U 07-APR-2026.CFG
drive.google.com
Log:
syslog RT-BE92U 07-APR-2026.txt
drive.google.com
We use essential cookies to make this site work, and optional cookies to enhance your experience.