[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: Wi-Fi client sometimes reconnects for no reason

Hi guys. I have a problem that I've been troubleshooting for about a month now with no luck, so I finally gave up and decided to post here.
One of the phones (Samsung Galaxy S22) sometimes decides to disconnect and reconnect multiple times to wifi even when in the room near AP. All other phones (even another Galaxy S22 with identical settings) don't exhibit this behavior. The AP is Asus RP-AX58 connected in repeater mode (not AiMesh node) to RT-AX88U Pro over 5GHz, clients over 2.4GHz. All firmware latest, hard reset, then configured with minimal settings.
Here's the log (log_level set to 8):

Code:
Mar  9 11:46:25 wpa_supplicant[2652]: eth2: WPA: Group rekeying completed with c8:7f:54:5e:a6:b4 [GTK=CCMP]
Mar  9 11:46:25 kernel: CFG80211-ERROR) wl_cfg80211_set_rekey_data :
Mar  9 11:46:25 kernel: seting gtk_key_info failed code=-23
Mar  9 11:49:14 hostapd: wl0.1: STA 98:b8:bc:a5:73:a0 WPA: group key handshake completed (RSN)
Mar  9 11:49:14 hostapd: wl0.1: STA b4:0b:1d:69:84:ad WPA: group key handshake completed (RSN)
Mar  9 12:22:42 hostapd: wl0.1: STA b4:0b:1d:69:84:ad IEEE 802.11: disassociated
Mar  9 12:22:42 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Disassociated due to inactivity (4), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:0
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:0
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:0
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:26:46 hostapd: wl0.1: STA b4:0b:1d:69:84:ad IEEE 802.11: associated
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:26:46 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:26:46 hostapd: wl0.1: STA b4:0b:1d:69:84:ad RADIUS: starting accounting session A8FD3B4EF645298A
Mar  9 12:26:46 hostapd: wl0.1: STA b4:0b:1d:69:84:ad WPA: pairwise key handshake completed (RSN)

[Assistant]
Code:
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:27:54 hostapd: wl0.1: STA b4:0b:1d:69:84:ad IEEE 802.11: associated
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:27:54 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:27:54 hostapd: wl0.1: STA b4:0b:1d:69:84:ad RADIUS: starting accounting session A8FD3B4EF645298A
Mar  9 12:27:54 hostapd: wl0.1: STA b4:0b:1d:69:84:ad WPA: pairwise key handshake completed (RSN)
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:28:35 hostapd: wl0.1: STA b4:0b:1d:69:84:ad IEEE 802.11: associated
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:28:35 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:28:35 hostapd: wl0.1: STA b4:0b:1d:69:84:ad RADIUS: starting accounting session A8FD3B4EF645298A
Mar  9 12:28:35 hostapd: wl0.1: STA b4:0b:1d:69:84:ad WPA: pairwise key handshake completed (RSN)

Code:
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-46
Mar  9 12:29:21 hostapd: wl0.1: STA b4:0b:1d:69:84:ad IEEE 802.11: associated
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-46
Mar  9 12:29:21 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc B4:0B:1D:69:84:AD, status: Successful (0), rssi:-46
Mar  9 12:29:21 hostapd: wl0.1: STA b4:0b:1d:69:84:ad RADIUS: starting accounting session A8FD3B4EF645298A
Mar  9 12:29:21 hostapd: wl0.1: STA b4:0b:1d:69:84:ad WPA: pairwise key handshake completed (RSN)
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:0
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:29:50 hostapd: wl0.1: STA b4:0b:1d:69:84:ad IEEE 802.11: associated
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:29:50 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc B4:0B:1D:69:84:AD, status: Successful (0), rssi:-47
Mar  9 12:29:50 hostapd: wl0.1: STA b4:0b:1d:69:84:ad RADIUS: starting accounting session A8FD3B4EF645298A
Mar  9 12:29:50 hostapd: wl0.1: STA b4:0b:1d:69:84:ad WPA: pairwise key handshake completed (RSN)

Code:
Mar  9 12:34:24 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:0
Mar  9 12:34:24 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:0
Mar  9 12:34:24 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:0
Mar  9 12:34:24 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-49
Mar  9 12:34:24 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-49
Mar  9 12:34:25 hostapd: wl0.1: STA b4:0b:1d:69:84:ad IEEE 802.11: associated
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-49
Mar  9 12:34:25 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc B4:0B:1D:69:84:AD, status: Successful (0), rssi:-49
Mar  9 12:34:25 hostapd: wl0.1: STA b4:0b:1d:69:84:ad RADIUS: starting accounting session A8FD3B4EF645298A
Mar  9 12:34:25 hostapd: wl0.1: STA b4:0b:1d:69:84:ad WPA: pairwise key handshake completed (RSN)
Mar  9 12:35:19 hostapd: wl0.1: STA b4:0b:1d:69:84:ad IEEE 802.11: disassociated
Mar  9 12:35:19 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Disassociated due to inactivity (4), rssi:-48
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:0
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:0
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-40
Mar  9 12:40:00 hostapd: wl0.1: STA b4:0b:1d:69:84:ad IEEE 802.11: associated
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind B4:0B:1D:69:84:AD, status: 0, reason: Unspecified reason (1), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B4:0B:1D:69:84:AD, status: Successful (0), rssi:-40
Mar  9 12:40:00 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc B4:0B:1D:69:84:AD, status: Successful (0), rssi:-40
Mar  9 12:40:00 hostapd: wl0.1: STA b4:0b:1d:69:84:ad RADIUS: starting accounting session CACF6ADCBE3F3DCE
Mar  9 12:40:00 hostapd: wl0.1: STA b4:0b:1d:69:84:ad WPA: pairwise key handshake completed (RSN)
Mar  9 12:46:25 wpa_supplicant[2652]: eth2: WPA: Group rekeying completed with c8:7f:54:5e:a6:b4 [GTK=CCMP]
Mar  9 12:46:25 kernel: CFG80211-ERROR) wl_cfg80211_set_rekey_data :
Mar  9 12:46:25 kernel: seting gtk_key_info failed code=-23
Mar  9 12:49:14 hostapd: wl0.1: STA b4:0b:1d:69:84:ad WPA: group key handshake completed (RSN)
Mar  9 12:49:14 hostapd: wl0.1: STA 98:b8:bc:a5:73:a0 WPA: group key handshake completed (RSN)
Mar  9 13:46:25 wpa_supplicant[2652]: eth2: WPA: Group rekeying completed with c8:7f:54:5e:a6:b4 [GTK=CCMP]
Mar  9 13:46:25 kernel: CFG80211-ERROR) wl_cfg80211_set_rekey_data :
Mar  9 13:46:25 kernel: seting gtk_key_info failed code=-23
Mar  9 13:49:14 hostapd: wl0.1: STA b4:0b:1d:69:84:ad WPA: group key handshake completed (RSN)
Mar  9 13:49:14 hostapd: wl0.1: STA 98:b8:bc:a5:73:a0 WPA: group key handshake completed (RSN)


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: Asus DFS algorithm

Hello,

Long time lurker just got around to make an account to post a question. I learned a lot from the forums but just never got to a point where a search won't turn up the answer I need Anyway here's the issue:

I have a double AX11000 pro AiMesh setup (latest stock firmware) where everything works consistently with 160MHz backhaul at the unii4 channels (I73)

The 5G-1 interface can be set to 160MHz (and surprisingly my neighbors also use Asus routers and use 160MHz channels). At my location every few days there will be radar detected and the router moves to 80MHz. But the problem is that I haven't seen it ever moving back. From the older posts I see folks mention that they also don't see router moving back to 160MHz. But Asus's help articles do say the router "might" go back.

Here's a sample log:
Code:
Feb 27 02:18:13 wlceventd: wlceventd_proc_event(831): eth7: Radar detected
Feb 27 02:18:13 kernel: In wl_dfs_cac_notify_status chanspec 0xe932 DFS state 3
Feb 27 02:18:13 cfg_server: cm_updateChanspec call wl_chanspec_changed_action
Feb 27 02:18:13 cfg_server: event: wl_chanspec_changed_action_a103 of eid(3) of cfgs(3074)
Feb 27 02:18:13 cfg_server: current chansp(unit0) is 100a, shall_be_excluded:0, avbl:1.
Feb 27 02:18:13 cfg_server: current chansp(unit1) is e932, shall_be_excluded:0, avbl:1.
Feb 27 02:18:14 cfg_server: current chansp(unit2) is eea3, shall_be_excluded:0, avbl:1.
Feb 27 02:18:14 cfg_server: dump exclchans:
Feb 27 02:18:14 cfg_server: old wl0_acs_excl_chans:0x100c,0x190a,0x100d,0x190b,0x100e,0x190c
Feb 27 02:18:14 cfg_server: new wl0_acs_excl_chans:0x100c,0x190a,0x100d,0x190b,0x100e,0x190c
Feb 27 02:18:14 cfg_server: valid wl0_acs_excl_chans:0x100c,0x190a,0x100d,0x190b,0x100e,0x190c
Feb 27 02:18:14 cfg_server: old wl1_acs_excl_chans:0xd0b1,0xd9af,0xe3ab,0xefa3
Feb 27 02:18:14 cfg_server: new wl1_acs_excl_chans:0xd03c,0xd040,0xd83e,0xd93e,0xe23a,0xe33a,0xee32,0xef32
Feb 27 02:18:14 cfg_server: valid wl1_acs_excl_chans:0xd0b1,0xd9af,0xe3ab,0xefa3
Feb 27 02:18:14 cfg_server: old wl2_acs_excl_chans:0xd0b1,0xd9af,0xe3ab,0xefa3
Feb 27 02:18:14 cfg_server: new wl2_acs_excl_chans:0xd0b1,0xd9af,0xe3ab,0xefa3
Feb 27 02:18:14 cfg_server: valid wl2_acs_excl_chans:0xd0b1,0xd9af,0xe3ab,0xefa3
Feb 27 02:18:14 cfg_server:  wl_chanspec_changed_action: Need to restart acsd for AVBL update, static5G=0
Feb 27 02:18:14 rc_service: cfg_server 3074:notify_rc restart_acsd_acscli2
Feb 27 02:18:14 kernel: In wl_dfs_cac_notify_status chanspec 0xd028 DFS state 0
Feb 27 02:18:16 acsd: eth7: selected channel spec: 0xe12a (40/80)
Feb 27 02:18:16 acsd: eth7: Adjusted channel spec: 0xe12a (40/80)
Feb 27 02:18:16 acsd: eth7: selected channel spec: 0xe12a (40/80)

From Wifi analyzer on my phone I see my neighbors router reselect back 160MHz while mine stays 80, which is infuriating The DFS state also shows idle on my log:

Code:
DFS status: state IDLE time elapsed 0ms radar channel cleared by DFS channel 64/160 (0xEF32)

Any idea if it's a configuration issue? I have tried all of the options below on 5G-1

1. fixed 160MHz width , auto control channel or fixed
2. 20/40/80/160 , auto control channel or fixed

Current setup:

I do get the 2400+ mbps phy rate when 160 is enabled. First world problem I know but wondering if there's anything I can to make it better. Thanks!

[Assistant]
fast08 said:
...but wondering if there's anything I can to make it better.
Not really. It is what it is. Once RADAR has forced it to change channel the only scenario where it would voluntarily change again (back to the original or to a different channel) is if it sees that there's another channel that is significantly better than the one it's currently using. That's highly unlikely and not something I've ever seen happen myself.

Forgot to mention, after I manually toggle the 160 enable button on the UI, the wireless log shows a non-zero timer now:

Code:
DFS status: state In-Service Monitoring(ISM) time elapsed 198900ms radar channel cleared by DFS channel 64/160 (0xEF32)

What does this mean? In 3 minutes or so it will check radar again?

fast08 said:
What does this mean? In 3 minutes or so it will check radar again?
No, it simply means that the current chanspec (channel/bandwidth) has been active for 198 seconds.


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: Looking for more coverage, Range Extender or use Router?

I currently have a RT-AX86U (with merlin) located in my basement and would like add something on the second floor of the house. (would be running ethernet to connect them)
Is there any benefits or disadvantages to using a extender like the ASUS RP-AX58 over another AX router? Less range?
I'm guessing the RP is just plug and play where the router I would need to set up first and give me extra Ethernet ports (if anyone in the room where it would to use)

If a router would be the better option does it really matter what the specs are?
The rt-ax55 can be had for about 30-40 on eBay, if this is a bad choice to pair please suggest something else.

Thank you.

[Assistant]
I would get another RT-AX86U used off eBay. They are reliable units. AiMesh works best with 2x identical units. You don't need to setup anything on it. Reset to defaults and add as AiMesh node. See user experience with 2x RT-AX86U in recent thread here:

is it required Smart Connect enabled in order to have Wifi 6 enabled?
Hello, I have AiMesh with AX-86U (1 main and 1 node). I split 2.4 & 5ghz into two different SSID xxxx-2.4 & xxxx-5ghz. It's been reliable AiMesh, Wifi .. Does splitting 2.4/5Ghz to two different SSID make WiFi6 not working (as I heard Wifi6 needs both 2.4 & 5Ghz to work)? Do i need to enable...
www.snbforums.com

Wafflestyx said:
(would be running ethernet to connect them)
Since you plan to hard-wire the connection, it is hard to beat the reliability of a plain vanilla access point.

Tech9 said:
I would get another RT-AX86U used off eBay. They are reliable units. AiMesh works best with 2x identical units. You don't need to setup anything on it. Reset to defaults and add as AiMesh node. See user experience with 2x RT-AX86U in recent thread here:

is it required Smart Connect enabled in order to have Wifi 6 enabled?
Click to expand...
What is the down side to using different models?
Also, would it matter that one is merlin and the node is stock?


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: RT-AXE7800 (not collecting AiProtection data)

My RT-AXE7800 up to date (firmware 2.438 / Version : 3.0.0.4.388_25142-g8c68976) does not seem to be collecting or tallying any AI protection "hits"....
I have the protection turned on but dont seem to be getting any hits - my previous RT-AC3200 had countless number of tallied hits.

Am I missing something / failed to turn on a setting?
The 1 Risk is related to my disabling Web access from WAN (which I turn enable / disable as needed when traveling)....but it seems hard to believe the others are actually zero (given my past experience with the RT-AC3200)

[Assistant]
Not unusual to register 0 protection hits if you are careful with your web browsing habits and do not have port forward enabled.
As for that remote access enabled...DON'T!!! BIG security risk!!! You are safer using a VPN. Asus Instant Guard is great for Android and iOS devices. OpenVPN works but disable compression and enable both internet and intranet access. Wireguard also works well.

bushpilot said:
AI protection "hits"

You can test it here:

WICAR.org - Test Your Anti-Malware Solution!
The wicar.org website was designed to test the correct operation your anti-virus / anti-malware software. The name " WICAR " is derived from the industry standard EICAR anti-virus test file ,...
www.wicar.org

You have to disable your browser's Safe Browsing first. Most modern browsers have it enabled by default. The browser's protection will block the threats before the router and AiProtection won't register a hit. Perhaps the reason you don't see hits there, browsers got smarter over time. And there is no AI in AiProtection. It's a marketing name just like other Asus AiCloud, AiDisk, AiMesh, etc. Third party service by Trend Micro, not very effective with signatures updated once a month.

bbunge said:
Asus Instant Guard

thanks! I do understand there is a risk using ASUS's remote access.
Instant Guard is apparently NOT supported with the AXE-7800....I'll have to do some studying to figure out how to do this w/out using the OEM enable access from wan feature


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: One Solid Fix: Issues with Asus GT-AXE16000

Thanks to ASUS and Amazon, and a big headache, I found this forum!

As an attorney, I notice and am aware of the discussions regarding locked hardware and countries of authorized distribution. Sadly, some misinformation triggers some resolutions to be mistaken for illegal activity. This is not a post to hack or workaround, but to resolve a sad issue associated with Amazon and perhaps other retailers.
Amazon mixes inventory from multiple inbound sources, and getting a unit preloaded with firmware optimized for another country is possible. This does not mean the router is illegally licensed (although it can). In my case, my "open box" GT-AXE16000 was likely returned for this reason. Talking with ASUS, the firmware will lock out, change, or add options based on support within a given region. Thanks for their support.

My unit arrived and the EULA (End user license agreement) was for North America/USA.
My unit arrived with firmware version 3.0.0.4.388_24403 (the latest), although I did not note the longer number shown after this fix (3.0.0.4.388_24403-g48ccb61). My issue like other is I was NOT able to see or access the SSID for the 5GHZ-1 band, and some selections (namely control channel options) were not showing as they were following my steps to resolve.
Navigating to the US support site [https://rog.asus.com/us/support/download-center/], and not the general support site that the router interface may direct you to [https://rog.asus.com/networking/rog-rapture-gt-axe16000-model/helpdesk_download/] I downloaded and applied the firmware file.
Whether this was a corrupt firmware, different firmware, or the new load made some other change to allow proper use of the 5GHZ-1 band is up for guess, but it worked nonetheless.
While yes a manufacturer can restrict sales and support of certain products for a variety of reasons, I would suggest that if ASUS wanted to in this case, the US firmware would not load onto an unapproved device. While I did not ask ASUS, I do not know anything about devices that ship with a EULA from other countries.

I hope this helps someone else.

[Assistant]
AlphaX said:
Navigating to the US support site [https://rog.asus.com/us/support/download-center/], and not the general support site that the router interface may direct you to [https://rog.asus.com/networking/rog-rapture-gt-axe16000-model/helpdesk_download/] you can find the firmware file (for the US!) It is named the same, but only on the US site will you get all the US features.
This is incorrect. The firmware you download from the US Asus site is exactly the same as the ones you can download from other country's Asus websites. There is no "US version" of the firmware. Compare the checksums of the two files you linked to, here and here. They are the same. The region is set on the device when it is manufactured and is not part of the downloadable firmware.

AlphaX said:
I was NOT able to see or access the SSID for the 5GHZ-1 band

Not only the firmware is exactly the same, but also 5GHz_1 band channels are largely the same in multiple regions.

Well, what would you suggest the Asus tech did or advised in my session that would have corrected the issue? I don't dispute that two sites may have the same version and even the same code, but something was surely different in what was loaded before I received it and post install of the new file firmware download. The available settings as well as the viewing of the SSID sure changed.


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: AIProtection /w Diversion and Skynet

Using Skynet and Diversion does AI Protection still serve a purpose?

Thanks

[Assistant] Diversion is DNS blocker, Skynet is IP blocker, AiProtection can catch some things based on signature in packets... so yes, it may add extra layer of protection, but also increases the chance of false positives and requires data sharing to Trend Micro.


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: WiFi extender always showing as wired

Hi, I have the BE30000 (BQ16 Pro) setup with one node as router and two satellite nodes. I also have a Netgear Orbi outdoor WiFi extender. This all works fine, but the Orbi always shows as wired connecting to the ASUS mesh network. The issue with this, for some reason it always connects to the main router, and I need it to connect to a satellite that is closer for better performance. I know that it should hit the particular satellite due to how it has worked with my older Orbi network and a WiFi7 tp-link setup I had for a few months before ditching it for ASUS. If it showed as wireless I’d be able to bind to the correct AP. Everything is running the latest firmware. I’ve rebooted everything, etc, always comes back as wired and connected to the router. Any thoughts or suggestions?

BTW, I do occasionally get another wireless device show as wired, but those usually clear up upon reboot.

[Assistant]
Chris000 said:
Hi, I have the BE30000 (BQ16 Pro) setup with one node as router and two satellite nodes. I also have a Netgear Orbi outdoor WiFi extender. This all works fine, but the Orbi always shows as wired connecting to the ASUS mesh network. The issue with this, for some reason it always connects to the main router, and I need it to connect to a satellite that is closer for better performance. I know that it should hit the particular satellite due to how it has worked with my older Orbi network and a WiFi7 tp-link setup I had for a few months before ditching it for ASUS. If it showed as wireless I’d be able to bind to the correct AP. Everything is running the latest firmware. I’ve rebooted everything, etc, always comes back as wired and connected to the router. Any thoughts or suggestions?

BTW, I do occasionally get another wireless device show as wired, but those usually clear up upon reboot.
Click to expand...

First, client lists in ASUSWRT can be unreliable and can only be ignored.

Crazy thought here... maybe the Orbi extender remembers the exact signal (not SSID) that you set it up to extend(?) Maybe temporarily disabling radios except on the desired node and then setup the Orbi to extend that node signal would yield what you want(?) Maybe this is a dumb idea!

OE

Thanks OE, that’s an interesting idea, to disable the 5Ghz radio on the node it is hitting to see if it connects elsewhere. I don’t think this is possible because it is hitting the main router, I don’t see an option to disable particular radios just on that node, as I do on the satellite nodes. One more thing, the extender does not show up at all in the ASUS web interface, only on the mobile apps (iOS and Android). Very strange and buggy stuff.

I don’t want to, but maybe I’ll factory reset the extender and hope it connects to a closer AP. Even if that works, it would be good for it to show are wireless so that I can bind it.


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: New AIMesh system, no clients connect to AIMesh Node? GT-AX600 + AX68U

Yesterday I installed fresh/new GT6000 (AP) + AX68U (node). It worked great, yesterday! Now I'm noticing that no clients connect to the node, even when 10 to 20 ft away through 1 interior wall. The AP is on the extreme end, of the house 2 floors down (same locations as my prior AC86Us; worked great in same spots)
Ethernet backhaul
Node's 2.4g is OFF, AP 2.4g MAC filter for 5 specific devices that require 2.4g. All other devices forced to 5g (this is the same as my prior AC86U setup)

I even changed a few things trying to get the Node to connect to the devices... no go!?
AP 5G signal strength reduced to Balanced (mid-level, default is 2 level up on Performance)
Roaming assistant to -60 (default -70)
3 devices in Node's line of sight are not connecting to AP (AP signal is far too weak there); not "locking" to AP so seems not a roaming issue?

help please

[Assistant]
Turn the WIFI back on and use the defaults for WIFI and AiMesh. Then wait for the system to settle in. May need to run overnight.

bbunge said:
Turn the WIFI back on and use the defaults for WIFI and AiMesh. Then wait for the system to settle in. May need to run overnight.
Wifi is on, I only turned of the 2.4g radio on the Node. No reason to have it on - it will only add to the interference.
It did run overnight, and it was working immediately yesterday when first installed... running it over night was when it "broke"

Livin said:
Wifi is on, I only turned of the 2.4g radio on the Node. No reason to have it on - it will only add to the interference.
It did run overnight, and it was working immediately yesterday when first installed... running it over night was when it "broke"
Hello, I am facing the same problem with same exact model and I have also turned 2.4 off. Did you find a solution for the problem?


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: AX11000 pro router with AXE mesh nodes

I have a dual AX11000 pro setup that's working fine especially with the backhaul on UNII4 channels (5.9 GHz , 160MHz with no DFS). There was a post here a while ago regarding someone wanting to add Wifi6e mesh node to a Wifi6 system to extend the network to 6GHz. I happen to have an Asus ET12 for a few days and tried adding it to the system as AiMesh. I forgot to take screenshots but here's what I found in case someone else wonders:

1. It does work to an extent - ET12 is detected and can be added as an AiMesh mode. Main router UI shows ET12 having 3 Radios that can be toggled (2.4, 5G, 6G)
2. However the 6-GHz is selected as the dedicated backhaul without way of changing it. I tried setting backhaul priority to ethernet but that does not release the 6G radio from backhaul.
3. There's seemingly no way to use Ethernet backhaul on *only* the ET12 - either the entire system is ethernet backhual or it's going to be completely wireless.

Connecting ET12 as a wired AP certainly works and I enabled 6GHz radio only to test the connection around the house.

On a different note - the 6GHz band isn't really working that well in my house. At the same spot where I put the AX11000 pro mesh node (main on 2nd floor, mesh node down stairs in the garage), the 6GHz signal dropped off almost completely while the 5G-2 at channel 173 can maintain phy rate 17-1900mbps. Unfortunately looks like Asus and other router manufactors are all about done with the UNII-4 channels. I don't see the ET12 and AXE16000 supporting this band.

[Assistant]
6GHz frequencies have the shortest wavelength and thus travel/penetrate the least effectively. Use it for up-close, wide bandwidth connections.

OE

OzarkEdge said:
6GHz frequencies have the shortest wavelength and thus travel/penetrate the least effectively. Use it for up-close, wide bandwidth connections.

OE
Yea .. looks like I'm going to stick with AX11000 pro for a while for the 5.9GHz backhaul which weirdly fits my bill - it's has higher penetration than 6GHz and is not crowded at all.
May be I will look into wifi 7 in several years.


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: Asus AX86U Pro - Guest Network Pro in AP Mode - no internet

I have my AX86u Pro in AP Mode. I tried to use the Guest Network pro feature and created a customized network. Clients can connect to the guest network but it couldn't obtain IP address. Is there any way to make it work or should I be in router mode for Guest Network Pro to work properly?

Firmware version: 3.0.0.6.102_34336

[Assistant]
Where is the DHCP server being hosted ?
What else is on the network ? ISP router/modem in router mode or pass through ?

degrub said:
Where is the DHCP server being hosted ?
What else is on the network ? ISP router/modem in router mode or pass through ?
DHCP is on the gateway(router)

modem -> router -> ax86upro(ap mode)

Which Guest Network Pro preset are you using? And how is it configured?
If the Guest Network Pro option Use same subnet as main network is available in the Guest Network Pro network you have created? If so is it enabled or disabled?

Unfortunately Guest Network Pro has a number of quirks and oddities. Somethings with Guest Network Pro just don't operate as expected or desired.


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: iOS devices stop responding to network for up to 30 seconds

Hi All,

I'm trying to troubleshoot an issue that has seemingly cropped up lately where my iPhone 16 Pro Max and iPad M4 Pro on iOS 18 stop responding to the Wi-Fi network for up to 30 seconds. It will eventually kick in if I let it sit.

Router: GT-AXE16000 with Asus-Merlin 3004.388.8_4
Network: iOS devices are connected to the 6Ghz and 5Ghz, they roam back and forth using Smart Connect based on signal strength (this has seemingly worked well).
iOS: Private Wi-Fi Address is off

When the issue occurs, the following shows up the in the router system log:

Feb 17 16:14:16 wlceventd: wlceventd_proc_event(695): eth9: ReAssoc <Mac Address>, status: Successful (0), rssi:-60
Feb 17 16:14:58 wlceventd: wlceventd_proc_event(645): eth8: Deauth_ind <Mac Address>, status: 0, reason: Disassociated due to inactivity (4), rssi:-54
Feb 17 17:03:06 wlceventd: wlceventd_proc_event(685): eth8: Auth <Mac Address>, status: Successful (0), rssi:0
Feb 17 17:03:06 wlceventd: wlceventd_proc_event(695): eth8: ReAssoc <Mac Address>, status: Successful (0), rssi:-70
Feb 17 17:03:28 wlceventd: wlceventd_proc_event(645): eth9: Deauth_ind <Mac Address>, status: 0, reason: Disassociated due to inactivity (4), rssi:-60
Feb 17 18:40:36 wlceventd: wlceventd_proc_event(695): eth9: ReAssoc <Mac Address>, status: Successful (0), rssi:-70
Feb 17 18:41:12 wlceventd: wlceventd_proc_event(645): eth8: Deauth_ind <Mac Address>, status: 0, reason: Disassociated due to inactivity (4), rssi:-64
Feb 17 20:01:58 wlceventd: wlceventd_proc_event(685): eth8: Auth <Mac Address>, status: Successful (0), rssi:0
Feb 17 20:01:58 wlceventd: wlceventd_proc_event(695): eth8: ReAssoc <Mac Address>, status: Successful (0), rssi:-86
Feb 17 20:02:08 wlceventd: wlceventd_proc_event(645): eth9: Deauth_ind <Mac Address>, status: 0, reason: Disassociated due to inactivity (4), rssi:-83
Feb 17 20:04:55 wlceventd: wlceventd_proc_event(662): eth8: Disassoc <Mac Address>, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 17 20:04:55 wlceventd: wlceventd_proc_event(645): eth8: Deauth_ind <Mac Address>, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Feb 17 20:09:45 wlceventd: wlceventd_proc_event(685): eth8: Auth <Mac Address>, status: Successful (0), rssi:0
Feb 17 20:09:45 wlceventd: wlceventd_proc_event(722): eth8: Assoc <Mac Address>, status: Successful (0), rssi:-86
Feb 17 20:58:33 wlceventd: wlceventd_proc_event(695): eth9: ReAssoc <Mac Address>, status: Successful (0), rssi:-60
Feb 17 20:59:02 wlceventd: wlceventd_proc_event(645): eth8: Deauth_ind <Mac Address>, status: 0, reason: Disassociated due to inactivity (4), rssi:-48

I changed Wi-Fi DTIM Interval from 1 to 3 and disabled Universal Beamforming based on some threads out there, but no luck with fixing the issue.

Perhaps it's Smart Connect rules, but I don't recall this happening before or at least it wasn't this noticeable. The main goal with this was to keep the devices on 6Ghz, as without it they would keep falling back to 5Ghz and never switch back to 6Ghz.

If anyone else is running into this same issue or has some ideas, thanks in advance.

[Assistant]
Looks like some of the RF power levels are marginal and the radio in the IOS device is not being heard well enough by the AP. Likely that is the 6GHz radio as it does not penetrate obstacles (walls, furniture , etc) very well if at all. 5GHz band is a little better - can usually penetrate 1 gypsum board wall, but not 2. IOS devices will cling to a radio even if they cannot really talk to it.

If you have direct, clear line of sight to the AP antennas, does the same behavior occur ?

What is the wifi environment - neighbor's signals overlaying yours ?

Yes, turn off smart connect and set your 5 GHz radio to 80 MHz wide band, 6 GHz to 80 or try 160, and 2.4 GHz to 40 or 40/20 MHz. Should be more than enough available bandwidth for IOS devices at those settings.

You can't do anything about the wifi radios in the IOS devices. All you can do is position additional APs where the signal from the IOS device falls off too far. Usually shoot for -65 dB RSSI. In ASUS devices you don't have very good control over RF TX power, so you have to be careful of overlap between the main wifi router and the node wifi .

degrub said:
2.4 GHz to 40 or 40/20 MHz. Should be more than enough available bandwidth for IOS devices at those settings.

Apple does not support 40MHz channels in 2.4, so better perhaps to keep 2.4 at 20MHz channel widths...

I had the same issues with 2.4/5 Ghz on AX86 (Pro), but wasn't able to figure it out. I just put Apple devices on 2.4Ghz only.


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: Issue with selective VPN Routing on ASUS GS-AX3000 (WireGuard & VPN Fusion)

Hi everyone,

I’m setting up a VPN for my home network using my ASUS GS-AX3000 router (firmware version: 3.0.0.4.388_23088). I’ve configured a WireGuard VPN connection through the router’s VPN Fusion feature, and I want to route only specific traffic through the VPN while leaving the rest to use my regular ISP connection via WAN for every device in network.

To test this setup, I limited the VPN configuration to route only traffic for 104.19.223.79/32 and 104.19.222.79/32 (the IPs for WhatIsMyIPAddress) through the VPN by setting these in the Allowed IPs field. I expect the following behavior:
When I visit WhatIsMyIPAddress, it should show the VPN server’s IP.
For all other websites, it should show my ISP’s IP.
When I set Allowed IPs to 0.0.0.0/0, everything works as expected—all traffic is routed through the VPN server (a DigitalOcean droplet in the UK). However, when I restrict Allowed IPs to only 104.19.223.79/32, 104.19.222.79/32, traffic to these IPs works fine, but all other traffic fails—devices lose connectivity entirely for anything outside the specified IPs.

What I suspect:
When I configure VPN Fusion and assign a device to use a specific VPN configuration, the device does not fallback to the WAN connection if it cannot communicate with the assigned VPN. This means that if the destination IP is not included in the VPN’s Allowed IPs, the device effectively loses connectivity and cannot access the internet.
I would greatly appreciate any advice or insights on how to fix this behavior or configure VPN Fusion to allow fallback to WAN for non-VPN traffic. Thanks in advance for your help!

[Assistant]
By the way, I would like to mention that if I use the same configuration in a WireGuard client on my laptop (instead of on the router), it works exactly as I expect.
Only the connection to the specified IPs is routed through the VPN, the rest of the traffic uses the WAN.

So I think, the problem here is how ASUS’s VPN Fusion firmware assigns a specific VPN configuration to devices. It seems that when a device cannot communicate through the assigned VPN config, it does not fallback to the WAN connection. Not sure if there is a workaround to this, but I'd like to hear your opinion.

I set up VPN Fusion with a Nord an Open VPN config and unchecked the "all devices" button. Then I added a single device in the box below it - my Firestick. That device runs on the Nord connection while everything else does not.

The reason it doesn't fall back may be related to it automatically getting a manual DHCP and MAC Binding. At least mine did. I never setup that up manually, once I set it up under VPN Fusion it showed up that way.

Edit I just tested by adding my phone to another VPN Fusion setup, it it manually bound my DHCP and MAC to it, too. Maybe that's it.

I'd like to know more if anyone else can chime in.

I achieved what I want by configuring VPN Fusion to route all local traffic to my Mac mini, and I set up the actual offshore VPN setup to my Mac mini where it orchestrates the network traffic and decide what goes to my regular ISP and what goes to remote VPN.

However I did not like this solution. As it means every traffic in my home network now has to be relayed to Mac mini, which causes double routing. It also completely destroys my internet speed which I am not sure why yet. I really want this VPN Fusion thing work


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: Trend Micro...talks a lot

Got NextDNS running and I was shocked at how many times Trend Micro is mentioned because I have just the AI threat Protection turned on.

I turn the filter off for just a minute every day to let it update and put the wall back up.

Tons of traffic blocked by just OISD and HaGeZi - Multi PRO++

Just putting that out there for someone that might want to know.

[Assistant]
That URL to Trend Micro is how AiProtection is evaluating potentially malicious URLs you are visiting from your devices. Might as well turn it off.

dave14305 said:
That URL to Trend Micro is how AiProtection is evaluating potentially malicious URLs you are visiting from your devices. Might as well turn it off
I learned something new today. I think I'll shut it off then because it's eating my free 300k queries.

But...your saying Trend evaluates every URL accessed through the router?

I think you are and I'm going to turn it off now.

Thanks

Currently Studying said:
But...your saying Trend evaluates every URL accessed through the router?
Not many people take the time to read the AiProtection notice, and the links it contains, that they agree to when enabling AiProtection. Yes, AiProtection will generally scan and collect data on every web link/IP address you visit. That information may be transmitted back to Trend Micro/Asus. Trend Micro evaluates the link/website for malware.
Trend Micro End User License Agreement
TrendMicro Privacy Policy
Privacy and Personal Data Collection Disclosure

In addition to disabling AiProtection, make sure to hit the Withdraw button under Advanced settings > Administration > Privacy (or Policy).


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: XT8 appears as RT-AX95Q instead of ZenWifi AX in web GUI and will not mesh

I have a pair of hardware version 1 ZenWiFi XT8 units.

I was having a hard time updating one unit's firmware past version 3.0.0.4.386.25790 (which may be the version it came with). Following suggestions, I did a hard reset of the units in an attempt to update the firmware.

However, after the hard reset, the unit that had a hard time with firmware updating identifies itself now as RT-AX95Q whereas the other unit remains ZenWiFi AX. (See attached screenshots from the web GUI.) Further, the RT-AX95Q unit does not have an AiMesh option and the ZenWiFi AX unit cannot detect it as a mesh node.

In case it matters. I used the Mac version of the ASUS Firmware Restoration app and updated the RT-AX95Q unit manually with the most recent version of firmware 3.0.0.4.388_24621.

Anyone has any suggestions on how to get the RT-AX95Q unit to play nice?

Edit: typo.

[Assistant]
Interesting way it identifies itself via two IDs! Asus…

If you’re willing to try Merlin, there’s a Gnuton version for the XT8/RT-AX95Q. Maybe that will help get your Mesh, stability (and sanity) back?

EDIT; link to the list of gnuton releases.

jksmurf said:
Interesting way it identifies itself via two IDs! Asus…

If you’re willing to try Merlin, there’s a Gnuton version for the XT8/RT-AX95Q. Maybe that will help get your Mesh, stability (and sanity) back?

@jksmurf I am guessing that involves another round of hard reset and using the firmware restoration app to upload the Merlin firmware on both units? Do you know if one can still use ASUS's iOS app to manage the network with Merlin?

woozy-wave said:
@jksmurf I am guessing that involves another round of hard reset and using the firmware restoration app to upload the Merlin firmware on both units? Do you know if one can still use ASUS's iOS app to manage the network with Merlin?
As regards reset, a hard reset is strongly recommended after a change from stock to any alternative FW. I say “alternative” but it’s very much Asus-with-enhancements.

As regards mechanism for updating, you should just be able to update over what you have now, using the WebGUI. Worst case, use the FW restoration utility but it’s not normally necessary.

As regards the App, while I do use it to look at the network from time to time, I believe Merlin has noted on a number of occasions it is not supported due to incompatibilities arising from changes to the stock FW made by AsusMerlin, so unfortunately you’d probably lose some of that functionality, if it’s important to you. I’ll see if I can find the statements on it. It’s closed source proprietary I believe.

EDIT; see this thread on compatibility between AsusMerlin and the App. It seems that it retains “85% -90% functionality” according to one user, so it may well be sufficient for your purposes.


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: Adding a 3rd Router to Aimesh Network (but not as a node)

Hi all...I currently use an AX11000 as my main router and I have an RT-AC86U as an Ai-Mesh node. I read where I could have a dedicated gaming router (3rd router in my case) so I purchased a RT-AX1800S for that specific task. My problem is that I do not understand how to add this 3rd router to my current network, but not as a node to the Ai-Mesh network) so I can use it exclusively for VR Gaming.

Thank you all in advance

[Assistant]
0) What is your setup ? 1) ISP router LAN ---> ASUS AX11000 WAN port ? or 2) is the AX11000 WAN port connected to an ISP modem or 3) ISP modem/router in Bridge mode ?

What issue are you trying to solve ?

You can add it as an AP attached via a long ethernet cable back to the AX11000 or as a router attached to a LAN port on the AX11000 or as a router attached to the ISP modem/router either in LAN or DMZ

Assuming you are using cables and not wireless for the lowest latency.....

1) Simple - Get a long ethernet cable (cat6) and connect the WAN port of the AX1800s to a LAN port on your main router (double NAT), OR
2) Get the same cable and plug it into the DMZ port of your ISP router if it has one. Beware, as that will put that router directly exposed to the internet the same as the ISP router ( if you have). Configure accordingly. You could also connect to a LAN port if available. OR
3) Get the same cable and plug one end into a LAN port on your AX11000 and the other end into a LAN port on the new AX1800. OR
4) Get the same cable, plug one end into the AX11000 LAN port and the other end into your PC LAN port. Lowest possible latency. OR
5) Using the same cable, plug one end into the DMZ port of the ISP router and the other into the LAN port on your PC. Make sure your PC firewall is correctly configured as your PC will be exposed to all the bad guys on the internet trying to get in.

If you are thinking to use wireless for all the connections - forget it . You likely have too much RF signal in the house and adding another WIFI source will only make it worse with overlap. You would have to set the AX1800 in Media Bridge mode to act as a wifi extender with all those issues. Otherwise, it will have to be another node on your AiMesh.

So what did this other site say about how to install the additional wifi router ?

glockstr said:
I currently use an AX11000 as my main router

Why don't you dedicate one of the 5GHz radios to the VR set? GT-AX11000 has 2x 5GHz radios. This RT-AX1800S is not needed and being the cheapest AX-class Asus router one can find - perhaps not good for gaming. Folks with VR sets usually look for Wi-Fi 6E/7 routers with 6GHz radios. What you need is dedicated Access Point.

Tech9 said:
Why don't you dedicate one of the 5GHz radios to the VR set? GT-AX11000 has 2x 5GHz radios. This RT-AX1800S is not needed and being the cheapest AX-class Asus router one can find - perhaps not good for gaming. Folks with VR sets usually look for Wi-Fi 6E/7 routers with 6GHz radios. What you need is dedicated Access Point.
Yes, I do, I'm asking HOW to do that, step by step. Perhaps I'm not understanding but 2 of my routers are WiFi 6, the AX11000 & 1800s. Sorry, I just don't know enough to figure it out, you would think that with 35Years experience in IT including 23 years as a Consultant / Software Developer I would know this stuff..


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: Matching nodes for a Rt-AX88

I’m currently running a RT-AX88u with 3 x RT-AC86u nodes. Obviously with the setup, WiFi 6 won’t be available from the nodes so I’m looking to replace them. Are there any recommendations or will any RT-AX models be ok as a node?

Thanks

[Assistant]
Best chance of success with AiMesh is to have all devices the same exact same model and running identical firmware.
Are you using wired (ethernet) backhaul or wireless ?
Unless your clients all support wifi 6 or higher AND your RF environment allows you to use 80 MHz or 160 MHz (need clear line of sight) channel width, moving to wifi6 radios would only incrementally improve your local bandwidth.

What is your ISP service down/up bandwidth ?

Moving to AX with supporting clients would only increase your local transfer bandwidth, not the ISP bandwidth, so that would become the new bottleneck. Most home use setups are not able to saturate a 1 Gbit/s local link, much less a 1Gbit/s ISP link. Internet servers, many times, limit clients to 100 Mbit/s bandwidth or less. 100 Mbit/s works amazingly well for most residential setups but can be saturated locally. So 1 Gbit/s lan and wifi is usually more than adequate for residential.

As long as the APs/wifi routers are not directly facing the internet, EOL support doesn't really matter. For staying on AiMesh with best chance of success, it may if the primary router's firmware is updated and breaks the mesh support. You could also just run them as APs instead of mesh nodes in that case. Most clients are 2x2 radios, so more than that on the AP doesn't change anything.

Ah right, it’s probably not going to make any difference then. All of the nodes are connected via Ethernet, Download speed is only about 370Mbps and upload is 38Mbps.
I have a few devices which are WiFi6 compatible but I’m assuming that it’s pointless upgrading with the low speed of the ISP.
So if I was to upgrade, you would recommend having all RT-AX88u’s?

Avinitlarge said:
Ah right, it’s probably not going to make any difference then. All of the nodes are connected via Ethernet, Download speed is only about 370Mbps and upload is 38Mbps.
I have a few devices which are WiFi6 compatible but I’m assuming that it’s pointless upgrading with the low speed of the ISP.
So if I was to upgrade, you would recommend having all RT-AX88u’s?
No. The devices do not have to be the same model. In your case they should all be AX with 5 GHz capable of 160 MHz (unless 80 MHz works OK for you). AX86U or AX86S would be a good match. Other Asus AX would also work.


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: BE30000/BQ16 Pro - Devices dropping to 2.4Ghz, will not reconnect to 5Ghz

Hi, fairly new system, as the subject states, many devices across all 3 APs dropped from 5GHz to 2.4, and I am having great difficulty getting them back. Essentially I have to take them offline, delete the record of the device in the offline client list, and reconnect them to get them back to 5GHz. rebooted the network, no help. A simple device reboot, which normally would work is not currently. I was running on channel 36, when this happened I noticed some interference, have switched to 161, still having the issue. Now I am back on 48 as it shows clear, devices still not switching back to 5GHz. Also kicked it down to 4Mhz band. It seems like corrupt entries in the client DB in some manner. Latest firmware across the board, happened to a Windows 11 PC, Echo devices, Ring cameras, some of these mere feet from an AP. Any thoughts?

[Assistant]
wireless client decides when and which radio to connect to. period. And when to drop a radio connection.
For the IOT devices, see other recent threads about a specific option of IOT network preconfigured. It is intended to help with compatibility issues somewhat. i'm looking for the thread from earlier today.

New BE-98 Pro
I just setup a BE98 Pro. Stock updated firmware. The only issue was some, not all of iOT devices did not connect to 2.4. I used guest network pro and created an iOT network called Idiots under the original SSID for 2.4. As soon as I did that all of the 2.4 iOT devices that did not connect...
www.snbforums.com

You can also play with MAC filtering in the AP portion of the configuration. May or may not work to blacklist (exclude) on one band and whitelist on desired.
Many have luck restricting IOTs to the 2.4 GHz band as this is all the bandwidth needed See above. Otherwise, Set WPA2 for max compatibility, 40 MHz or 40/20 or 20 MHz channel width for more stability and coverage distance.

And avoid using DFS channels if available.


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: Problem with registering hostname to Asus router

I've just setup bridged network to pass my pc (Windows 11) network also to AppleTV sitting beside.

Then I need to setup static IP for my PC so that it can continue to use network

However, after this setup, the router didn't take that PC hostname anymore so I cannot use hostname to access other network device to/from that PC. From my research on web, this is because the PC is not sending/requesting DHCP request so the hostname will never push to router.

May I know what is the option for me to use hostname instead of IP to access to/from that PC settings up bridged network?

Thanks

[Assistant]
If you are assigning a static IP address to a client it is a good idea to leave room in the DHCP pool for the static address. Otherwise, in most home networks it is best to just use DHCP to assign addresses.
Asus routers will in time gather info for host name to IP. Their network manager can be wonky.

bbunge said:
If you are assigning a static IP address to a client it is a good idea to leave room in the DHCP pool for the static address. Otherwise, in most home networks it is best to just use DHCP to assign addresses.
Asus routers will in time gather info for host name to IP. Their network manager can be wonky.
My problem is if it's possible for router to take this PC's hostname if this PC set to use static IP but not using DHCP

As @bbunge mentioned, no matter what you do, it has the capability to be a bit wonky! But if you try Tools>Other Settings>Wan: Use local caching DNS server as system resolver (default: No): Yes
You might improve your chances!
*On a PC the hostname will be what you have set on the PC, and not any "friendly" name you assign using the router.


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: Dyson Fans won’t connect to Asus WiFi?

I have 3 Dyson cooling fans (TP12) in my house and are 3 were successfully connected to the IoT guest wireless network in my Asus Rog GT-BE98 Pro.

However this weekend all 3 fans stopped connecting to WiFi. I reset the network connection in the fans and tried to reconnect but the connection is TIMING OUT each time and unable to connect. This is happening on all 3 fans.

Previously my 5 GHz SSID would appear under available networks but all I’m seeing now is the IoT guest network and the 2.5 GHz. Tried connecting to both and no luck.

I’ve rebooted my modem and router and also unplugged the fans to no avail.

Could a recent Asus firmware update possibly changed a previous setting or should I adjust sobering under the “professional” tab? Not sure how to get the fans to connect to WiFi again so I can use them via the Dyson app.

Thanks.

[Assistant]
Is the channel select set to AUTO in the Asus for either/both of the 2.4 GHz and 5 GHz ?
If you update firmware, cleanest method is to factory reset and manually configure. Uploading a backup config can lead to issues.
Don't mess with the PRO pages unless you know what you are doing. IOTs are pretty simple devices.

Poseidon said:
I have 3 Dyson cooling fans (TP12) in my house and are 3 were successfully connected to the IoT guest wireless network in my Asus Rog GT-BE98 Pro.

However this weekend all 3 fans stopped connecting to WiFi. I reset the network connection in the fans and tried to reconnect but the connection is TIMING OUT each time and unable to connect. This is happening on all 3 fans.

Previously my 5 GHz SSID would appear under available networks but all I’m seeing now is the IoT guest network and the 2.5 GHz. Tried connecting to both and no luck.

I’ve rebooted my modem and router and also unplugged the fans to no avail.

Could a recent Asus firmware update possibly changed a previous setting or should I adjust sobering under the “professional” tab? Not sure how to get the fans to connect to WiFi again so I can use them via the Dyson app.

Thanks.
Click to expand...

Where are you viewing 'available networks'?... on the client?

Do your devices support the current 5.0 control channel? If not, they won't see the 5.0 WLAN/SSID.

OE

degrub said:
Is the channel select set to AUTO in the Asus for either/both of the 2.4 GHz and 5 GHz ?
If you update firmware, cleanest method is to factory reset and manually configure. Uploading a backup config can lead to issues.
Don't mess with the PRO pages unless you know what you are doing. IOTs are pretty simple devices.
Yes the channel select are set to “auto” and yes I did perform a factory reset after the latest firmware update.

Should I select a channel manually instead of auto?


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: Robot vaccum speaking at nights

Hi!

I have an Asus RT-AC68U with latest official firmware from Asus.

I noticed that my Xiaomi Vaccum-Mop 2 Ultra speak alone at nighttime. It’s disturbing because it even makes me asleep.

I looked into the Asus log and it’s showing this message for the vaccum MAC.

syslog: wlceventd_proc_event(494): eth1: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0

What can be causing this?

[Assistant]
This is not an ASUS issue. Ask Xiaomi on their forum if they have one.

Disable "Smart Connect" on the router and see how it goes.

jfim88 said:
Hi!

I have an Asus RT-AC68U with latest official firmware from Asus.

I noticed that my Xiaomi Vaccum-Mop 2 Ultra speak alone at nighttime. It’s disturbing because it even makes me asleep.

I looked into the Asus log and it’s showing this message for the vaccum MAC.

syslog: wlceventd_proc_event(494): eth1: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0

What can be causing this?
Click to expand...
He’s just lonely and want to speak


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: How to force an update on Client List

Dear Sir/Mdm,

For all ASUS router I've used, it seems the Client list sometime misbehave.
ie it is not updating properly.

e.g. My client device is connected to the Wifi but the router client list is not showing that its connected.

I've tried using the ASUS AX86U_PRO as the AIMESH router and AX11000 as the AIMESH node. The client lists seems not updating. It is using the latest firmware from the merlin.

I've also tried the ASUS ZenWifi AX, it also exhibit the same. Sometime it works real-time but sometime it dont work. For ZenWifi, I am using the latest stock firmware.

It seems client list update is not accurate. Is there a way to force the client lists update so that it appears to be the latest for ease of debug and to really know who is connected to the network. Else its giving false information about the clients connected to the network. This is undesirable.

Best Regards,
Wee-How

[Assistant]
If you look at the system log, you will find that the device deauthenticated. Meaning left the house and no longer connected to the wifi. But the client list still listed as being connected and it can also display the Wifi signal strength. Even if you use "refreshes", it will still show the device connected. How can such basic bugs exists ?Is there a way to force update the client list ? Can the developer of this help to have it implemented so that we can force a clean up and re-connect all the valid devices in the network?

Also, to get the updated client list, you need to reboot the AIMESH main node. That's not proper. This is a very basic bugs.

Known issues with Client List in all Asuswrt versions, not very reliable tool, it is what it is. All fixes are usually temporary until you change something and it goes back to inaccurate or stuck state.


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: AiMesh Router Node Maximum

Hi,

Sorry if this has been posted before but I haven't seen it mentioned anywhere.

As you may know there's a hard limit of 9 nodes in an Asus AiMesh network. Adding any more gives the error "The limit on the number of AiMesh nodes is 9. Currently your system has reached the maximum".
Today I tried to add a new AiMesh Node and it said I'd hit the maximum when I hadn't. I assumed there's a counter and it had become incorrect due to earlier topology changes I'd made.

It seems that not only is there a counter but it can be changed via SSH/Telnet. I didn't need to currently do that as I was reinstalling an existing node but I will try this in the future when we need to add more.
The config value is "cfg_recount" and it should be set on the AiMesh master to the number of Nodes installed. It's set to zero on the nodes.
To view the current value run "nvram show | grep 'cfg_recount' "
To change it simply run "nvram set cfg_recount=[number of nodes] | nvram commit".

Not only that but there seems to be a maximum as well, which is stored in "cfg_re_maxnum". Unlike the count this is stored on all Nodes as well, but not sure if it's needed.
To view the current value (which defaults to 9) run "nvram show | grep 'cfg_re_maxnum' "
To change it run "nvram set cfg_re_maxnum=[number of nodes] | nvram commit".

Has anyone else got any experience of changing these two values? How many nodes can an AiMesh run with, assuming mostly ethernet backhaul?
I am looking forward to testing this and will report back.

[Assistant]
I did some more testing with this.
These settings are reset on reboot. The settings cfg_relist and cfg_relist_x hold the Node list which cfg_recount calculates on reboot.

Unfortunately when I tried to change these settings it cleared them as they contain < characters. So be careful!

In the end I recreated the Mesh which fixed the issue

im having the same issues from the multiple testing, removal, a router crash after firmware update fail etc etc.

>>>/tmp/home/root# nvram show | grep 'cfg_recount'
cfg_recount=9
size: 75005 bytes (56067 left)
>>>:/tmp/home/root#

Do i clear it with

nvram set cfg_recount=[number of nodes] | nvram commit
?

Will this remove and of the existing nodes?

I had orphaned nodes that wouldn't show up in the GUI and prevented me from adding new nodes as the outer thought I had reached the 9-node limit.

This thread helped me fix the problem. Here's what I did:

Use Merlin FW to ensure SCP is working (Asus firmware doesn't have it).
Use an SSH client like Bitvise to logon
Use WinSCP to pull up the file explorer
Check the current node count
nvram get cfg_recount
Write the cfg_relist to a file.
nvram get cfg_relist > cfg_relist.txt
Use WinSCP to edit out the bogus/orphaned entries from the file and save
EDIT cfg_relist.txt with WinSCP (Notepad++) then SAVE
Write the data back to NVRAM. Doing it this away dodges the "<" character issue mentioned above.
nvram set cfg_relist "`cat cfg_relist.txt`"
Reboot and Check the count! It works!
nvram get cfg_recount

I forgot to NVRAM COMMIT when I did the above, but it seemed to work just fine and retained everything post-boot. YMMV.


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: Solved Are the 8 POE ports on the ASUS ExpertWiFi EBG19P active or passive?

I can't, for the life of me, find any information on the subject. I have no interest in the device if it's ports are passive POE, as the risks are unacceptable to me.

[Assistant]
YRTFS said:
I can't, for the life of me, find any information on the subject. I have no interest in the device if it's ports are passive POE, as the risks are unacceptable to me.
Some of the comments on the Amazon page for this unit state that the PoE is active.

RobJack said:
Some of the comments on the Amazon page for this unit state that the PoE is active.
Indeed. Forgot to menstion that I stumbled upon one of those as well, but I wouldn't really trust that, to be honest. I was hoping from confirmation from an actual owner or someone in the know.

Contact Asus and ask them. As that info is not disclosed in the Tech Specs on their website, they would be the best source of information.


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: Enabling WireGuard on RT-AX86U Pro reduces other clients' WireGuard bandwidth

On 750Mbps fiber connection my PC download speed is about 650Mbps using WireGuard NT, which is the official kernel space WireGuard client for Windows, or OpenVPN with Data Channel Offload, which also runs in kernel space. Enabling WireGuard VPN Fusion on ASUS RT-AX86U Pro (stock 3.0.0.6 firmware) for any VLAN results in my main PC download speed being reduced to about 450Mbps regardless of whether I use WireGuard NT or OpenVPN-DCO. That happens even if nobody is connected to the router except for my main PC. Is that normal?

If I route my PC through ASUS router's WireGuard tunnel (instead of using WireGuard for Windows), then I get about 500Mbps for download speed, but OpenVPN bandwidth maxes out at 200Mbps. My guess is that official stock firmware does not use DCO for OpenVPN.

Running bandwidth tests does show that router's CPU Core 1 reaches 100% utilization. Other 3 cores stat at 1% during those tests. Is this router simply not optimized to run WireGuard in kernel space?

EDIT: It looks like its some kind of port saturation issue. If I use OpenVPN-DCO via non-default port 51820 (same as default WireGuard port) then my PC bandwidth is reduced to 450Mbps when WireGuard is enabled for any client on this router, but if I switch my PC to use OpenVPN-DCO via port 1194, then my bandwidth goes back up to 650Mbps, even when WireGuard is enabled on router for other clients. Why would outbound port affect bandwidth?

[Assistant]
SDF07S said:
On 750Mbps fiber connection my PC download speed is about 650Mbps using WireGuard NT, which is the official kernel space WireGuard client for Windows, or OpenVPN with Data Channel Offload, which also runs in kernel space. Enabling WireGuard VPN Fusion on ASUS RT-AX86U Pro (stock 3.0.0.6 firmware) for any VLAN results in my main PC download speed being reduced to about 450Mbps regardless of whether I use WireGuard NT or OpenVPN-DCO. That happens even if nobody is connected to the router except for my main PC. Is that normal?

If I route my PC through ASUS router's WireGuard tunnel (instead of using WireGuard for Windows), then I get about 500Mbps for download speed, but OpenVPN bandwidth maxes out at 200Mbps. My guess is that official stock firmware does not use DCO for OpenVPN.

Running bandwidth tests does show that router's CPU Core 1 reaches 100% utilization. Other 3 cores stat at 1% during those tests. Is this router simply not optimized to run WireGuard in kernel space?

EDIT: It looks like its some kind of port saturation issue. If I use OpenVPN-DCO via non-default port 51820 (same as default WireGuard port) then my PC bandwidth is reduced to 450Mbps when WireGuard is enabled for any client on this router, but if I switch my PC to use OpenVPN-DCO via port 1194, then my bandwidth goes back up to 650Mbps, even when WireGuard is enabled on router for other clients. Why would outbound port affect bandwidth?
Click to expand...
If you get to the bottom of thsi please post.... I have this router and have found that it tends to make up it's own mind on stuff too often.

GetToTheChopper! said:
If you get to the bottom of thsi please post.... I have this router and have found that it tends to make up it's own mind on stuff too often.
You appear to be running one or more add-ons. As a troubleshooting step if you haven't done so already, remove all addons and test. Sometimes add-ons can introduce the oddball issue.
Ideally when one is having strange issues; is to troubleshot by performing a hard factory reset, then a basic initial manual configuration without restoring a saved router.cfg file and without installing any add-on scripts or USB drives.

SDF07S said:
Running bandwidth tests does show that router's CPU Core 1 reaches 100% utilization. Other 3 cores stat at 1% during those tests. Is this router simply not optimized to run WireGuard in kernel space?
It is due to broadcom nat hw acceleration is not compatible with Wireguard kernel implementation. Thus nat has to be done in software for the Wireguard port and source ip used. So when core 1 maxes out its due to sw nat and not wireguard (wireguard is multi core)

SDF07S said:
Why would outbound port affect bandwidth?
Asus/broadcom flowcache bypass (nat hw bypass) is set on Wireguard port and source ip. Other data using these will be affected as well.

You could check bypass via ssh if you want:
Code:
cat /proc/blog/skip_wireguard_port
cat /proc/blog/skip_wireguard_network

Edit: saw that this thread was not new after writing but leaving info here if someone needs it.


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: Wireless Devices connecting to Wireless Backhaul

Just saw something today that I wanted to find out is normal behavior...

I have 5ghz-2 set as the dedicated wireless backhaul. 5ghz-2 is also set in smart connect (5ghz and 5ghz-2 are the only ones ticked). I hear many for and against using smart connect. Is this why I have some devices connecting to 5ghz-2 even though its set as wireless backhaul?

[Assistant]
outlaw78 said:
Just saw something today that I wanted to find out is normal behavior...

I have 5ghz-2 set as the dedicated wireless backhaul. 5ghz-2 is also set in smart connect (5ghz and 5ghz-2 are the only ones ticked). I hear many for and against using smart connect. Is this why I have some devices connecting to 5ghz-2 even though its set as wireless backhaul?
Router model please

Regardless of router model - this situation is most likely result of Asuswrt lack of dependencies. You can't have dedicated wireless backhaul and Smart Connect involving the same radio at the same time. The backhaul is dedicated or shared, not both.

Tech9 said:
Regardless of router model - this situation is most likely result of Asuswrt lack of dependencies. You can't have dedicated wireless backhaul and Smart Connect involving the same radio at the same time. The backhaul is dedicated or shared, not both.
That's what I figured, it was my setup. Does this affect anything negatively? I'm just loosing bandwidth for the backhaul correct?


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: ASUS XT8 issues

New guy here and I’ve done some searching and see some threads with similar issues but haven’t found a solution in any of them.

I recently moved into a new house and it has a fiber direct to house ISP. The house I came from had spectrum cable and used a modem.
I used my Asus XT8 system there with no issues and paid for a 400mbps connection and very often got over that.

Fast forward to now, I brought one of my nodes from old house to the new one, I factory reset it, put it in router mode, and standing right beside it I get 280 down and 495 up and I’m paying for 500/500. This is on the 5G-1 and it’s worse on 2.4 and about the same on 5G-2. I have since added 3 nodes and seem to have decent coverage around the house but the speed is about half what I’m paying for on the download side. If I hook my laptop directly to router or direct to the supply cable I get 540/540 and that’s on speedtest…using Asus speed test in dashboard I get 525/550. I have all the stuff disabled that’s been reported to hurt, and the Asus rep I spoke with last night suggested to turn off the firewall which I did…didn’t help. I’ve tried channel 36,40,44, and 48 on 5G-1 with no real difference in any of them.

The only thing that changed from then and now is
1. A different ISP and type of service
2. I think when I reset and set it up it did a firmware update.

I will say I’ve never had any issues with it until now, however my new house is in a very rural area and has zero cell reception so WiFi signal and bandwidth are of the utmost importance to me and my wife who works from home.

That brings me to my questions.

1. What am I missing on the download speed ?
2. Is my xt8 system outdated?

3. Is there a better Asus mesh system available?

[Assistant]
JB14 said:
and the Asus rep I spoke with last night suggested to turn off the firewall

Really? Never call Asus Support again... turn the Firewall back on.

Tech9 said:
Really? Never call Asus Support again... turn the Firewall back on.
Turned it back on immediately….the guy literally just ran through all the things I had already done and I firmly believe I know as much as he does and I know very little, which is why I chose a mesh system like the XT8

Based on the information provided so far all I can say is - enjoy your new home! About TX8 - you obviously have Wi-Fi related issues, Wi-Fi settings are environment specific and I have no idea what "I have all the stuff disabled that’s been reported to hurt" means. Don't copy/paste someone else's settings, they may not apply to you.


[System] You are a professional Wi-Fi router support assistant; I will provide forum posts as background material, and you should learn from them while remaining aware that forum content may be incomplete, outdated, or incorrect — when uncertain, explicitly note that you are uncertain and refer the user to official documentation or other authoritative sources for verification.

[User]
Title: Asus Mesh Nodes

Question: Asus router (RT-AX86U Pro) I'm using as my main and is fully supported. I have a older RT-AC68U that I'm using as a Mesh Node with a wired back haul(out of support) Does it matter that I'm using an older device? I'm I putting my network at risk? My first thought was that the RT-AC68U is not using its firmware and using the main router instead therefore it should be safe?? I'm really not sure maybe someone can advise?

[Assistant]
custmblt said:
I'm I putting my network at risk?

No. Wired node is an access point. No routing there.

Great, that's what I was thinking. I will admit I don't fully understand how the AI Mesh works and how it is able to maintain the same SSID and not have conflict. Thank you

custmblt said:
maintain the same SSID and not have conflict

AiMesh has nothing to do with it. Wireless routers using the same channels share the available bandwidth regardless of SSID name. This is how Wi-Fi works. Routers hear each other and wait for their turn to transmit and receive data.

custmblt said:
AI Mesh

Not AI Mesh, but AiMesh. Nothing AI there, just a marketing name of Asus extra "mesh" software in Asuswrt. Like AiProtection, AiCloud and other Ai things they have there. Asus likes to mimic popular abbreviations in their marketing.

Asus AI is... Always Incredible
Asus SDN is... Self-Defined Network