Results 1 to 8 of 8
  1. #1
    ROG Member Array
    Join Date
    Nov 2015
    Reputation
    10
    Posts
    8

    GT-AX11000 drops WAN connection every couple of days - even on latest beta firmware

    Every couple of days, my GT-AX11000 drops the WAN connection. The GUI will say "Disconnected" and none of my clients can talk out to the internet anymore.

    I applied the latest Beta firmware (9.0.0.4.386_45652-gea67014), hoping that would address the issue, but unfortunately it still happens.

    It's not my cable modem, because a simple GT-AX11000 restart resolves the issue.

    What may be of note is that I re-assigned the 2.5 Gig part as my WAN port.

    Here are the last few log entries:

    Code:
    Sep 22 02:08:34 miniupnpd[1718]: remove port mapping 54624 UDP because it has expired
    Sep 22 03:54:22 miniupnpd[1718]: remove port mapping 54624 UDP because it has expired
    Sep 22 04:20:14 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7431)]do webs_update
    Sep 22 04:20:16 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7449)]retrieve firmware information
    Sep 22 04:20:16 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7464)]fimrware update check first time
    Sep 22 04:20:16 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7497)]no need to upgrade firmware
    Sep 22 04:20:46 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7431)]do webs_update
    Sep 22 04:20:46 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7449)]retrieve firmware information
    Sep 22 04:20:46 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7469)]fimrware update check once
    Sep 22 04:21:16 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7431)]do webs_update
    Sep 22 04:21:16 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7449)]retrieve firmware information
    Sep 22 04:21:16 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7469)]fimrware update check once
    Sep 22 04:21:46 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7431)]do webs_update
    Sep 22 04:21:46 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7449)]retrieve firmware information
    Sep 22 04:21:46 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7464)]fimrware update check first time
    Sep 22 04:21:46 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7497)]no need to upgrade firmware
    Sep 22 07:50:04 miniupnpd[1718]: upnp_event_process_notify: connect(192.168.1.43:2869): Connection timed out
    Sep 22 07:50:06 miniupnpd[1718]: upnp_event_process_notify: connect(192.168.1.43:2869): Connection timed out
    Sep 22 07:50:06 miniupnpd[1718]: upnpevents_processfds: 0x2964b0, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-3c7c3f86ab9c after an ERROR cb: http://192.168.1.43:2869/upnp/eventing/wcxgdmcveq
    Sep 22 07:52:08 wlceventd: wlceventd_proc_event(527): eth8: Auth B2:6D:62:76:00:D3, status: Successful (0), rssi:0
    Sep 22 07:52:08 wlceventd: wlceventd_proc_event(556): eth8: Assoc B2:6D:62:76:00:D3, status: Successful (0), rssi:-72
    Sep 22 08:40:45 wlceventd: wlceventd_proc_event(527): eth6: Auth A0:6A:44:89:44:47, status: Successful (0), rssi:0
    Sep 22 08:40:45 wlceventd: wlceventd_proc_event(556): eth6: Assoc A0:6A:44:89:44:47, status: Successful (0), rssi:-56
    Sep 22 09:23:44 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 3C:A3:08:93:1F:79, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-49
    Sep 22 09:23:44 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 3C:A3:08:93:1F:79, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-49
    Sep 22 09:23:44 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 3C:A3:08:93:1F:79, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-49
    Sep 22 09:23:46 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 3C:A3:08:93:1F:79, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
    Sep 22 09:23:55 wlceventd: wlceventd_proc_event(527): eth6: Auth 3C:A3:08:93:1F:79, status: Successful (0), rssi:0
    Sep 22 09:23:55 wlceventd: wlceventd_proc_event(556): eth6: Assoc 3C:A3:08:93:1F:79, status: Successful (0), rssi:-50
    Sep 22 09:42:18 wlceventd: wlceventd_proc_event(527): eth7: Auth 38:68:93:5C:95:2C, status: Successful (0), rssi:0
    Sep 22 09:42:18 wlceventd: wlceventd_proc_event(537): eth7: ReAssoc 38:68:93:5C:95:2C, status: Successful (0), rssi:-82
    Sep 22 09:42:55 wlceventd: wlceventd_proc_event(491): eth8: Deauth_ind 38:68:93:5C:95:2C, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-79
    Sep 22 09:42:55 wlceventd: wlceventd_proc_event(491): eth8: Deauth_ind 38:68:93:5C:95:2C, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-79
    Sep 22 09:42:56 wlceventd: wlceventd_proc_event(508): eth8: Disassoc 38:68:93:5C:95:2C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
    Sep 22 10:29:17 wlceventd: wlceventd_proc_event(491): eth8: Deauth_ind 12:5E:48:4F:A5:B4, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-78
    Sep 22 10:29:17 wlceventd: wlceventd_proc_event(491): eth8: Deauth_ind 12:5E:48:4F:A5:B4, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-78
    Sep 22 10:29:18 wlceventd: wlceventd_proc_event(508): eth8: Disassoc 12:5E:48:4F:A5:B4, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
    Sep 22 10:29:24 wlceventd: wlceventd_proc_event(527): eth8: Auth 12:5E:48:4F:A5:B4, status: Successful (0), rssi:0
    Sep 22 10:29:24 wlceventd: wlceventd_proc_event(537): eth8: ReAssoc 12:5E:48:4F:A5:B4, status: Successful (0), rssi:-81
    Sep 22 10:37:06 miniupnpd[1718]: remove port mapping 54624 UDP because it has expired
    Sep 22 10:43:37 WAN Connection: WAN(0) link down.

  2. #2
    New ROGer Array
    Join Date
    Jul 2021
    Reputation
    10
    Posts
    3

    I have the same problem, and has been happening ever since I got the AX11000.
    Support just advise a factory reset.

    What I did which has helped for over a month was setup a schedule to reboot around 2am on a Sunday and Wednesday.
    This has been working fine, until I upgraded to the latest firmware Version 3.0.0.4.386.45375 from 3.0.0.4.386.44266.

    The latest version caused disconnects again, so I have tried the beta version 9.0.0.4_386_45652-gea67014 (from this thread https://rog.asus.com/forum/showthrea...hats-happening)
    But this beta version is losing the AI Mesh system every day.

    I have now gone back to the .44266 version today and will give it a few days to see what happens, perhaps schedule yours for a reboot and see if it helps.

  3. #3
    ROG Guru: White Belt Array
    Join Date
    Apr 2020
    Reputation
    32
    Posts
    84

    did you two send feedback to asus? please PM me your email
    Thanks.

  4. #4
    New ROGer Array
    Join Date
    Jul 2021
    Reputation
    10
    Posts
    3

    Quote Originally Posted by wilsondenq View Post
    did you two send feedback to asus? please PM me your email
    Thanks.
    I did send feedback to Asus, after my constant disconnections since I purchased it in March of this year, although I did not when I used the beta firmware this week.
    If I get disconnections again, I will send more feedback and PM you my details.
    Thanks for your help.

  5. #5
    New ROGer Array
    Join Date
    Aug 2021
    Reputation
    10
    Posts
    36

    Quote Originally Posted by GreenMotion View Post
    Every couple of days, my GT-AX11000 drops the WAN connection. The GUI will say "Disconnected" and none of my clients can talk out to the internet anymore.
    I applied the latest Beta firmware (9.0.0.4.386_45652-gea67014), hoping that would address the issue, but unfortunately it still happens.
    It's not my cable modem, because a simple GT-AX11000 restart resolves the issue.
    What may be of note is that I re-assigned the 2.5 Gig part as my WAN port.
    Here are the last few log entries:
    Does your modem do the connecting or the AX?
    How is the AX setup on the WAN side?

  6. #6
    ROG Member Array
    Join Date
    Nov 2015
    Reputation
    10
    Posts
    8

    Quote Originally Posted by Indigian View Post
    Does your modem do the connecting or the AX?
    How is the AX setup on the WAN side?
    My AX connects to a Motorola SB8611 Cable modem and I'm on the Xfinity 1200 plan. The SB8611 has a 2.5 Gig port, and so to get the full 1200, I had to connect it to the 2.5 Gig game port on the AX and configure that game port as the WAN port.

  7. #7
    New ROGer Array
    Join Date
    Jul 2021
    Reputation
    10
    Posts
    3

    Quote Originally Posted by GreenMotion View Post
    My AX connects to a Motorola SB8611 Cable modem and I'm on the Xfinity 1200 plan. The SB8611 has a 2.5 Gig port, and so to get the full 1200, I had to connect it to the 2.5 Gig game port on the AX and configure that game port as the WAN port.
    My modem is also connected to the 2.5g port, I have read others having problems with the 2.5g port also, but mainly speed, however I wonder if this is an issue with the 2.5g port.

  8. #8
    New ROGer Array
    Join Date
    Nov 2021
    Reputation
    10
    Posts
    7

    I am having the same issue.

    I have two GT-AX11000 one is the main router and one is the mesh node.

    The main router drops the WLAN connection every 1-2 days.

    I then have to log into the router and reboot it to get a WAN connection.

    How do I fix this?

    FIRMWARE: 3.0.0.4.386_45898-gfa90458

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •