Asus RT-AXE7800 5GHz Radio Regularly Crashing

[whit4D]

I traced my terrible WiFi performance to the disappearing of the 5 GHz signal. I have had the Asus RT-AXE7800 for about 10 months, and the past few months have been terrible. I traced my poor WiFi performance to the fact that I am making a 2.4 GHz / 802.11n / WiFI 4 connection -- instead of the desirable WiFi 6 (or 6E). I can also see that the 5 GHz radio is gone -- it has crashed -- it is no longer transmitting. I can temporarily fix this by rebooting the router and then re-establishing a WiFi connection (with a 5 GHz signal), but the 5 Ghz radio will eventually crash, reverting my connection to the slower 2.4 Ghz. This happens randomly every day.

On the Wireless tab, I see 5 GHz report the Control Channel as 0:

Current Control Channel: 0

The other radios (2.4 & 6) show a legitimate channel. Each radio has Auto selected for channel. I have experimented with setting a fixed channel, but that does not help.

When the 5 GHz radio has disappeared, the System Log reports this every 5 seconds:

Jun 2 09:11:43 kernel: In wl_dfs_cac_notify_status chanspec 0xe832 DFS state 0
Jun 2 09:11:43 kernel: Set wpa_cap for preauth error -1
Jun 2 09:11:43 kernel: Beacon set security failed
Jun 2 09:11:43 kernel: ADD/SET beacon failed

This looks like a firmware bug; I am running the latest firmware: Firmware Version:3.0.0.4.388_24631

I need to reboot the router to resolve the issue, but this keeps happening randomly every day. I have about 20 devices on this router.

I am extremely frustrated by this and am seriously considering abandoning Asus for a competitor (like TP-Link or back to Netgear?). It sucks because when it works, it works great, but reliability is critical.

Anybody else experience this? Recommendations?

 

[Ripshod]

Have you manually set a 5GHz channel? Set it back to Auto, or just don't use DFS channels

 

[jerry6]

I traced my terrible WiFi performance to the disappearing of the 5 GHz signal. I have had the Asus RT-AXE7800 for about 10 months, and the past few months have been terrible. I traced my poor WiFi performance to the fact that I am making a 2.4 GHz / 802.11n / WiFI 4 connection -- instead of the desirable WiFi 6 (or 6E). I can also see that the 5 GHz radio is gone -- it has crashed -- it is no longer transmitting. I can temporarily fix this by rebooting the router and then re-establishing a WiFi connection (with a 5 GHz signal), but the 5 Ghz radio will eventually crash, reverting my connection to the slower 2.4 Ghz. This happens randomly every day.

On the Wireless tab, I see 5 GHz report the Control Channel as 0:

The other radios (2.4 & 6) show a legitimate channel. Each radio has Auto selected for channel. I have experimented with setting a fixed channel, but that does not help.

When the 5 GHz radio has disappeared, the System Log reports this every 5 seconds:


This looks like a firmware bug; I am running the latest firmware: Firmware Version:3.0.0.4.388_24631

I need to reboot the router to resolve the issue, but this keeps happening randomly every day. I have about 20 devices on this router.

I am extremely frustrated by this and am seriously considering abandoning Asus for a competitor (like TP-Link or back to Netgear?). It sucks because when it works, it works great, but reliability is critical.

Anybody else experience this? Recommendations?

you picked the wrong Asus router weak cpu low on memory , overpriced in my book , my friend bought one I told him to return it and buy another model .

 

[Tech9]

disappearing of the 5 GHz signal

Use non-DFS channels only at 80MHz channel bandwidth and try again. Channels 36-48 or 149-161 (if available).

 

[OzarkEdge]

I traced my terrible WiFi performance to the disappearing of the 5 GHz signal. I have had the Asus RT-AXE7800 for about 10 months, and the past few months have been terrible. I traced my poor WiFi performance to the fact that I am making a 2.4 GHz / 802.11n / WiFI 4 connection -- instead of the desirable WiFi 6 (or 6E). I can also see that the 5 GHz radio is gone -- it has crashed -- it is no longer transmitting. I can temporarily fix this by rebooting the router and then re-establishing a WiFi connection (with a 5 GHz signal), but the 5 Ghz radio will eventually crash, reverting my connection to the slower 2.4 Ghz. This happens randomly every day.

On the Wireless tab, I see 5 GHz report the Control Channel as 0:

The other radios (2.4 & 6) show a legitimate channel. Each radio has Auto selected for channel. I have experimented with setting a fixed channel, but that does not help.

When the 5 GHz radio has disappeared, the System Log reports this every 5 seconds:


This looks like a firmware bug; I am running the latest firmware: Firmware Version:3.0.0.4.388_24631

I need to reboot the router to resolve the issue, but this keeps happening randomly every day. I have about 20 devices on this router.

I am extremely frustrated by this and am seriously considering abandoning Asus for a competitor (like TP-Link or back to Netgear?). It sucks because when it works, it works great, but reliability is critical.

Anybody else experience this? Recommendations?

Know when to call it a hardware issue... if the default configuration router with nothing wired to it can't maintain working radio signal(s), then replace it.

OE

 

[whit4D]

Have you manually set a 5GHz channel? Set it back to Auto, or just don't use DFS channels

I have tried choosing a fixed channel, but that does not resolve the issue.
Also tried disabling Smart Connect and Roaming Assistance.

 

[OzarkEdge]

Also tried disabling Smart Connect and Roaming Assistance.

You said 'crashing radio'... these functions do not crash the radios.

OE

 

[whit4D]

you picked the wrong Asus router weak cpu low on memory , overpriced in my book , my friend bought one I told him to return it and buy another model .

What router do you recommend? (I don't need WiFi 7 yet, but I do need 6E and have about 20 devices spread across a two level, 4400 sq ft house. I have a 1 GB cable modem feed -- which provides a little over 1 GB.)

 

[Tech9]

What router do you recommend?

No much of a choice from Asus Wi-Fi 6E models - GT-AXE16000 is your next step up before Wi-Fi 7 models.

but I do need 6E

What it is used for in your case? This requirement severely limits the choices. All good price/performance models are out.

 

[jerry6]

What router do you recommend? (I don't need WiFi 7 yet, but I do need 6E and have about 20 devices spread across a two level, 4400 sq ft house. I have a 1 GB cable modem feed -- which provides a little over 1 GB.)

Sorry I do not give router buying advice , my friend bought the 88u pro he is happy with it . Has run well with no problems . Others here will give advice on which router to buy , I would pick one with Merlin support , 4400sqft house should be covered with one well placed router the routers in my sig cover a 5000 sqft house and a 2000sq ft house depends on house construction as well concrete walls and floors will kill wifi

 

[PAPPL]

with newest update and disabling SmartConnect and Roaming (single Router setting), i get the same errors and frequent crashes (reboots):

....
kernel: Set wpa_cap for preauth error -1
kernel: Beacon set security failed
kernel: ADD/SET beacon failed
ndev(eth5) e89e7f57 not found
....

I was hoping to get no crashes after disabling these settings.

I'm starting to hate ASUS.

 

[PAPPL]

Re-Enabled Roaming Assistant in Professional settings tab for 5Ghz and 6Ghz only, and set 80Mhz only for 5Ghz band.
No Beacon errors anymore.

The only logs i get spammed are still are Deauth/Auth messages. What is this?:

Mar  2 12:45:54 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-38
Mar  2 12:45:54 wlceventd: wlceventd_proc_event(685): eth7: Auth .....:20:D1:77, status: Successful (0), rssi:0
Mar  2 12:45:54 wlceventd: wlceventd_proc_event(695): eth7: ReAssoc .....:20:D1:77, status: Successful (0), rssi:-72
Mar  2 12:45:54 wlceventd: wlceventd_proc_event(662): eth5: Disassoc .....:20:D1:77, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar  2 12:45:54 wlceventd: wlceventd_proc_event(662): eth5: Disassoc .....:20:D1:77, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar  2 12:45:55 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-37
Mar  2 12:45:56 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:B9:13:55, status: 0, reason: Previous authentication no longer valid (2), rssi:-74
Mar  2 12:45:57 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:B9:13:55, status: 0, reason: Previous authentication no longer valid (2), rssi:-74
Mar  2 12:46:04 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-36
Mar  2 12:46:05 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Unspecified reason (1), rssi:0
Mar  2 12:46:05 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-38
Mar  2 12:46:06 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-38
Mar  2 12:46:07 wlceventd: wlceventd_proc_event(685): eth5: Auth .....:20:D1:77, status: Successful (0), rssi:0
Mar  2 12:46:07 wlceventd: wlceventd_proc_event(695): eth5: ReAssoc .....:20:D1:77, status: Successful (0), rssi:-69
Mar  2 12:46:15 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-37
Mar  2 12:46:16 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-37
Mar  2 12:46:16 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-38
Mar  2 12:46:17 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-38
Mar  2 12:46:25 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:B9:13:55, status: 0, reason: Previous authentication no longer valid (2), rssi:-74
Mar  2 12:46:26 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:B9:13:55, status: 0, reason: Previous authentication no longer valid (2), rssi:-74
Mar  2 12:46:26 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-39
Mar  2 12:46:27 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Unspecified reason (1), rssi:0
Mar  2 12:46:27 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-39
Mar  2 12:46:27 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-39
Mar  2 12:46:37 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-36
Mar  2 12:46:38 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Unspecified reason (1), rssi:0
Mar  2 12:46:38 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-36
Mar  2 12:46:38 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-36
Mar  2 12:46:39 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:B9:13:55, status: 0, reason: Previous authentication no longer valid (2), rssi:-74
Mar  2 12:46:40 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:B9:13:55, status: 0, reason: Previous authentication no longer valid (2), rssi:-74
Mar  2 12:46:48 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:20:D1:77, status: 0, reason: Disassociated due to inactivity (4), rssi:-73
Mar  2 12:46:48 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-37
Mar  2 12:46:49 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Unspecified reason (1), rssi:0
Mar  2 12:46:49 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-38
Mar  2 12:46:49 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-37
Mar  2 12:46:49 wlceventd: wlceventd_proc_event(685): eth7: Auth .....:20:D1:77, status: Successful (0), rssi:0
Mar  2 12:46:49 wlceventd: wlceventd_proc_event(695): eth7: ReAssoc .....:20:D1:77, status: Successful (0), rssi:-71
Mar  2 12:46:49 wlceventd: wlceventd_proc_event(662): eth5: Disassoc .....:20:D1:77, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar  2 12:46:49 wlceventd: wlceventd_proc_event(662): eth5: Disassoc .....:20:D1:77, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar  2 12:46:59 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-38
Mar  2 12:47:00 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Unspecified reason (1), rssi:0
Mar  2 12:47:00 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-38
Mar  2 12:47:00 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-38
Mar  2 12:47:00 dnsmasq[3314]: possible DNS-rebind attack detected: app-analytics-v2.snapchat.com
Mar  2 12:47:07 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:B9:13:55, status: 0, reason: Previous authentication no longer valid (2), rssi:-73
Mar  2 12:47:08 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:B9:13:55, status: 0, reason: Previous authentication no longer valid (2), rssi:-73
Mar  2 12:47:10 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-38
Mar  2 12:47:11 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Unspecified reason (1), rssi:0
Mar  2 12:47:11 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-38
Mar  2 12:47:11 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-38
Mar  2 12:47:21 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-36
Mar  2 12:47:21 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:B9:13:55, status: 0, reason: Previous authentication no longer valid (2), rssi:-73
Mar  2 12:47:22 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Unspecified reason (1), rssi:0
Mar  2 12:47:22 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-37
Mar  2 12:47:22 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:40:B3:BC, status: 0, reason: Previous authentication no longer valid (2), rssi:-37
Mar  2 12:47:22 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind .....:B9:13:55, status: 0, reason: Previous authentication no longer valid (2), rssi:-73
Mar  2 12:47:22 wlceventd: wlceventd_proc_event(685): eth7: Auth .....:16:7C:C8, status: Successful (0), rssi:0
Mar  2 12:47:22 wlceventd: wlceventd_proc_event(695): eth7: ReAssoc .....:16:7C:C8, status: Successful (0), rssi:-73
Mar  2 12:47:22 wlceventd: wlceventd_proc_event(662): eth6: Disassoc .....:16:7C:C8, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar  2 12:47:22 wlceventd: wlceventd_proc_event(662): eth6: Disassoc .....:16:7C:C8, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar  2 12:47:24 wlceventd: wlceventd_proc_event(685): eth5: Auth .....:20:D1:77, status: Successful (0), rssi:0