Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Republic of Gamers Forum
- Networking
- Gaming Routers
- Daily drop in connection with AX-11000 (router) + ...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Daily drop in connection with AX-11000 (router) + Zenwifi XT8 (mesh)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
05-21-2020
12:36 AM
- last edited on
03-05-2024
07:59 PM
by
ROGBot
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.
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.
Labels:
- Labels:
-
Gaming Routers
-
Network Routers
6,451 Views
7 REPLIES 7
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
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.
Let assume all your Zenwifi XT8 are in the default setting out of the box. turn on individual mesh to add it to your AX 110000 router one by one and it working find with each mesh connected correctly. Dont rush to add another mesh until the unit are able to connect correctly.
The error message indicate there is a drop in one of your mesh point connection failed.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
05-21-2020 11:51 PM
Hi,
Thank you for your kind advice. Have not thought that the drop in connection could be due to two issues.
I presume that the error message which is linked to a mesh node not being setup optimally, that you were referring to in your advice, was:
"ld2d[1276]: packetio_recv_handler: mis-matched sequence number: got 1, expecting 3; ignoring"
Will hard reset two of the nodes which i believe could be problematic, reinstate them as per your advice and see if this helps.
As for the other error message, i suspect that it could be caused by a client device (office laptop). So long that i do not log this device onto my network, the error message will not surface and the connections will not drop. Once the nodes have been turned off and on following the lost in connection, even with the client continued to be logged on, the message will not appear and the drop will not happen. Not sure if my assumption is correct? Or is it an intrinsic problem of my network instead?
Thank you for your kind advice. Have not thought that the drop in connection could be due to two issues.
I presume that the error message which is linked to a mesh node not being setup optimally, that you were referring to in your advice, was:
"ld2d[1276]: packetio_recv_handler: mis-matched sequence number: got 1, expecting 3; ignoring"
Will hard reset two of the nodes which i believe could be problematic, reinstate them as per your advice and see if this helps.
As for the other error message, i suspect that it could be caused by a client device (office laptop). So long that i do not log this device onto my network, the error message will not surface and the connections will not drop. Once the nodes have been turned off and on following the lost in connection, even with the client continued to be logged on, the message will not appear and the drop will not happen. Not sure if my assumption is correct? Or is it an intrinsic problem of my network instead?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
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.
Hi
would like to have your log for RD side double check, could you kindly use feedback to provide additional info?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
05-27-2020 09:23 PM
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
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
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
05-31-2020 07:56 PM
Hi Sir,
the log is too narrow to check, could you kindly use feedback system in our firmware? it will bring us more.
Thanks.
the log is too narrow to check, could you kindly use feedback system in our firmware? it will bring us more.
Thanks.
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
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
06-04-2020 01:26 AM
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.
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.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
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.
Hi
thanks, and need your email to query from our feedback system, please private message me your email.
Related Content
- Slow, Unstable WiFi on GT-AX11000 in Gaming Routers
- [Networking Product] Duration of Security Update Support (only for UK) in FAQs (Networking)
- [Wireless Router] Duration of Security Update Support (only for Singapore) in FAQs (Networking)
- Asus GT-AX11000 with Moca Backbone and Switch in Gaming Routers
- Mesh WiFi connection problem in Gaming Routers
