ASUS GTAX11000 Disconnect issues

[Starlocket]

Posting here cuz I've head no luck with Asus support other than requesting to send it in and waiting a few weeks. Trying to figure out whether its a router issue or elsewhere.

Basically the issue is this, randomly at least once (sometimes twice) a day (sometimes can go 1-3 days w/o any issue) the modem will just lose internet access.

We had our cable provider come out and test and say it was initially the modem, but tests w/ it showed nothing wrong, still replaced anyways per their recommendation. Using a motorola (latest can get the model if anyone needs)
Set that up and was back online for a few days before the issue happenned again.


Our setup:

Asus GTAX11000 Router as the main router on AI MESH
GTX?5300 Router as an AP in wired backhaul mode.

Modem connects to the 11000, while the 5300 connects to the 11000 directly (from upstairs (3 floors used to be on the 2nd but moved to the 3rd )
For the rest of the wall jacks in the house we have them going to a switch panel that diverts down via 2 lines to our 11000.

The issue when the router loses internet is that I can't ping or anything, and router says internet has no connection, HOWEVER if I reboot the router, everything is fine.

If I connect directly to the modem itself while the router is down ( unplugging from router and putting directly to laptop ) internet is still working.

I've attempted a factory reset on the devices after to validate but no dice so far.

We're gonna probably order the 16000 to replace the 11000 in the event its bad but trying to get additional insight to see if maybe it could just be a setting within the AI Mesh that I'm missing.

Here's the latest log from when it disconnected , I logged into the router and copy/pasta'd the log before rebooting. Any additional info requests please let me know.

May 12 21:52:09 wlceventd: wlceventd_proc_event(508): eth6: Disassoc C6:58:F6:3A:FD:30, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 12 21:52:09 wlceventd: wlceventd_proc_event(508): eth6: Disassoc C6:58:F6:3A:FD:30, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 12 21:52:09 roamast: [EXAP]Deauth old sta in 0 0: C6:58:F6:3A:FD:30
May 12 21:52:09 roamast: eth6: disconnect weak signal strength station [c6:58:f6:3a:fd:30]
May 12 21:52:09 roamast: eth6: remove client [c6:58:f6:3a:fd:30] from monitor list
May 12 21:52:31 wlceventd: wlceventd_proc_event(508): eth7: Disassoc EE:E1:18:5C:60:86, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 12 21:52:31 wlceventd: wlceventd_proc_event(508): eth7: Disassoc EE:E1:18:5C:60:86, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 12 21:52:31 roamast: [EXAP]Deauth old sta in 1 0: EE:E1:18:5C:60:86
May 12 21:52:31 roamast: eth7: disconnect weak signal strength station [ee:e1:18:5c:60:86]
May 12 21:52:31 roamast: eth7: remove client [ee:e1:18:5c:60:86] from monitor list
May 12 21:52:34 wlceventd: wlceventd_proc_event(527): eth7: Auth EE:E1:18:5C:60:86, status: Successful (0), rssi:0
May 12 21:52:34 wlceventd: wlceventd_proc_event(537): eth7: ReAssoc EE:E1:18:5C:60:86, status: Successful (0), rssi:-85
May 12 21:52:40 wlceventd: wlceventd_proc_event(508): eth7: Disassoc EE:E1:18:5C:60:86, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 12 21:52:40 wlceventd: wlceventd_proc_event(508): eth7: Disassoc EE:E1:18:5C:60:86, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 12 21:52:42 roamast: [EXAP]Deauth old sta in 1 0: EE:E1:18:5C:60:86
May 12 21:52:42 roamast: eth7: disconnect weak signal strength station [ee:e1:18:5c:60:86]
May 12 21:52:42 roamast: eth7: remove client [ee:e1:18:5c:60:86] from monitor list
May 12 21:52:42 wlceventd: wlceventd_proc_event(527): eth7: Auth EE:E1:18:5C:60:86, status: Successful (0), rssi:0
May 12 21:52:42 wlceventd: wlceventd_proc_event(537): eth7: ReAssoc EE:E1:18:5C:60:86, status: Successful (0), rssi:-80
May 12 21:52:54 roamast: [EXAP]Deauth old sta in 1 0: EE:E1:18:5C:60:86
May 12 21:52:54 roamast: eth7: disconnect weak signal strength station [ee:e1:18:5c:60:86]
May 12 21:52:54 roamast: eth7: remove client [ee:e1:18:5c:60:86] from monitor list

 

[Starrbuck]

That log appears to contain only wireless info. I don't see anything about the WAN connection.

Usually what you are experiencing is a DHCP issue. Have you tried playing around with the "DHCP query frequency" setting?

 

[Starlocket]

That log appears to contain only wireless info. I don't see anything about the WAN connection.

Usually what you are experiencing is a DHCP issue. Have you tried playing around with the "DHCP query frequency" setting?

where can I find that ?

 

[Starrbuck]

where can I find that ?

Near the bottom of the WAN - Internet Connection screen.

 

[degrub]

read -

Tutorial - How to automatically run a script on asus routers that monitors your WAN link - will reboot the router if WAN is down. (from POV of a non linux guy)

My hardware Asus RT-AX92U, I believe this may work for many other asus routers but I only have the RT-AX92U router so I cannot say if this works for other asus routers. Firmware 3.0.04.386.43084 Note: You need a USB stick to automate. First my issue and why I wanted to automate a reboot of...

www.snbforums.com

 

[Starlocket]

Near the bottom of the WAN - Internet Connection screen.

Thanks, found it and set it to continuous and so far was good till now where it dropped again. Still repeating the issue.

Curious if there's anything else I can try.

read -

Tutorial - How to automatically run a script on asus routers that monitors your WAN link - will reboot the router if WAN is down. (from POV of a non linux guy)

My hardware Asus RT-AX92U, I believe this may work for many other asus routers but I only have the RT-AX92U router so I cannot say if this works for other asus routers. Firmware 3.0.04.386.43084 Note: You need a USB stick to automate. First my issue and why I wanted to automate a reboot of...

www.snbforums.com

Appreciate it, but this is what I'm trying to avoid, losing connection entirely at a constant, which I've never had w/ any other router previously, its just an annoyance since my family works from home and the disconnection eats into calls, and work.

 

[Starlocket]

Just following up in hopes of other possible solutions. If ultimately the only fix is to have a script that auto reboots the router then I'll go ahead and check out other routers on the market if anyone can recommend one that properly works as intended since I'm seeing this appears to have been something introduced in a later firmware.

Anyone know if the 160000X has the same issue or is this w/ all Asus routers currently.

 

[Starlocket]

@Invisible Boy
My AC68U & AX10000 would drop internet randomly, sometime once a few days, sometimes a few times a day. IDK if it's my noisy DSL line, SmartRG modems (I have 2) or the ASUS firmware. After spending months trying to find a pattern and fix it, I simply give up and let it be. I tend to believe ASUS software simply suck (and not just for their routers) as the modems never loses the DSL connection, my ASUS routers simply drop the internet connection randomly. Sometime it will reconnect the internet by itself within a few minutes, sometimes a lot longer if I leave it alone. I suspect all ASUS routers suffered from this issue which has been known for years w/o explanation.

That's a shame, I doubt others work w/ the AI mesh asus has, was looking to see about replacing it w/ the 16000 but if thats the case I'll have to check the other sub sections to see whats equivalent, I'm seeing that noted as a common thing on the asus forums and reddit as well about the disconnect part, shame Asus won't respond on the matter despite it being pointed out what builds it first appeared in.

**Edit**

Wait what happenned to all the comments did mods remove them?

 

[Starlocket]

Checking back in as a lot of comments seem to have been removed, idky they appeared to be helpful at least information wise, hoping anyone can shine some light on this if this is def the issue w/ AI mesh and manual/scripted reboots are required? If so does custom firmware here fix that or is it something only at asus' level of repair?