05-21-2020 12:36 AM - last edited on 03-05-2024 07:59 PM by ROGBot
05-21-2020 08:11 AM
MomoSam wrote:
Hi,
My home network is made up of Router (ROG AX-11000) and 4 mesh nodes (Zenwifi XT8), via wired backhaul.
I have been encountering a drop in connection between Router and nodes at least once daily. All other devices that are connected to Router, directly or indirectly via switch, remain active and well, during the drop. To reinstate the nodes, i will need to turn off and on the nodes and everything will work as per normal.
Have reset all nodes with no improvement. Trying not to reset the Router.
I have noticed the following extraordinary items in the system log of Router during the occurrence, either singly or together:
avahi-daemon[1246]: Host name conflict, retrying with GT-AX11000-1E90-192
lld2d[1276]: packetio_recv_handler: mis-matched sequence number: got 1, expecting 3; ignoring
Wondering if this drop in connection is due to one or both of these? If so, what can i do to fix this? Otherwise, anything else i can look into to fix the issue?
It's a pity that this happens. The system works wonderfully (and fast) otherwise.
Thank you for your kind advice.
05-21-2020 11:51 PM
05-24-2020 08:06 PM
MomoSam wrote:
Hi,
My home network is made up of Router (ROG AX-11000) and 4 mesh nodes (Zenwifi XT8), via wired backhaul.
I have been encountering a drop in connection between Router and nodes at least once daily. All other devices that are connected to Router, directly or indirectly via switch, remain active and well, during the drop. To reinstate the nodes, i will need to turn off and on the nodes and everything will work as per normal.
Have reset all nodes with no improvement. Trying not to reset the Router.
I have noticed the following extraordinary items in the system log of Router during the occurrence, either singly or together:
avahi-daemon[1246]: Host name conflict, retrying with GT-AX11000-1E90-192
lld2d[1276]: packetio_recv_handler: mis-matched sequence number: got 1, expecting 3; ignoring
Wondering if this drop in connection is due to one or both of these? If so, what can i do to fix this? Otherwise, anything else i can look into to fix the issue?
It's a pity that this happens. The system works wonderfully (and fast) otherwise.
Thank you for your kind advice.
05-27-2020 09:23 PM
05-31-2020 07:56 PM
MomoSam wrote:
Hi,
Enclosed pls find the system log. Pls note that the connection drops at 12.10-12.11pm.
I have reset all nodes and issue remains.
Kindly advise. Many thanks.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(509): eth7: ReAssoc 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:19 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:19 wlceventd: wlceventd_proc_event(481): eth6: Disassoc 5C:96:9D:BB:8F:96, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:10:20 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Unspecified reason (1)
May 28 12:10:20 wlceventd: wlceventd_proc_event(499): eth7: Auth 5C:96:9D:BB:8F:96, status: Successful (0)
May 28 12:10:23 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind 5C:96:9D:BB:8F:96, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
May 28 12:10:39 wlceventd: wlceventd_proc_event(499): eth6: Auth D4:5D:64:4A:EB:81, status: Successful (0)
May 28 12:10:39 wlceventd: wlceventd_proc_event(527): eth6: Assoc D4:5D:64:4A:EB:81, status: Successful (0)
May 28 12:10:39 wlceventd: wlceventd_proc_event(499): eth6: Auth A8:5E:45:8B:E2:21, status: Successful (0)
May 28 12:10:39 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind A8:5E:45:8B:E2:21, status: 0, reason: Unspecified reason (1)
May 28 12:10:39 wlceventd: wlceventd_proc_event(499): eth6: Auth A8:5E:45:8B:E2:21, status: Successful (0)
May 28 12:10:39 wlceventd: wlceventd_proc_event(527): eth6: Assoc A8:5E:45:8B:E2:21, status: Successful (0)
May 28 12:10:39 wlceventd: wlceventd_proc_event(499): eth6: Auth A8:5E:45:8B:DF:41, status: Successful (0)
May 28 12:10:39 wlceventd: wlceventd_proc_event(527): eth6: Assoc A8:5E:45:8B:DF:41, status: Successful (0)
May 28 12:10:41 wlceventd: wlceventd_proc_event(499): eth8: Auth D4:5D:64:4A:EB:88, status: Successful (0)
May 28 12:10:41 wlceventd: wlceventd_proc_event(527): eth8: Assoc D4:5D:64:4A:EB:88, status: Successful (0)
May 28 12:10:41 wlceventd: wlceventd_proc_event(499): eth8: Auth A8:5E:45:8B:E2:28, status: Successful (0)
May 28 12:10:41 wlceventd: wlceventd_proc_event(527): eth8: Assoc A8:5E:45:8B:E2:28, status: Successful (0)
May 28 12:10:41 wlceventd: wlceventd_proc_event(499): eth8: Auth A8:5E:45:8B:DF:48, status: Successful (0)
May 28 12:10:41 wlceventd: wlceventd_proc_event(527): eth8: Assoc A8:5E:45:8B:DF:48, status: Successful (0)
May 28 12:10:43 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind D4:5D:64:4A:EB:81, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
May 28 12:10:43 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind A8:5E:45:8B:E2:21, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
May 28 12:10:43 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind A8:5E:45:8B:DF:41, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
May 28 12:10:45 wlceventd: wlceventd_proc_event(464): eth8: Deauth_ind D4:5D:64:4A:EB:88, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
May 28 12:10:45 wlceventd: wlceventd_proc_event(464): eth8: Deauth_ind A8:5E:45:8B:E2:28, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
May 28 12:10:45 wlceventd: wlceventd_proc_event(464): eth8: Deauth_ind A8:5E:45:8B:DF:48, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
May 28 12:10:46 wlceventd: wlceventd_proc_event(499): eth6: Auth A8:5E:45:8B:DF:41, status: Successful (0)
May 28 12:10:46 wlceventd: wlceventd_proc_event(527): eth6: Assoc A8:5E:45:8B:DF:41, status: Successful (0)
May 28 12:10:46 avahi-daemon[1281]: Host name conflict, retrying with GT-AX11000-1E90-49
May 28 12:10:47 avahi-daemon[1281]: Alias name "GT-AX11000" successfully established.
May 28 12:10:48 avahi-daemon[1281]: Host name conflict, retrying with GT-AX11000-1E90-50
May 28 12:10:48 avahi-daemon[1281]: Host name conflict, retrying with GT-AX11000-1E90-51
May 28 12:10:49 avahi-daemon[1281]: Host name conflict, retrying with GT-AX11000-1E90-52
May 28 12:10:49 wlceventd: wlceventd_proc_event(499): eth6: Auth D4:5D:64:4A:EB:81, status: Successful (0)
May 28 12:10:49 wlceventd: wlceventd_proc_event(527): eth6: Assoc D4:5D:64:4A:EB:81, status: Successful (0)
May 28 12:10:50 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind A8:5E:45:8B:DF:41, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
May 28 12:10:50 avahi-daemon[1281]: Host name conflict, retrying with GT-AX11000-1E90-53
May 28 12:10:51 avahi-daemon[1281]: Host name conflict, retrying with GT-AX11000-1E90-54
May 28 12:10:52 avahi-daemon[1281]: Host name conflict, retrying with GT-AX11000-1E90-55
May 28 12:10:53 avahi-daemon[1281]: Host name conflict, retrying with GT-AX11000-1E90-56
May 28 12:10:53 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind D4:5D:64:4A:EB:81, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
May 28 12:10:54 avahi-daemon[1281]: Host name conflict, retrying with GT-AX11000-1E90-57
May 28 12:10:54 wlceventd: wlceventd_proc_event(499): eth6: Auth A8:5E:45:8B:E2:21, status: Successful (0)
May 28 12:10:54 wlceventd: wlceventd_proc_event(527): eth6: Assoc A8:5E:45:8B:E2:21, status: Successful (0)
May 28 12:10:55 avahi-daemon[1281]: Host name conflict, retrying with GT-AX11000-1E90-58
May 28 12:10:55 lld2d[1308]: packetio_recv_handler: mis-matched sequence number: got 1, expecting 6; ignoring
May 28 12:10:55 lld2d[1308]: packetio_recv_handler: mis-matched sequence number: got 1, expecting 6; ignoring
May 28 12:10:55 lld2d[1308]: packetio_recv_handler: mis-matched sequence number: got 1, expecting 6; ignoring
May 28 12:10:55 lld2d[1308]: packetio_recv_handler: mis-matched sequence number: got 2, expecting 6; ignoring
May 28 12:10:55 lld2d[1308]: packetio_recv_handler: mis-matched sequence number: got 2, expecting 6; ignoring
May 28 12:10:55 lld2d[1308]: packetio_recv_handler: mis-matched sequence number: got 2, expecting 6; ignoring
May 28 12:10:55 lld2d[1308]: packetio_recv_handler: mis-matched sequence number: got 3, expecting 6; ignoring
May 28 12:10:56 lld2d[1308]: packetio_recv_handler: mis-matched sequence number: got 3, expecting 6; ignoring
May 28 12:10:56 lld2d[1308]: packetio_recv_handler: mis-matched sequence number: got 3, expecting 6; ignoring
May 28 12:10:56 lld2d[1308]: packetio_recv_handler: mis-matched sequence number: got 4, expecting 6; ignoring
May 28 12:10:56 lld2d[1308]: packetio_recv_handler: mis-matched sequence number: got 4, expecting 6; ignoring
May 28 12:10:56 wlceventd: wlceventd_proc_event(499): eth6: Auth D4:5D:64:4A:E7:C1, status: Successful (0)
May 28 12:10:56 lld2d[1308]: packetio_recv_handler: mis-matched sequence number: got 4, expecting 6; ignoring
May 28 12:10:56 wlceventd: wlceventd_proc_event(527): eth6: Assoc D4:5D:64:4A:E7:C1, status: Successful (0)
May 28 12:10:56 wlceventd: wlceventd_proc_event(499): eth6: Auth A8:5E:45:8B:DF:41, status: Successful (0)
May 28 12:10:56 wlceventd: wlceventd_proc_event(527): eth6: Assoc A8:5E:45:8B:DF:41, status: Successful (0)
May 28 12:10:56 avahi-daemon[1281]: Host name conflict, retrying with GT-AX11000-1E90-59
May 28 12:10:57 avahi-daemon[1281]: Host name conflict, retrying with GT-AX11000-1E90-60
May 28 12:10:58 avahi-daemon[1281]: Host name conflict, retrying with GT-AX11000-1E90-61
May 28 12:10:58 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind A8:5E:45:8B:E2:21, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
May 28 12:10:59 avahi-daemon[1281]: Host name conflict, retrying with GT-AX11000-1E90-62
May 28 12:11:00 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind D4:5D:64:4A:E7:C1, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
May 28 12:11:00 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind A8:5E:45:8B:DF:41, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
May 28 12:11:00 avahi-daemon[1281]: Host name conflict, retrying with GT-AX11000-1E90-63
May 28 12:11:05 wlceventd: wlceventd_proc_event(499): eth6: Auth D4:5D:64:4A:EB:81, status: Successful (0)
May 28 12:11:05 wlceventd: wlceventd_proc_event(527): eth6: Assoc D4:5D:64:4A:EB:81, status: Successful (0)
May 28 12:11:05 wlceventd: wlceventd_proc_event(481): eth6: Disassoc D4:5D:64:4A:EB:81, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:11:05 wlceventd: wlceventd_proc_event(481): eth6: Disassoc D4:5D:64:4A:EB:81, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:11:12 wlceventd: wlceventd_proc_event(499): eth8: Auth D4:5D:64:4A:EB:88, status: Successful (0)
May 28 12:11:12 wlceventd: wlceventd_proc_event(527): eth8: Assoc D4:5D:64:4A:EB:88, status: Successful (0)
May 28 12:11:12 wlceventd: wlceventd_proc_event(499): eth8: Auth A8:5E:45:8B:E2:28, status: Successful (0)
May 28 12:11:12 wlceventd: wlceventd_proc_event(527): eth8: Assoc A8:5E:45:8B:E2:28, status: Successful (0)
May 28 12:11:12 wlceventd: wlceventd_proc_event(499): eth8: Auth A8:5E:45:8B:DF:48, status: Successful (0)
May 28 12:11:12 wlceventd: wlceventd_proc_event(527): eth8: Assoc A8:5E:45:8B:DF:48, status: Successful (0)
May 28 12:11:15 wlceventd: wlceventd_proc_event(481): eth8: Disassoc D4:5D:64:4A:EB:88, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:11:15 wlceventd: wlceventd_proc_event(481): eth8: Disassoc D4:5D:64:4A:EB:88, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:11:15 wlceventd: wlceventd_proc_event(481): eth8: Disassoc A8:5E:45:8B:DF:48, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:11:15 wlceventd: wlceventd_proc_event(481): eth8: Disassoc A8:5E:45:8B:DF:48, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:11:16 wlceventd: wlceventd_proc_event(481): eth8: Disassoc A8:5E:45:8B:E2:28, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:11:16 wlceventd: wlceventd_proc_event(481): eth8: Disassoc A8:5E:45:8B:E2:28, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:11:17 wlceventd: wlceventd_proc_event(499): eth8: Auth A8:5E:45:8B:E2:28, status: Successful (0)
May 28 12:11:17 wlceventd: wlceventd_proc_event(527): eth8: Assoc A8:5E:45:8B:E2:28, status: Successful (0)
May 28 12:11:17 wlceventd: wlceventd_proc_event(499): eth8: Auth D4:5D:64:4A:EB:88, status: Successful (0)
May 28 12:11:17 wlceventd: wlceventd_proc_event(527): eth8: Assoc D4:5D:64:4A:EB:88, status: Successful (0)
May 28 12:11:19 wlceventd: wlceventd_proc_event(481): eth8: Disassoc D4:5D:64:4A:EB:88, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:11:19 wlceventd: wlceventd_proc_event(481): eth8: Disassoc D4:5D:64:4A:EB:88, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:11:20 wlceventd: wlceventd_proc_event(481): eth8: Disassoc A8:5E:45:8B:E2:28, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:11:20 wlceventd: wlceventd_proc_event(481): eth8: Disassoc A8:5E:45:8B:E2:28, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:11:21 avahi-daemon[1281]: Alias name "GT-AX11000" successfully established.
May 28 12:11:37 roamast: determine candidate node [A8:5E:45:8B:E2:20](rssi: -51dbm) for client [B0:C0:90:CB:16:45](rssi: -75dbm) to roam
May 28 12:11:37 roamast: eth7: disconnect weak signal strength station [b0:c0:90:cb:16:45]
May 28 12:11:37 roamast: eth7: remove client [b0:c0:90:cb:16:45] from monitor list
May 28 12:11:37 wlceventd: wlceventd_proc_event(464): eth7: Deauth_ind B0:C0:90:CB:16:45, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
May 28 12:11:38 wlceventd: wlceventd_proc_event(481): eth7: Disassoc B0:C0:90:CB:16:45, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:12:07 roamast: determine candidate node [D4:5D:64:4A:EB:80](rssi: -44dbm) for client [34:A8:EB:27:BB:D1](rssi: -76dbm) to roam
May 28 12:12:07 wlceventd: wlceventd_proc_event(481): eth7: Disassoc 34:A8:EB:27:BB:D1, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:12:07 wlceventd: wlceventd_proc_event(481): eth7: Disassoc 34:A8:EB:27:BB:D1, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:12:17 roamast: determine candidate node [D4:5D:64:4A:EB:80](rssi: -48dbm) for client [34:A8:EB:27:BB:D1](rssi: -76dbm) to roam
May 28 12:12:32 roamast: determine candidate node [D4:5D:64:4A:EB:80](rssi: -43dbm) for client [40:4D:7F:97:D0:7C](rssi: -71dbm) to roam
May 28 12:12:32 wlceventd: wlceventd_proc_event(481): eth7: Disassoc 40:4D:7F:97:D0:7C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:12:32 wlceventd: wlceventd_proc_event(481): eth7: Disassoc 40:4D:7F:97:D0:7C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 28 12:12:32 roamast: eth7: disconnect weak signal strength station [40:4d:7f:97:d0:7c]
May 28 12:12:32 roamast: eth7: remove client [40:4d:7f:97:d0:7c] from monitor list
06-04-2020 01:26 AM
06-08-2020 01:52 AM
MomoSam wrote:
HI,
Have submitted via feedback as advised. Still awaiting reply.
The drop still happens on daily basis. Noticed a common trend though. The following log statements always occur before the drop:
wlceventd: wlceventd_proc_event(464): eth8: Deauth_ind D4:5D:64:4A:EB:88, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
wlceventd: wlceventd_proc_event(464): eth8: Deauth_ind A8:5E:45:8B:E2:28, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
wlceventd: wlceventd_proc_event(499): eth6: Auth A8:5E:45:8B:DF:41, status: Successful (0)
wlceventd: wlceventd_proc_event(527): eth6: Assoc A8:5E:45:8B:DF:41, status: Successful (0)
wlceventd: wlceventd_proc_event(464): eth8: Deauth_ind A8:5E:45:8B:DF:48, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
These Mac addresses do not belong to any of my listed devices. A quick check online shows that they belong to Asus hardwares. Once i have restarted the nodes, these statements do not appear anymore, until the next cycle/next day. My current nodes have different Mac addresses.
Also realized that the error message "avahi-daemon[1281]: Host name conflict, retrying with GT-AX11000-1E90-133" only appears after i have restarted the nodes, and is therefore not the cause of the drop.