5Ghz becoming unreachable till Power button restart -after some days work on AXE11000 model

[iskander4real]

3 different SSID  for all 3 ranges, problem with the 5Ghz range - in 2-4 days working fine, then you can't connect to this range -> Power button.

2,4 and 6 Ghz ranges worked fine.

Tried both last Merlin or Asus bios, Smart connect off, Roaming assistant off.

Asus support doesn't recommend too much after, except change in 5Ghz to 20-40, take out 80 Mhz.

Exchanged router - same thing, seems running in the model? Previous wifi 5 router works fine.

[jzchen]

I have Smart Connect 2,4 and 5 GHz.  6 GHz same SSID and Password.

160 MHz enabled on 5 GHz.

(See attached, everything okay)...

[Saltgrass]

This looks like a situation which would really need information from your logs.  If you copy and paste a section of the log, you may be able to search for the MAC address of your 5 GHz network or radio.  Sometimes they are identified as ethX where 0-3 or 1-4 are the Ethernet ports and the ones higher are the wireless versions.

Each radio does have a specific designation, so when you find that, it won't be that hard to see what the logs are showing.  If you want us to look at them, just make them available.

[iskander4real]

Thank you - I will try to make it soon, can I use Direct Message here?

[Saltgrass]

It is better to keep it in the thread, but private messages are available.

[iskander4real]

Thank you for looking:

seems from LOG file we hit  this PROBLEM:  Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

Fixing channel doesn't help for 5Ghz Range. So put back in auto. Read some forums - so now waiting for problems AFTER these changes only in 5Ghz range (where it doesn't connect after reboot in 3-5 days):

1. Enable WMM ASD - OFF now  2. 802.11ax/ac Beamforming  KEEP IT ON  3. Universal Beamforming SWITCH IT OFF

Feb 1 13:01:45 kernel: FPM Pool 1: invalid token 0x20320000 freed
Feb 1 13:01:46 kernel: FPM Pool 1: invalid token 0x20328000 freed
Feb 1 13:02:00 wlceventd: wlceventd_proc_event(662): eth7: Disassoc  :D9:42:BB, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 1 13:02:07 wlceventd: wlceventd_proc_event(662): eth7: Disassoc  :1B:EE:A0, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

Feb 1 13:11:21 wlceventd: wlceventd_proc_event(685): eth7: Auth :D9:42:BB, status: Successful (0), rssi:0
Feb 1 13:11:21 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind :D9:42:BB, status: 0, reason: Unspecified reason (1), rssi:0
Feb 1 13:11:21 wlceventd: wlceventd_proc_event(685): eth7: Auth :D9:42:BB, status: Successful (0), rssi:0
Feb 1 13:11:22 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind :D9:42:BB, status: 0, reason: Unspecified reason (1), rssi:0
Feb 1 13:11:22 wlceventd: wlceventd_proc_event(685): eth7: Auth :D9:42:BB, status: Successful (0), rssi:0
Feb 1 13:11:22 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind :D9:42:BB, status: 0, reason: Unspecified reason (1), rssi:0
Feb 1 13:11:22 wlceventd: wlceventd_proc_event(685): eth7: Auth :D9:42:BB, status: Successful (0), rssi:0
Feb 1 13:11:22 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind :D9:42:BB, status: 0, reason: Unspecified reason (1), rssi:0

Here we REBOOT - and all good - both 2 devices connected to 5Ghjz

Feb 1 13:13:45 wlceventd: wlceventd_proc_event(685): eth7: Auth :1B:EE:A0, status: Successful (0), rssi:0
Feb 1 13:13:45 wlceventd: wlceventd_proc_event(722): eth7: Assoc :1B:EE:A0, status: Successful (0), rssi:-59
Feb 1 13:13:58 crond[1332]: time disparity of 3548468 minutes detected
Feb 1 13:15:02 wlceventd: wlceventd_proc_event(685): eth7: Auth :D9:42:BB, status: Successful (0), rssi:0
Feb 1 13:15:02 wlceventd: wlceventd_proc_event(722): eth7: Assoc :D9:42:BB, status: Successful (0), rssi:-55
Feb 1 13:15:02 dnsmasq[2021]: nameserver 127.0.1.1 refused to do a recursive query
Feb 1 13:15:11 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7904)]periodic_check AM 3:58
Feb 1 13:15:11 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7948)]do webs_update

[jzchen]

This router is in service at my sister-in-law's place.  I manage it and have these settings:

[Saltgrass]

In you log , the two lines below are what is supposed to happen when the radio is reacquired.  You can see the rssi is -59, so it can be Associated.  This sort of thing goes on all the time.  But we know, both of our systems were unable to find a Control Channel for certain radios, which probably means they can't even see those radios.  An Unspecified reason (1), is not much help unless you know what it means.  If it continues, you may need to do a feedback report and include all the logs for ASUS to analyze.

My system has been stable now for two days, after the hard reset.

Feb 1 13:13:45 wlceventd: wlceventd_proc_event(685): eth7: Auth :1B:EE:A0, status: Successful (0), rssi:0
Feb 1 13:13:45 wlceventd: wlceventd_proc_event(722): eth7: Assoc :1B:EE:A0, status: Successful (0), rssi:-59

The earlier bad log, will not let it connect because the rssi is 0.  If the firmware is not able to set a control channel for that network, that may be the reason it is failing.

Feb 1 13:11:21 wlceventd: wlceventd_proc_event(685): eth7: Auth :D9:42:BB, status: Successful (0), rssi:0
Feb 1 13:11:21 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind :D9:42:BB, status: 0, reason: Unspecified reason (1), rssi:0

[jzchen]

Do you know/recognize what the log looks like if you experience a DFS event?  I read somewhere that 6 GHz also shares frequencies with military equipment, hence the addition of barometric and GPS data.  This does not explain your dropping of 2.4 GHz though...

[jzchen]

This router is pretty mature now.  I have a TP-Link RE815XE in repeater mode.  It should show in the Network List as one item each in 2.4, 5, and 6 GHz, but as you can see it does not show in 6 GHz for some strange reason.  It does appear as connected via Ethernet even though that is not true...