What's new

Rt-ax86U disconnects frequently

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

pb9

Regular Contributor
Hello,
My router has been working fine over the last few weeks and started disconnecting again. Below are the logs. Any help would be appreciated.
 
Last edited:
Hello,
My router has been working fine over the last few weeks and started disconnecting again. Below are the logs. Any help would be appreciated.

Mar 9 08:54:21 wlceventd: wlceventd_proc_event(527): eth6: Auth 52:17:FB:2D:F1:4D, status: Successful (0), rssi:0
Mar 9 08:54:21 hostapd: eth6: STA 52:17:fb:2d:f1:4d IEEE 802.11: associated
Mar 9 08:54:21 wlceventd: wlceventd_proc_event(556): eth6: Assoc 52:17:FB:2D:F1:4D, status: Successful (0), rssi:-66
Mar 9 08:54:21 hostapd: eth6: STA 52:17:fb:2d:f1:4d RADIUS: starting accounting session 6FB80C2354F2353C
Mar 9 08:54:21 hostapd: eth6: STA 52:17:fb:2d:f1:4d WPA: pairwise key handshake completed (RSN)
Mar 9 08:54:22 dnsmasq-dhcp[1452]: DHCPDISCOVER(br0) 52:17:fb:2d:f1:4d
Mar 9 08:54:22 dnsmasq-dhcp[1452]: DHCPOFFER(br0) 192.168.50.84 52:17:fb:2d:f1:4d
Mar 9 08:54:23 dnsmasq-dhcp[1452]: DHCPDISCOVER(br0) 52:17:fb:2d:f1:4d
Mar 9 08:54:23 dnsmasq-dhcp[1452]: DHCPOFFER(br0) 192.168.50.84 52:17:fb:2d:f1:4d
Mar 9 08:54:23 dnsmasq-dhcp[1452]: DHCPREQUEST(br0) 192.168.50.84 52:17:fb:2d:f1:4d
Mar 9 08:54:23 dnsmasq-dhcp[1452]: DHCPACK(br0) 192.168.50.84 52:17:fb:2d:f1:4d Galaxy-S9
Mar 9 09:02:08 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xe832 (36/160)
Mar 9 09:02:08 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Mar 9 09:02:08 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xe832 (36/160)
Mar 9 09:02:08 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xe932 (40/160)
Mar 9 09:02:08 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Mar 9 09:02:08 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xe932 (40/160)
Mar 9 09:02:08 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xea32 (44/160)
Mar 9 09:02:08 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Mar 9 09:02:08 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xea32 (44/160)
Mar 9 09:02:08 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Mar 9 09:02:08 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Mar 9 09:02:08 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xeb32 (48/160)
Mar 9 15:15:22 kernel: httpd (1477): drop_caches: 1
Also, I did try unplugging the modem and router for a minute or so. Didn't help much. Thanks.
 
Hello,
My router has been working fine over the last few weeks and started disconnecting again. Below are the logs. Any help would be appreciated.

Mar 9 08:54:21 wlceventd: wlceventd_proc_event(527): eth6: Auth 52:17:FB:2D:F1:4D, status: Successful (0), rssi:0
Mar 9 08:54:21 hostapd: eth6: STA 52:17:fb:2d:f1:4d IEEE 802.11: associated
Mar 9 08:54:21 wlceventd: wlceventd_proc_event(556): eth6: Assoc 52:17:FB:2D:F1:4D, status: Successful (0), rssi:-66
Mar 9 08:54:21 hostapd: eth6: STA 52:17:fb:2d:f1:4d RADIUS: starting accounting session 6FB80C2354F2353C
Mar 9 08:54:21 hostapd: eth6: STA 52:17:fb:2d:f1:4d WPA: pairwise key handshake completed (RSN)
Mar 9 08:54:22 dnsmasq-dhcp[1452]: DHCPDISCOVER(br0) 52:17:fb:2d:f1:4d
Mar 9 08:54:22 dnsmasq-dhcp[1452]: DHCPOFFER(br0) 192.168.50.84 52:17:fb:2d:f1:4d
Mar 9 08:54:23 dnsmasq-dhcp[1452]: DHCPDISCOVER(br0) 52:17:fb:2d:f1:4d
Mar 9 08:54:23 dnsmasq-dhcp[1452]: DHCPOFFER(br0) 192.168.50.84 52:17:fb:2d:f1:4d
Mar 9 08:54:23 dnsmasq-dhcp[1452]: DHCPREQUEST(br0) 192.168.50.84 52:17:fb:2d:f1:4d
Mar 9 08:54:23 dnsmasq-dhcp[1452]: DHCPACK(br0) 192.168.50.84 52:17:fb:2d:f1:4d Galaxy-S9
Mar 9 09:02:08 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xe832 (36/160)
Mar 9 09:02:08 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Mar 9 09:02:08 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xe832 (36/160)
Mar 9 09:02:08 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xe932 (40/160)
Mar 9 09:02:08 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Mar 9 09:02:08 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xe932 (40/160)
Mar 9 09:02:08 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xea32 (44/160)
Mar 9 09:02:08 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Mar 9 09:02:08 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xea32 (44/160)
Mar 9 09:02:08 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Mar 9 09:02:08 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Mar 9 09:02:08 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xeb32 (48/160)
Mar 9 15:15:22 kernel: httpd (1477): drop_caches: 1

The log suggests the router does not like using 160MHz bandwidth across DFS channels/frequencies. You could try setting a control channel that puts 160MHz across different DFS channels, but you may need to change to 80MHz bandwidth... and a non-DFS control channel.

OE
 
Ok. I disabled 160 MHz and my settings are as below now
 
Last edited:
Ok. I disabled 160 MHz and my settings are as below now

View attachment 40086

That ought to avoid DFS issues... 80MHz will span non-DFS channels 36-48. The graph below applies in the US:
1646840454949.png


Another option is to try 160MHz with a 100-128 control channel, but older clients may not recognize that WLAN with those frequencies.

OE
 
That ought to avoid DFS issues... 80MHz will span non-DFS channels 36-48. The graph below applies in the US:
View attachment 40087

Another option is to try 160MHz with a 100-128 control channel, but older clients may not recognize that WLAN with those frequencies.

OE
Ok. These are the new settings I have with 160MHz enabled based on the above
 
Last edited:
Ok. These are the new settings I have with 160MHz enabled based on the above

View attachment 40088

Now wait and see if the router detects DFS issues in that range of frequencies. If DFS was the original interference, I'd bet you will feel it again (but I don't know anything about radar usage!). Also watch for older clients not able to connect at those frequencies no matter any other settings.

I don't seem to have DFS interference here... yet, but I have a client that does not work with DFS channels. So, my only ax 160MHz option is to use a non-DFS control channel 36-48 and the low DFS channels 52-64 and hope for no DFS interference.... or retire my 2013 client that I really like using.

OE
 
Last edited:
  • Like
Reactions: pb9
I've always found ch64 solid as a rock here. Also the fastest as I have tried all of them because I have no life.
 
Ok. These are the new settings I have with 160MHz enabled based on the above

View attachment 40088
May I recommend you try 20, 40, 80, 160 MHz with Auto channel. If you want to, check Auto channel including DFS channels. You may be surprised how well it works. Trust your router to choose what is best in its environment. Also, enable Dual Band SmartConnect. This works very well for me.
 
May I recommend you try 20, 40, 80, 160 MHz with Auto channel. If you want to, check Auto channel including DFS channels. You may be surprised how well it works. Trust your router to choose what is best in its environment. Also, enable Dual Band SmartConnect. This works very well for me.
So, I had it with the Auto channel setup as you outline above. It worked fine for some time and then started disconnecting. I didn't have the Dual Band SmartConnect on though
 
Trust your router to choose what is best in its environment.

Will Auto channel avoid channels that older clients don't support?

OE
 
got disconnected again. Below is the log. Under the log is the print screen of my settings. Changed to 160MHz only on channel 124 for 5G
 
Last edited:
got disconnected again. Below is the log. Under the log is the print screen of my settings. Changed to 160MHz only on channel 124 for 5G
Mar 10 10:00:58 hostapd: eth6: STA c8:58:c0:dd:ef:4b WPA: group key handshake completed (RSN)
Mar 10 10:00:58 hostapd: eth6: STA 8e:af:72:fb:9f:a6 WPA: group key handshake completed (RSN)
Mar 10 10:00:58 hostapd: eth6: STA 7c:61:66:fb:87:f1 WPA: group key handshake completed (RSN)
Mar 10 10:00:58 hostapd: eth7: STA 98:2c:bc:26:32:e3 WPA: group key handshake completed (RSN)
Mar 10 10:00:58 hostapd: eth6: STA c8:6c:3d:a2:73:49 WPA: group key handshake completed (RSN)
Mar 10 10:00:58 hostapd: eth6: STA 18:74:2e:b4:68:5b WPA: group key handshake completed (RSN)
Mar 10 10:00:58 hostapd: wl0.2: STA 7c:27:bc:b0:63:9b WPA: group key handshake completed (RSN)
Mar 10 10:00:58 hostapd: eth6: STA d0:25:98:c0:21:27 WPA: group key handshake completed (RSN)
Mar 10 10:01:00 hostapd: eth6: STA 86:9c:8a:44:b6:e9 WPA: group key handshake completed (RSN)
Mar 10 10:02:37 dnsmasq-dhcp[1521]: DHCPINFORM(br0) 192.168.50.148 98:2c:bc:26:32:e3
Mar 10 10:02:37 dnsmasq-dhcp[1521]: DHCPACK(br0) 192.168.50.148 98:2c:bc:26:32:e3 TXAUSLTCD154572
Mar 10 16:10:04 kernel: httpd (1546): drop_caches: 1

I don't see/know anything from those log entries. "Disconnected" could mean a lot of things. If you want to rule out DFS, set 80MHz and a non-DFS control channel and watch it for awhile.

OE
 
I don't see/know anything from those log entries. "Disconnected" could mean a lot of things. If you want to rule out DFS, set 80MHz and a non-DFS control channel and watch it for awhile.

OE
Ok. These are my settings now for 5G
 
Last edited:
Alas, the disconnects still keep happening for clients connected to both 2.4G and 5G. Below is the log and the print screen of the latest settings is posted above. It worked fine for a while and then these issues started again.
 
Last edited:
Changed channel to 36. Leaving 160MHz disabled for now

Better... the previous ch 64 is a DFS channel. See how 36 runs.

OE
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top