Be careful with ASUS routers

Make sure to check out the Gamers Nexus video: • ASUS Scammed Us
Gamers Nexus presents their first-hand experience when dealing with ASUS devices that need to be repaired under warranty. It's not pretty. And since I am testing quite a few ASUS routers, I thought I may share with you my two cents.
Visuals made using musicvid.org
Info about the warranty label: www.ftc.gov/ne...
Where to report fraudulent behavior: reportfraud.ft...

[@jtz2268]

I don't know if this is relevant to the video but its in regards to the Asus warranty for my RT AX3000. When I sent one for service, one of the repair centres needed the approval from ASUS from a different branch inorder to give me a replacement. For a long time I have not gotten any updates from both ASUS and the seller whom I bought the router from until one person from ASUS contacted me and finally gave me the update in the situation. The representative said that the product I have is out of warranty because the serial number of the product was out of production but luckily he said that I can contact the seller to get his approval for the replacement. After several days of waiting I finally got the replacement but this one is the V2 with the quad core and not the one based on the tri core...which is weird because the quad core is nowhere available even in Amazon. Now I have to get this replacement updated for the warranty period...that is creating problems.

[@SamBondor]

Of course it's relevant. I do test wireless routers, but the support and warranty aspect is very difficult to check, which is why your experience is very much valuable.

[@randomgamingin144p]

my asus rt-ax53u is working for the time being (i mean i got it like a month ago so i wouldnt expect it to break THAT early)

[@Marauder-q2v]

I just use my ISP provided router and then use MOCA for anything that requires a high data throughput. This setup has been pretty stable. I can hit around 100-200 mbps on WiFi. Which is more than enough for mobile devices. Bonus, the ISP router doesn’t look gimmicky AF. Also helps that wifi 6 pretty much is meaningless in my use case. 6E is really expensive, so wifi 5 has aged quite well.

[@tratzum]

I have a RT-AX86U router. It is about 6 months old. One of the Ethernet ports does not work. Rather then have to deal with an RMA from ASUS I just bought a simple network switch. ASUS RMA process IS designed to suck the life and money out of you. ASUS is no longer the brand of the people. They got lazy and bloated and forgot their roots.

[@ChaosTheory666]

Oh, right. I have an Asus router that has Asuswrt-Merlin on it which hasn't been in use for a few months. Was thinking of finding a use for it, but I should get rid of it since it's Asus.

[@SamBondor]

If you can sell it, then that's up to you. But you can also just set it as an access point (or as a mesh node) to add WiFi somewhere that's hard to reach. Don't throw it away if it works, there's enough junk in the ground already..

[@fu1r4]

For many years ago D-LINK sold routers with 11 years warranty and i manage to get a new router on warranty after 8 years when mine stopped working. 🙂 I do not recommend buying D-LINK. It is garbage!

[@bFix]

the software? yes but with openwrt these run fine

[@benc-uw9jg]

D link is the worst. I have the covr mesh 1873. It works but the software is bare bones. There's never been a update for it. I got a Asus ROG ax6000 coming in the mail. That should be way better I see they update there router software with patches.

[@bFix]

yeah, with openwrt the COVR-X1860 run like a charm. (X1863 is just the name, if you buy a bundle of 3 of these)

[@benc-uw9jg]

I think asus moght be the best router company. And google 2nd probably. Due to software updates.

[@benc-uw9jg]

Asus being first for more customisation and google 2nd as there's no customisation but there software crew works across like multiple devices platforms.

[@NutkeyDoesMinecraft]

Im pretty sure my ASUS router is hacked by the chinese... I can't ping devices inside my own network. Im going to be replacing it in the near future with unifi equipment.

[@examen1996]

Search for openwrt or merlin asus , alternative firmware that will clean any potential "hack"

[@skatcat743]

bro how

[@vadnegru]

Disable isolation

[@Triro]

Probably network isolation. Its a security feature to prevent devices and malware from spreading across the network, but its also frustrating. If you're going with a new router, I highly recommend getting a open sourced GL-INET roter, been using one for about 5 months now, and absolutely love it. Its privacy friendly, and easy to use with their user interface. Oh yeah, and you're not just blindly trusting the security of a closed sourced firmware. as they are based off of a well established, and secure, opensourced firmware named OpenWRT.

[@SamBondor]

I don't know if you did anything specific before you got this behavior from the router, but I am willing to bet it's more likely a configuration issue than hacking. As other people said, check out the client isolation or just reset the router and start with a fresh slate.

[@zahirkhan778]

A sus sux

[@annettesurfer]

Something keeps changing the time in the traffic analyzer web history of my Asus GT-AXE 16000 and the system log seems to indicate firmware checks even though it's set to off. It seems I have to do a factory restore weekly to reset it to the correct time and sometimes it'll last a day or two before being altered. I suspect my teen is tinkering from his PC but I always select the strongest password possible just in case, plus I keep everything in a locked room so he doesn't have physical access. He's always hacking his consoles so I wouldn't put it past him. I could use some help. Here's the recent log: May 17 22:04:58 rc_service: httpd 2839:notify_rc restart_logger May 17 22:04:58 kernel: klogd started: BusyBox v1.24.1 (2023-12-06 15:21:33 CST) May 17 22:11:24 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN. May 17 22:11:24 kernel: ^[[0;34m[NTC xport] xport_reset: rc = 0; intf = 3 port = 2 spd = 2.5G dup = 1 May 17 22:11:24 kernel: ^[[0m May 17 22:11:26 kernel: ^[[0;34m[NTC xport] xport_init: rc = 0; intf = 3 port = 2 spd = 100M dup = 1 May 17 22:11:26 kernel: ^[[0m May 17 22:11:26 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 100 mbps full duplex May 17 22:27:46 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 17 22:58:38 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 17 23:29:27 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 00:00:08 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 00:30:38 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 01:01:06 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 01:31:47 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 02:02:17 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 02:32:46 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 03:02:07 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7954)]do webs_update May 18 03:02:16 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7972)]retrieve firmware information May 18 03:02:16 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7987)]fimrware update check first time May 18 03:02:16 WATCHDOG: [FAUPGRADE][auto_firmware_check:(8018)]no need to upgrade firmware May 18 03:02:46 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7954)]do webs_update May 18 03:02:46 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7972)]retrieve firmware information May 18 03:02:46 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7992)]fimrware update check once May 18 03:03:16 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7954)]do webs_update May 18 03:03:16 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7972)]retrieve firmware information May 18 03:03:16 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7992)]fimrware update check once May 18 03:03:27 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 03:03:46 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7954)]do webs_update May 18 03:03:46 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7972)]retrieve firmware information May 18 03:03:46 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7987)]fimrware update check first time May 18 03:03:46 WATCHDOG: [FAUPGRADE][auto_firmware_check:(8018)]no need to upgrade firmware May 18 03:33:58 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 04:04:47 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 04:07:57 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN. May 18 04:07:57 kernel: ^[[0;34m[NTC xport] xport_reset: rc = 0; intf = 3 port = 2 spd = 100M dup = 1 May 18 04:07:57 kernel: ^[[0m May 18 04:08:02 kernel: ^[[0;34m[NTC xport] xport_init: rc = 0; intf = 3 port = 2 spd = 2.5G dup = 1 May 18 04:08:02 kernel: ^[[0m May 18 04:08:02 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 2500 mbps full duplex May 18 04:08:10 wlceventd: wlceventd_proc_event(685): eth8: Auth 58:96:1D:58:91:9D, status: Successful (0), rssi:0 May 18 04:08:10 wlceventd: wlceventd_proc_event(722): eth8: Assoc 58:96:1D:58:91:9D, status: Successful (0), rssi:-68 May 18 04:10:53 wlceventd: wlceventd_proc_event(645): eth8: Deauth_ind 58:96:1D:58:91:9D, status: 0, reason: Disassociated due to inactivity (4), rssi:-68 May 18 04:18:02 wlceventd: wlceventd_proc_event(685): eth8: Auth 9C:25:95:67:A0:D1, status: Successful (0), rssi:-62 May 18 04:18:02 wlceventd: wlceventd_proc_event(722): eth8: Assoc 9C:25:95:67:A0:D1, status: Successful (0), rssi:-62 May 18 04:29:37 wlceventd: wlceventd_proc_event(685): eth10: Auth 34:94:54:8B:B0:70, status: Successful (0), rssi:0 May 18 04:29:37 wlceventd: wlceventd_proc_event(722): eth10: Assoc 34:94:54:8B:B0:70, status: Successful (0), rssi:-58 May 18 04:30:31 wlceventd: wlceventd_proc_event(645): eth10: Deauth_ind 34:94:54:8B:B0:70, status: 0, reason: Disassociated due to inactivity (4), rssi:-59 May 18 04:35:36 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 05:06:17 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 05:57:18 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 06:27:47 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 06:58:17 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 07:02:22 wlceventd: wlceventd_proc_event(685): eth7: Auth 5E:A1:02:B1:BF:3C, status: Successful (0), rssi:-54 May 18 07:02:22 wlceventd: wlceventd_proc_event(722): eth7: Assoc 5E:A1:02:B1:BF:3C, status: Successful (0), rssi:-54 May 18 07:28:58 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 07:59:28 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 08:29:56 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 09:00:40 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 09:31:32 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER

[@SamBondor]

I will give you my quick two cents and I will look into it a bit more in depth later. The routers seems to be checking regularly for the firmware, but that doesn't mean it will take any action if you have this function disabled. Has it ever updated automatically despite being set to off? That ACS_CSTIMER thing is usually related to the the channel if it's set to auto. The router will regularly check and change it depending on what it detects in the vicinity. You could just manually set a channel and the router should stop doing that. As for the time change, I am not sure yet, but I don't think your teen has anything to do with it. Is it possible to revert to a previous firmware or just use Merlin and see if the issue persists?

[@annettesurfer]

​@@SamBondor Thanks for the reply. I tried to reply but it looks like it didn't make it. I manually checked for an update a few weeks back and allowed it to continue but this issue has existed since I bought it last July of 23, and even in the previous router, an Asus GT-AX11000. While I was away today, the time changed again. The System log: May 18 07:28:58 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 11:14:09 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 11:22:36 wlceventd: wlceventd_proc_event(662): eth7: Disassoc 5E:A1:02:B1:BF:3C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0 May 18 11:22:36 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind 5E:A1:02:B1:BF:3C, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0 May 18 11:49:29 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN. May 18 11:49:29 kernel: ^[[0;34m[NTC xport] xport_reset: rc = 0; intf = 3 port = 2 spd = 2.5G dup = 1 May 18 11:49:29 kernel: ^[[0m May 18 11:49:32 kernel: ^[[0;34m[NTC xport] xport_init: rc = 0; intf = 3 port = 2 spd = 100M dup = 1 May 18 11:49:32 kernel: ^[[0m May 18 11:49:32 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 100 mbps full duplex May 18 12:21:46 wlceventd: wlceventd_proc_event(685): eth10: Auth D4:FB:8E:69:1F:A6, status: Successful (0), rssi:0 May 18 12:21:46 wlceventd: wlceventd_proc_event(722): eth10: Assoc D4:FB:8E:69:1F:A6, status: Successful (0), rssi:-54 May 18 12:25:53 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 12:37:09 acsd: acs_set_chspec: 0x1002 (2) for reason ACS_CSTIMER May 18 12:43:11 wlceventd: wlceventd_proc_event(685): eth10: Auth 34:94:54:8B:B0:70, status: Successful (0), rssi:-64 May 18 12:43:11 wlceventd: wlceventd_proc_event(722): eth10: Assoc 34:94:54:8B:B0:70, status: Successful (0), rssi:-64 May 18 12:44:16 wlceventd: wlceventd_proc_event(645): eth10: Deauth_ind 34:94:54:8B:B0:70, status: 0, reason: Disassociated due to inactivity (4), rssi:-59 May 18 12:57:50 wlceventd: wlceventd_proc_event(662): eth10: Disassoc D4:FB:8E:69:1F:A6, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0 May 18 12:57:50 wlceventd: wlceventd_proc_event(645): eth10: Deauth_ind D4:FB:8E:69:1F:A6, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0 May 18 13:02:15 wlceventd: wlceventd_proc_event(685): eth9: Auth 08:9D:F4:38:90:BE, status: Successful (0), rssi:0 May 18 13:02:15 wlceventd: wlceventd_proc_event(645): eth9: Deauth_ind 08:9D:F4:38:90:BE, status: 0, reason: Previous authentication no longer valid (2), rssi:-62 May 18 13:02:15 wlceventd: wlceventd_proc_event(645): eth9: Deauth_ind 08:9D:F4:38:90:BE, status: 0, reason: Unspecified reason (1), rssi:0 May 18 13:02:15 wlceventd: wlceventd_proc_event(695): eth9: ReAssoc 08:9D:F4:38:90:BE, status: Successful (0), rssi:-62 May 18 13:02:27 wlceventd: wlceventd_proc_event(645): eth9: Deauth_ind 08:9D:F4:38:90:BE, status: 0, reason: Unspecified reason (1), rssi:0 May 18 13:02:27 wlceventd: wlceventd_proc_event(662): eth9: Disassoc 08:9D:F4:38:90:BE, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0 May 18 13:02:27 wlceventd: wlceventd_proc_event(685): eth9: Auth 08:9D:F4:38:90:BE, status: Successful (0), rssi:0 May 18 13:02:27 wlceventd: wlceventd_proc_event(695): eth9: ReAssoc 08:9D:F4:38:90:BE, status: Successful (0), rssi:-63 May 18 13:13:24 kernel: sched: RT throttling activated May 18 13:13:24 kernel: NOHZ: local_softirq_pending 24a May 18 14:08:49 wlceventd: wlceventd_proc_event(645): eth9: Deauth_ind 08:9D:F4:38:90:BE, status: 0, reason: Unspecified reason (1), rssi:0 May 18 14:08:49 wlceventd: wlceventd_proc_event(662): eth9: Disassoc 08:9D:F4:38:90:BE, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0 May 18 14:10:58 wlceventd: wlceventd_proc_event(685): eth10: Auth FA:05:BE:56:37:56, status: Successful (0), rssi:-77 May 18 14:10:58 wlceventd: wlceventd_proc_event(645): eth10: Deauth_ind FA:05:BE:56:37:56, status: 0, reason: Unspecified reason (1), rssi:-77 May 18 14:10:58 wlceventd: wlceventd_proc_event(685): eth10: Auth FA:05:BE:56:37:56, status: Successful (0), rssi:-77 May 18 14:10:58 wlceventd: wlceventd_proc_event(722): eth10: Assoc FA:05:BE:56:37:56, status: Successful (0), rssi:-77 May 18 14:10:58 wlceventd: wlceventd_proc_event(722): eth10: Assoc FA:05:BE:56:37:56, status: Successful (0), rssi:-77 May 18 14:36:52 roamast: sta[FA:05:BE:56:37:56] on ap[A0:36:BC:62:F9:C4], rcpi is 80 and rssi is -70 May 18 14:40:14 roamast: sta[FA:05:BE:56:37:56] on ap[A0:36:BC:62:F9:C4], rcpi is 76 and rssi is -72 May 18 14:40:23 wlceventd: wlceventd_proc_event(662): eth10: Disassoc FA:05:BE:56:37:56, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0 May 18 14:40:23 wlceventd: wlceventd_proc_event(645): eth10: Deauth_ind FA:05:BE:56:37:56, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0 May 18 14:40:23 roamast: sta[FA:05:BE:56:37:56] on ap[A0:36:BC:62:F9:C4], rcpi is 68 and rssi is -76 May 18 14:40:23 roamast: sta[FA:05:BE:56:37:56] on ap[A0:36:BC:62:F9:C4], rcpi is 68 and rssi is -76 May 18 14:42:04 wlceventd: wlceventd_proc_event(645): eth8: Deauth_ind 9C:25:95:67:A0:D1, status: 0, reason: Disassociated due to inactivity (4), rssi:-91 May 18 14:50:18 acsd: acs_set_chspec: 0x1904 (6u) for reason ACS_CSTIMER May 18 15:40:50 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 15:57:51 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN. May 18 15:57:51 kernel: ^[[0;34m[NTC xport] xport_reset: rc = 0; intf = 3 port = 2 spd = 100M dup = 1 May 18 15:57:51 kernel: ^[[0m May 18 15:57:55 kernel: ^[[0;34m[NTC xport] xport_init: rc = 0; intf = 3 port = 2 spd = 2.5G dup = 1 May 18 15:57:55 kernel: ^[[0m May 18 15:57:55 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 2500 mbps full duplex May 18 15:58:03 wlceventd: wlceventd_proc_event(685): eth8: Auth 58:96:1D:58:91:9D, status: Successful (0), rssi:-70 May 18 15:58:03 wlceventd: wlceventd_proc_event(722): eth8: Assoc 58:96:1D:58:91:9D, status: Successful (0), rssi:-70 May 18 15:58:03 wlceventd: wlceventd_proc_event(645): eth8: Deauth_ind 58:96:1D:58:91:9D, status: 0, reason: Unspecified reason (1), rssi:0 May 18 15:58:03 wlceventd: wlceventd_proc_event(662): eth8: Disassoc 58:96:1D:58:91:9D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0 May 18 16:09:28 wlceventd: wlceventd_proc_event(685): eth7: Auth 18:48:CA:06:67:03, status: Successful (0), rssi:-59 May 18 16:09:28 wlceventd: wlceventd_proc_event(722): eth7: Assoc 18:48:CA:06:67:03, status: Successful (0), rssi:-59 May 18 16:10:44 roamast: sta[18:48:CA:06:67:03] on ap[A0:36:BC:62:F9:C8], rcpi is 112 and rssi is -54 May 18 16:10:44 roamast: sta[18:48:CA:06:67:03] on ap[A0:36:BC:62:F9:C8], rcpi is 112 and rssi is -54 May 18 16:11:43 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER May 18 16:12:54 roamast: sta[18:48:CA:06:67:03] on ap[A0:36:BC:62:F9:C8], rcpi is 106 and rssi is -57 May 18 16:31:34 wlceventd: wlceventd_proc_event(662): eth7: Disassoc 18:48:CA:06:67:03, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0 May 18 16:31:34 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind 18:48:CA:06:67:03, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0 May 18 16:42:28 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER Shortened because: We weren't able to add your reply. Please try again.

[@annettesurfer]

I think the issue is with the Trend Micro section that provides the AiProtection and Traffic Analyzer with their Web History, Bandwidth Monitor, Traffic Monitor, and Web History. To reset the time, I clear the traffic analyzer, then turn it off (applying settings) turn off the bandwidth monitor (applying settings), turn off the statistic (applying settings) turn off AiProtection (applying settings) then I clear the log and I do a policy withdrawal under administration. To restart to the correct time I turn AiProtection back on (agree to the privacy policy) (applying settings) And then turn on everything under the Traffic Analyzer settings such as Statistic/Bandwidth monitor/Web History. System log after applying: May 18 16:53:20 rc_service: httpd 2839:notify_rc restart_logger May 18 16:53:20 kernel: klogd started: BusyBox v1.24.1 (2023-12-06 15:21:33 CST) May 18 16:53:32 rc_service: httpd 2839:notify_rc clean_web_history May 18 16:53:36 rc_service: httpd 2839:notify_rc restart_qos;restart_firewall May 18 16:53:39 BWDPI: fun bitmap = 43f May 18 16:54:16 rc_service: httpd 2839:notify_rc restart_qos;restart_firewall May 18 16:54:19 BWDPI: fun bitmap = 43f May 18 16:54:31 rc_service: httpd 2839:notify_rc restart_wrs;restart_firewall May 18 16:54:34 BWDPI: fun bitmap = 43f May 18 16:54:43 rc_service: httpd 2839:notify_rc restart_wrs;restart_firewall May 18 16:54:44 BWDPI: force to flush flowcache entries May 18 16:54:44 kernel: udb_core lock_num = 23 May 18 16:54:44 BWDPI: rollback fc May 18 16:55:04 rc_service: httpd 2839:notify_rc restart_wrs;restart_qos;restart_firewall May 18 17:00:14 rc_service: httpd 2839:notify_rc restart_wrs;restart_firewall May 18 17:00:16 kernel: SHN Release Version: 2.0.6 9d6bb506 May 18 17:00:16 kernel: UDB Core Version: 0.2.20 May 18 17:00:16 kernel: Registered DNS Req parsing May 18 17:00:16 kernel: sizeof forward pkt param = 280 May 18 17:00:16 BWDPI: fun bitmap = 43f May 18 17:03:05 rc_service: httpd 2839:notify_rc restart_wrs;restart_firewall May 18 17:03:08 BWDPI: fun bitmap = 43f May 18 17:05:05 rc_service: httpd 2839:notify_rc restart_qos;restart_firewall May 18 17:05:08 BWDPI: fun bitmap = 43f May 18 17:05:27 rc_service: httpd 2839:notify_rc restart_qos;restart_firewall May 18 17:05:30 BWDPI: fun bitmap = 43f May 18 17:12:58 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER

[@SamBondor]

@@annettesurfer What's happening at eth5? What device is connected to it? At this point, I would go by elimination. Connect and disconnect devices to see if the issue is client-agnostic. It's also possible it's just a bug that ASUS doesn't care for. Did you try Merlin?

[@annettesurfer]

​@@SamBondor No idea but that now changed to eth10 and eth8, plus multiple (over a dozen) entries for roamast even though I disabled "roaming assistant" under "professional" in wireless. I don't really know what I'm doing but I think the main bug is the integrated Trend Micro Traffic Analyzer, or the fact it only happens when my youngest son (the hacker) is home, which leads me to think he has something to do with it. My oldest is always complaining about slow internet while playing Vigor on his PS5 but a recent speed test reported 621.7 Mbps download and 38.3 Mbps upload, which is the fastest in our Charter cable/ Spectrum area. I play COD Warzone on my PC at well over 120 FPS on my old I9-10900K with a EVGA RTX 2080 Ti but somehow my nutty oldest son claims he can't hit anything unless everybody turns the wireless off on our phones. Somehow he solved the issue via a VPN but now he's back to complaining again. Maybe a Vigor player is messing with his IP address. As for Merlin, the issues with the router are too minor to chance bricking it, plus I'd lose the thing I'm trying to fix...the traffic analyzer. Although shutting up the Vigor whiner is a priority. Thanks for your hekp.