Menu
What's new
By:
Filters Better Search

Weird connection problem with 2 clients on 386.7

  • 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!

elyl

elyl

Occasional Visitor
I have an AX86U and a RP-AX56 in a mesh. Since updating to 386.7, I have had intermittent problems with my Galaxy S22 Ultra, and a Sony Android TV.

They will report that they are connected to the network, but I either get no internet, or it's ridiculously slow. Sometimes I get "connected without internet" on my S22, but generally nothing on the TV, it just reports as connected, but never loads anything.

I seem to get a loop of this in the system log when the issue happens...
Code: 
Jul 10 20:39:07 wlceventd: wlceventd_proc_event(505): eth6: Auth 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:39:07 wlceventd: wlceventd_proc_event(534): eth6: Assoc 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:40:08 kernel: wl0: random key value: 92A410D4AA05EE2B0D3601080A3F761F0A21E83B61E306AA77E4138981FE8BD5
Jul 10 20:40:08 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jul 10 20:40:10 wlceventd: wlceventd_proc_event(505): eth7: Auth 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:40:10 wlceventd: wlceventd_proc_event(534): eth7: Assoc 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:40:14 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:40:15 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:40:37 wlceventd: wlceventd_proc_event(505): eth7: Auth 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:40:37 wlceventd: wlceventd_proc_event(534): eth7: Assoc 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:40:41 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:40:42 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:41:17 wlceventd: wlceventd_proc_event(505): eth6: Auth 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:41:17 wlceventd: wlceventd_proc_event(534): eth6: Assoc 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:42:18 wlceventd: wlceventd_proc_event(505): eth7: Auth 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:42:18 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:42:18 kernel: wl0: random key value: 45B02CBA780E37B201DA00B109DC44FCCF3D24AB94DD040F07F774C132228FFF
Jul 10 20:42:18 wlceventd: wlceventd_proc_event(486): eth6: Disassoc 64:FF:XX:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul 10 20:42:18 wlceventd: wlceventd_proc_event(486): eth6: Disassoc 64:FF:XX:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul 10 20:42:22 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:42:23 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:42:24 wlceventd: wlceventd_proc_event(505): eth7: Auth 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:42:24 wlceventd: wlceventd_proc_event(534): eth7: Assoc 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:42:28 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:42:29 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:42:50 wlceventd: wlceventd_proc_event(505): eth7: Auth 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:42:50 wlceventd: wlceventd_proc_event(534): eth7: Assoc 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:42:54 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:42:55 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:43:03 kernel: 64:FF:XX:XX:XX:XX not mesh client, can't delete it

The MAC address here is my smart TV. I have tried binding these two clients to the main router (the closest source, in the TV's case) in AiMesh, but still the same issue. Any idea what these logs events might point to?

EDIT: Should specify, it only seems to be these 2 devices which have a problem. No problems on my other wifi-connected devices.
 
Last edited:
elyl said:
I have an AX86U and a RP-AX56 in a mesh. Since updating to 386.7, I have had intermittent problems with my Galaxy S22 Ultra, and a Sony Android TV.

They will report that they are connected to the network, but I either get no internet, or it's ridiculously slow. Sometimes I get "connected without internet" on my S22, but generally nothing on the TV, it just reports as connected, but never loads anything.

I seem to get a loop of this in the system log when the issue happens...
Code: 
Jul 10 20:39:07 wlceventd: wlceventd_proc_event(505): eth6: Auth 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:39:07 wlceventd: wlceventd_proc_event(534): eth6: Assoc 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:40:08 kernel: wl0: random key value: 92A410D4AA05EE2B0D3601080A3F761F0A21E83B61E306AA77E4138981FE8BD5
Jul 10 20:40:08 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jul 10 20:40:10 wlceventd: wlceventd_proc_event(505): eth7: Auth 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:40:10 wlceventd: wlceventd_proc_event(534): eth7: Assoc 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:40:14 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:40:15 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:40:37 wlceventd: wlceventd_proc_event(505): eth7: Auth 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:40:37 wlceventd: wlceventd_proc_event(534): eth7: Assoc 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:40:41 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:40:42 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:41:17 wlceventd: wlceventd_proc_event(505): eth6: Auth 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:41:17 wlceventd: wlceventd_proc_event(534): eth6: Assoc 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:42:18 wlceventd: wlceventd_proc_event(505): eth7: Auth 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:42:18 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:42:18 kernel: wl0: random key value: 45B02CBA780E37B201DA00B109DC44FCCF3D24AB94DD040F07F774C132228FFF
Jul 10 20:42:18 wlceventd: wlceventd_proc_event(486): eth6: Disassoc 64:FF:XX:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul 10 20:42:18 wlceventd: wlceventd_proc_event(486): eth6: Disassoc 64:FF:XX:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul 10 20:42:22 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:42:23 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:42:24 wlceventd: wlceventd_proc_event(505): eth7: Auth 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:42:24 wlceventd: wlceventd_proc_event(534): eth7: Assoc 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:42:28 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:42:29 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:42:50 wlceventd: wlceventd_proc_event(505): eth7: Auth 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:42:50 wlceventd: wlceventd_proc_event(534): eth7: Assoc 64:FF:XX:XX:XX:XX, status: Successful (0)
Jul 10 20:42:54 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:42:55 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 64:FF:XX:XX:XX:XX, status: 0, reason: Previous authentication no longer valid (2)
Jul 10 20:43:03 kernel: 64:FF:XX:XX:XX:XX not mesh client, can't delete it

The MAC address here is my smart TV. I have tried binding these two clients to the main router (the closest source, in the TV's case) in AiMesh, but still the same issue. Any idea what these logs events might point to?

EDIT: Should specify, it only seems to be these 2 devices which have a problem. No problems on my other wifi-connected devices.
Click to expand...

Try forgeting and recreating the client WiFi connections, and then cycling client power... for lack of a better idea.

OE
 
No luck with this. When the issue occurs (the TV seems to be the main culprit, although my phone will fallback to cellular when it has wifi issues, so I might not be noticing it as much there), seemingly the only way to resolve is to restart the TV, OR restart the wifi on the router by changing one of the wifi settings.
I've tried using the MAC filter to force it onto 5GHz or 2.4GHz, but it's not made any difference.
 
You must log in or register to reply here.

Similar threads

D
RT-AX88U losing WIFI
2
Replies
38
Views
2K
Ryan
Ryan
F
Problem getting Wireless IP address - Some Clients
Replies
7
Views
537
lgkahn
L
S
Struggling with Asus ZenWiFi BE30000 aka 3 node BQ16 Pro bundle
2 3
Replies
40
Views
6K
wrink
W
P
Peculiar syslog entries
Replies
7
Views
418
visortgw
visortgw
A
Devices associated but not completing connection
Replies
1
Views
331
Squall Leonhart
Squall Leonhart
Similar threads
Thread starter Title Forum Replies Date
E Weird connection drops on 5ghz Wifi GT-AX11000 Asuswrt-Merlin 3
Cr00zng Weird DNS issue.... Asuswrt-Merlin 4
C Weird client VPN problem that just started ! Asuswrt-Merlin 53
B Unable to establish VPN connection to my PiVPN (ovpn) from my Asus RT-AC86U running Asuswrt-Merlin 386.14 Asuswrt-Merlin 1
zombeeh8er GT-AX11000 Deauth-ing only 2.4GHz clients, no internet connection on other devices Asuswrt-Merlin 14
A RT-AX88U - 3004.388.8_2 - SSH connection closed after few minutes from reboot Asuswrt-Merlin 10
KrautHolg RT-AX88U Pro - Merlin Firmware:3004.388.8_2 - WiFi connection problem Asuswrt-Merlin 11
A PS5 Wired Connection Shows as Wi-Fi Asuswrt-Merlin 3
C Connection to router by ip fails while remote over OpenVPN Asuswrt-Merlin 17
U AX88U Do not come to the user interface after deactivated vpn connection Asuswrt-Merlin 6

Similar threads

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!

Members online

Total: 716 (members: 25, guests: 691)
Top