RT-AXE7800 loses WiFi (incl. Logfile)

[PAPPL]

Hi,

i'm using Asus RT-AXE7800 with latest firmware (3.0.0.4.388_25127) and once a week this router loses wifi. All my devices can't detect and log into the router. SSID isn't even visible for all previously connected devices, they go offline. Have to reboot the router and then it works again for a week.
Using same SSID for all three bands, else it works great.

Is this a known issue and is there a solution?

pappl

 

[tai1965]

@PAPPL well said. I see the exact same behavior. I'll get 1 - 3 weeks then all of a sudden devices like phones will not be able to connect to WiFi. I do see the SSID but the connection fails. Additionally, I cannot get to the RT-AXE7800 web interface and the only fix is to unplug the router. This is an improvement over the random crashes I used to see on older firmwares.

Most likely this is some sort of memory leak. On my older router I used to schedule a 4AM reboot once a week to avoid these sorts of issues.

 

[PAPPL]

True, i can also see the SSID but can't connect. All devices can't connect.
Already doing 4am reboot, but it's still happening. Even same day after reboot.
This firmware must be unstable, never had this before with my previous router.

 

[PAPPL]

Happened again, still firmware 3.0.0.4.388_25127
Around 15:27 (3:27pm) my devices went offline, no SSID visible.
At 15:28 or 15:29 (3:28pm or 3:39pm) my devices were online again. Any clue?

LOG PART 1

Jan  1 01:00:50 WAN Connection: WAN was restored.
Jan  1 01:00:50 ntp: start NTP update
Feb 17 15:27:35 rc_service: ntp 2910:notify_rc restart_stubby
Feb 17 15:27:35 rc_service: ntp 2910:notify_rc restart_diskmon
Feb 17 15:27:35 rc_service: waitting "restart_stubby" via ntp ...
Feb 17 15:27:35 wan_up: Find a 2.5G port on [eth0]
Feb 17 15:27:35 GPY211: ### GPY211 WAR 1G : eth0 ###
Feb 17 15:27:36 disk_monitor: Finish
Feb 17 15:27:36 disk monitor: be idle
Feb 17 15:27:36 acsd: eth6: selected channel spec: 0x694f (6g69/160)
Feb 17 15:27:36 acsd: eth6: Adjusted channel spec: 0x694f (6g69/160)
Feb 17 15:27:36 acsd: eth6: selected channel spec: 0x694f (6g69/160)
Feb 17 15:27:36 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 19) Link DOWN.
Feb 17 15:27:37 ping_target_with_size: Ping test is complete.
Feb 17 15:27:38 wlceventd: wlceventd_proc_event(685): eth5: Auth ...A2:A9:08, status: Successful (0), rssi:0
Feb 17 15:27:38 wlceventd: wlceventd_proc_event(695): eth5: ReAssoc ...A2:A9:08, status: Successful (0), rssi:-50
Feb 17 15:27:38 ping_target_with_size: Failed to ping target(192.168.178.1) with size(79)
Feb 17 15:27:40 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 19) Link Up at 1000 mbps full duplex
Feb 17 15:27:40 ping_target_with_size: Ping test is complete.
Feb 17 15:27:41 WAN Connection: WAN(0) link up.
Feb 17 15:27:41 rc_service: wanduck 1786:notify_rc restart_wan_if 0
Feb 17 15:27:41 ping_target_with_size: Failed to ping target(192.168.178.1) with size(80)
Feb 17 15:27:41 wan_up: Restart DDNS
Feb 17 15:27:41 dhcp client: bound 192.168.178.20/255.255.255.0 via 192.168.178.1 for 864000 seconds.
Feb 17 15:27:41 wlceventd: wlceventd_proc_event(695): eth5: ReAssoc ...4D:93:69, status: Successful (0), rssi:-48
Feb 17 15:27:42 bsd: bsd: Sending act Frame to ...4d:93:69 with transition target eth7 ssid 10:7c:61:a6:d6:b4
Feb 17 15:27:43 wlceventd: wlceventd_proc_event(695): eth5: ReAssoc ...ED:50:59, status: Successful (0), rssi:-49
Feb 17 15:27:44 bsd: bsd: STA:...4d:93:69 no response
Feb 17 15:27:44 bsd: bsd: Sending act Frame to ...4d:93:69 with transition target eth7 ssid 10:7c:61:a6:d6:b4
Feb 17 15:27:45 bsd: bsd: STA:...4d:93:69 no response
Feb 17 15:27:45 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...4D:93:69, status: 0, reason: Previous authentication no longer valid (2), rssi:-44
Feb 17 15:27:45 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...4D:93:69, status: 0, reason: Previous authentication no longer valid (2), rssi:-44
Feb 17 15:27:45 crond[2557]: time disparity of 595587 minutes detected
Feb 17 15:27:45 GPY211: ### GPY211 WAR AUTO : eth0 ###
Feb 17 15:27:45 wan: finish adding multi routes
Feb 17 15:27:46 WAN Connection: WAN was restored.
Feb 17 15:27:46 kernel: Archer TCP Pure ACK Enabled
Feb 17 15:27:46 rc_service: udhcpc_wan 3105:notify_rc stop_samba
Feb 17 15:27:46 Samba Server: smb daemon is stopped
Feb 17 15:27:46 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 19) Link DOWN.
Feb 17 15:27:47 rc_service: udhcpc_wan 3105:notify_rc start_samba
Feb 17 15:27:48 wan_up: Find a 2.5G port on [eth0]
Feb 17 15:27:50 bsd: bsd: Sending act Frame to ...ed:50:59 with transition target eth7 ssid 10:7c:61:a6:d6:b4
Feb 17 15:27:50 ping_target_with_size: Ping test is complete.
Feb 17 15:27:50 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=3, status=7, mac=00:00:00:00:00:00
Feb 17 15:27:50 bsd: bsd: BSS Transit Response: STA reject
Feb 17 15:27:50 bsd: bsd: Skip STA:...ed:50:59 reject BSSID
Feb 17 15:27:50 kernel: eth0 (Int switch port: 5) (Logical Port: 5) (phyId: 19) Link Up at 2500 mbps full duplex
Feb 17 15:27:51 ping_target_with_size: Failed to ping target(192.168.178.1) with size(79)
Feb 17 15:27:53 ping_target_with_size: Ping test is complete.
Feb 17 15:27:54 ping_target_with_size: Failed to ping target(192.168.178.1) with size(80)
Feb 17 15:27:54 wan_up: Restart DDNS
Feb 17 15:27:54 dhcp client: bound 192.168.178.20/255.255.255.0 via 192.168.178.1 for 864000 seconds.
Feb 17 15:27:55 WAN Connection: WAN(0) link up.
Feb 17 15:27:55 rc_service: wanduck 1786:notify_rc restart_wan_if 0
Feb 17 15:27:55 wlceventd: wlceventd_proc_event(722): eth5: Assoc ...4D:93:69, status: Successful (0), rssi:-47
Feb 17 15:27:56 wan: finish adding multi routes
Feb 17 15:27:56 kernel: Archer TCP Pure ACK Enabled
Feb 17 15:27:56 rc_service: udhcpc_wan 3863:notify_rc stop_samba
Feb 17 15:27:56 Samba Server: smb daemon is stopped
Feb 17 15:27:57 rc_service: udhcpc_wan 3863:notify_rc start_samba
Feb 17 15:27:58 WAN Connection: WAN was restored.
Feb 17 15:27:58 wlceventd: wlceventd_proc_event(722): eth5: Assoc ...4A:24:A8, status: Successful (0), rssi:-55
Feb 17 15:27:58 wan_up: Find a 2.5G port on [eth0]
Feb 17 15:27:59 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-44
Feb 17 15:27:59 ping_target_with_size: Ping test is complete.
Feb 17 15:28:00 wlceventd: wlceventd_proc_event(662): eth7: Disassoc ...A2:A9:08, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 17 15:28:00 bsd: bsd: Sending act Frame to ...4d:93:69 with transition target eth7 ssid 10:7c:61:a6:d6:b4
Feb 17 15:28:00 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Feb 17 15:28:01 bsd: bsd: STA:...4d:93:69 no response
Feb 17 15:28:01 bsd: bsd: Sending act Frame to ...4d:93:69 with transition target eth7 ssid 10:7c:61:a6:d6:b4
Feb 17 15:28:01 ping_target_with_size: Successful to ping target(192.168.178.1) with size(79)
Feb 17 15:28:01 wan_up: Restart DDNS
Feb 17 15:28:01 dhcp client: bound 192.168.178.20/255.255.255.0 via 192.168.178.1 for 864000 seconds.
Feb 17 15:28:02 wlceventd: wlceventd_proc_event(662): eth7: Disassoc ...4A:24:A8, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 17 15:28:02 bsd: bsd: STA:...4d:93:69 no response
Feb 17 15:28:02 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...4D:93:69, status: 0, reason: Previous authentication no longer valid (2), rssi:-44
Feb 17 15:28:03 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...4D:93:69, status: 0, reason: Previous authentication no longer valid (2), rssi:-42
Feb 17 15:28:04 wlceventd: wlceventd_proc_event(662): eth7: Disassoc ...ED:50:59, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 17 15:28:07 wlceventd: wlceventd_proc_event(685): eth5: Auth ...DC:EE:C5, status: Successful (0), rssi:0
Feb 17 15:28:07 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...DC:EE:C5, status: 0, reason: Previous authentication no longer valid (2), rssi:-54
Feb 17 15:28:07 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...DC:EE:C5, status: 0, reason: Previous authentication no longer valid (2), rssi:-54
Feb 17 15:28:08 wlceventd: wlceventd_proc_event(722): eth5: Assoc ...DC:EE:C5, status: Successful (0), rssi:-55
Feb 17 15:28:09 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-44
Feb 17 15:28:10 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...B9:13:55, status: 0, reason: Previous authentication no longer valid (2), rssi:-56
Feb 17 15:28:10 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...B9:13:55, status: 0, reason: Previous authentication no longer valid (2), rssi:-56
Feb 17 15:28:10 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Feb 17 15:28:11 wlceventd: wlceventd_proc_event(722): eth5: Assoc ...4D:93:69, status: Successful (0), rssi:-48
Feb 17 15:28:11 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-44
Feb 17 15:28:11 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Feb 17 15:28:12 bsd: bsd: Sending act Frame to ...dc:ee:c5 with transition target eth7 ssid 10:7c:61:a6:d6:b4
Feb 17 15:28:12 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=6, status=7, mac=00:00:00:00:00:00
Feb 17 15:28:12 bsd: bsd: BSS Transit Response: STA reject
Feb 17 15:28:12 bsd: bsd: Skip STA:...dc:ee:c5 reject BSSID

 

[PAPPL]

LOG PART 2

Feb 17 15:28:22 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Feb 17 15:28:22 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-44
Feb 17 15:28:23 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...B9:13:55, status: 0, reason: Previous authentication no longer valid (2), rssi:-55
Feb 17 15:28:23 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-45
Feb 17 15:28:24 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-44
Feb 17 15:28:24 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...B9:13:55, status: 0, reason: Previous authentication no longer valid (2), rssi:-55
Feb 17 15:28:33 kernel: In wl_dfs_cac_notify_status chanspec 0xe06a DFS state 2
Feb 17 15:28:34 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Feb 17 15:28:34 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Feb 17 15:28:35 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Feb 17 15:28:35 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Feb 17 15:28:45 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-45
Feb 17 15:28:45 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-45
Feb 17 15:28:46 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Feb 17 15:28:46 wlceventd: wlceventd_proc_event(685): eth7: Auth ...4A:24:A8, status: Successful (0), rssi:0
Feb 17 15:28:46 wlceventd: wlceventd_proc_event(695): eth7: ReAssoc ...4A:24:A8, status: Successful (0), rssi:-60
Feb 17 15:28:46 wlceventd: wlceventd_proc_event(662): eth5: Disassoc ...4A:24:A8, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 17 15:28:46 wlceventd: wlceventd_proc_event(662): eth5: Disassoc ...4A:24:A8, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 17 15:28:46 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Feb 17 15:28:51 wlceventd: wlceventd_proc_event(685): eth7: Auth ...DC:EE:C5, status: Successful (0), rssi:0
Feb 17 15:28:51 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind ...DC:EE:C5, status: 0, reason: Previous authentication no longer valid (2), rssi:-52
Feb 17 15:28:51 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind ...DC:EE:C5, status: 0, reason: Previous authentication no longer valid (2), rssi:-52
Feb 17 15:28:51 wlceventd: wlceventd_proc_event(695): eth7: ReAssoc ...DC:EE:C5, status: Successful (0), rssi:-52
Feb 17 15:28:51 wlceventd: wlceventd_proc_event(662): eth5: Disassoc ...DC:EE:C5, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 17 15:28:51 wlceventd: wlceventd_proc_event(662): eth5: Disassoc ...DC:EE:C5, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 17 15:28:54 wlceventd: wlceventd_proc_event(722): eth7: Assoc E6:70:6F:50:5A:D6, status: Successful (0), rssi:-68
Feb 17 15:28:56 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Feb 17 15:28:56 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind ...4D:93:69, status: 0, reason: Disassociated due to inactivity (4), rssi:-45
Feb 17 15:28:56 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-41
Feb 17 15:28:58 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-44
Feb 17 15:28:58 wlceventd: wlceventd_proc_event(685): eth7: Auth ...D8:13:C8, status: Successful (0), rssi:0
Feb 17 15:28:58 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind ...D8:13:C8, status: 0, reason: Previous authentication no longer valid (2), rssi:-56
Feb 17 15:28:58 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind ...D8:13:C8, status: 0, reason: Previous authentication no longer valid (2), rssi:-56
Feb 17 15:28:58 wlceventd: wlceventd_proc_event(722): eth7: Assoc ...D8:13:C8, status: Successful (0), rssi:-56
Feb 17 15:28:59 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-44
Feb 17 15:28:59 dnsmasq[4004]: possible DNS-rebind attack detected: app-analytics-v2.snapchat.com
Feb 17 15:29:04 dnsmasq[4004]: possible DNS-rebind attack detected: app-analytics-v2.snapchat.com
Feb 17 15:29:08 ahs: [read_json]Update ahs JSON file.
Feb 17 15:29:08 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Feb 17 15:29:09 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Feb 17 15:29:09 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind ...B9:13:55, status: 0, reason: Previous authentication no longer valid (2), rssi:-72
Feb 17 15:29:10 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-45
Feb 17 15:29:10 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Feb 17 15:29:10 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind ...B9:13:55, status: 0, reason: Previous authentication no longer valid (2), rssi:-72
Feb 17 15:29:20 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-45
Feb 17 15:29:20 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-45
Feb 17 15:29:22 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-45
Feb 17 15:29:22 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Feb 17 15:29:22 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7968)]periodic_check AM 4:55
Feb 17 15:29:22 WATCHDOG: [FAUPGRADE][auto_firmware_check:(8012)]do webs_update
Feb 17 15:29:32 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-44
Feb 17 15:29:32 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-44
Feb 17 15:29:34 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Feb 17 15:29:34 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-44
Feb 17 15:29:37 WATCHDOG: [FAUPGRADE][auto_firmware_check:(8030)]retrieve firmware information
Feb 17 15:29:37 WATCHDOG: [FAUPGRADE][auto_firmware_check:(8033)]user in use

 

[dave14305]

Around 15:27 (3:27pm) my devices went offline, no SSID visible.
At 15:29 (3:28pm) my devices were online again. Any clue?

Looks like the router rebooted, resetting the clock back to Jan 1 until time could be synced again.

 

[PAPPL]

Looks like the router rebooted, resetting the clock back to Jan 1 until time could be synced again.

Oh, i see. I thought there was no log between 01.January and 17.February.
The Log has 17.Feb, then 01.Jan, then 17.Feb again.

Prior reboot (01.Jan.2025) i get a lot of:

Feb 17 15:25:19 dnsmasq[3225]: possible DNS-rebind attack detected: app-analytics-v2.snapchat.com
Feb 17 15:25:21 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind ...40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-39

What does it mean? Is there something else suspicious prior Feb 17 15:25:57?

I have enabled DNS Rebind protection in WAN settings and i'm using Adguard DNS-over-TLS Servers in WAN settings. This shouldn't break Wifi?

See Full Log attached as txt