jzchen wrote:
I Google searched "ASUS router sending station is leaving". I still don't know what exactly it means, but this reddit post appears to show that it may happen due to different reasons, two of which are:
1. A bug in dealing with private MAC address (or something like that is my understanding).
2. WiFi deauthorization attack. Someone is trying to gain access to your network or deliberately crash it.
https://www.reddit.com/r/HomeNetworking/comments/ls1btb/the_disassociated_because_sending_station_is...
You seem to have a very large area to cover with that many devices. I would rather get rid of the repeaters vs getting rid of the router. It is a good one I just bought most recently to place on our 2nd floor. Anyways there are only two neighbors here that signal from our network may reach, so any attack is extremely unlikely for us at least. You'll have to determine if that's a possibility in your case.
Either way I did use the Scan function under AiProtection (in the web GUI). Everything is "Yes" Wireless encryption enabled is "Strong" but my WiFi password is "Weak". Something you may or may not want to look into.
WiFi saturation that you mention may be a concern. I'm not sure. You definitely have a whole bunch of ASUS networking products. I did enable Smart Connect and all defaults. Seems to work for me at least but we are at about 30 devices, not 130, in a 4200 sq ft home....
So in preparation to send it in for RMA, I removed all nodes and factory reset.
Some changes I noticed:
I am no longer getting any of the IP log errors, none of the device is not aimesh node cant update/delete it etc.
I am not seeing the IP is in use cant use it error (though this could be because about only 80 devices have reconnected so far)
When viewing the network map it lists many devices as static, even though they are set to dhcp and so is the router. don't understand this.
Now instead of those above logs on repeat I have pages and pages of this stuff:
May 16 21:17:12 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind D4:AD:FC:26:A6:69, status: 0, reason: Disassociated due to inactivity (4), rssi:0
May 16 21:17:12 wlceventd: wlceventd_proc_event(508): eth6: Disassoc D4:AD:FC:26:A6:69, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 16 21:17:12 wlceventd: wlceventd_proc_event(527): eth6: Auth 9C:04:A0:95:1D:F7, status: Successful (0), rssi:0
May 16 21:17:12 wlceventd: wlceventd_proc_event(556): eth6: Assoc 9C:04:A0:95:1D:F7, status: Successful (0), rssi:-64
May 16 21:18:10 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 9C:04:A0:09:1F:3F, status: 0, reason: Disassociated due to inactivity (4), rssi:0
May 16 21:18:10 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 9C:04:A0:09:1F:3F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 16 21:18:10 wlceventd: wlceventd_proc_event(527): eth6: Auth E8:DB:84:E1:9B:4A, status: Successful (0), rssi:0
May 16 21:18:10 wlceventd: wlceventd_proc_event(556): eth6: Assoc E8:DB:84:E1:9B:4A, status: Successful (0), rssi:-46
May 16 21:18:13 wlceventd: wlceventd_proc_event(508): eth6: Disassoc E8:DB:84:E1:9B:4A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 16 21:18:13 wlceventd: wlceventd_proc_event(508): eth6: Disassoc E8:DB:84:E1:9B:4A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 16 21:18:13 wlceventd: wlceventd_proc_event(527): eth6: Auth D4:AD:FC:47:4C:CA, status: Successful (0), rssi:0
May 16 21:18:13 wlceventd: wlceventd_proc_event(556): eth6: Assoc D4:AD:FC:47:4C:CA, status: Successful (0), rssi:-49
May 16 21:18:51 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 7C:78:B2:FC:D4:B9, status: 0, reason: Disassociated due to inactivity (4), rssi:0
May 16 21:18:51 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 7C:78:B2:FC:D4:B9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 16 21:18:51 wlceventd: wlceventd_proc_event(527): eth6: Auth D4:AD:FC:41:A3:12, status: Successful (0), rssi:0
May 16 21:18:51 wlceventd: wlceventd_proc_event(556): eth6: Assoc D4:AD:FC:41:A3:12, status: Successful (0), rssi:-43
May 16 21:24:32 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 7C:78:B2:69:D2:6D, status: 0, reason: Disassociated due to inactivity (4), rssi:0
May 16 21:24:32 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 7C:78:B2:69:D2:6D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 16 21:24:32 wlceventd: wlceventd_proc_event(527): eth6: Auth F0:F0:A4:E0:51:D9, status: Successful (0), rssi:0
May 16 21:24:32 wlceventd: wlceventd_proc_event(556): eth6: Assoc F0:F0:A4:E0:51:D9, status: Successful (0), rssi:-64
May 16 21:24:33 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind F0:F0:A4:E0:51:D9, status: 0, reason: Unspecified reason (1), rssi:0
May 16 21:24:33 wlceventd: wlceventd_proc_event(527): eth6: Auth F0:F0:A4:E0:51:D9, status: Successful (0), rssi:0
May 16 21:24:33 wlceventd: wlceventd_proc_event(556): eth6: Assoc F0:F0:A4:E0:51:D9, status: Successful (0), rssi:-61
May 16 21:24:34 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind F0:F0:A4:E0:51:D9, status: 0, reason: Unspecified reason (1), rssi:0
May 16 21:24:34 wlceventd: wlceventd_proc_event(527): eth6: Auth F0:F0:A4:E0:51:D9, status: Successful (0), rssi:0
May 16 21:24:34 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind F0:F0:A4:E0:51:D9, status: 0, reason: Unspecified reason (1), rssi:0
May 16 21:24:34 wlceventd: wlceventd_proc_event(527): eth6: Auth F0:F0:A4:E0:51:D9, status: Successful (0), rssi:0
May 16 21:24:34 wlceventd: wlceventd_proc_event(556): eth6: Assoc F0:F0:A4:E0:51:D9, status: Successful (0), rssi:-60
May 16 21:24:34 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind F0:F0:A4:E0:51:D9, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
May 16 21:24:34 wlceventd: wlceventd_proc_event(527): eth6: Auth D4:AD:FC:19:CD:F0, status: Successful (0), rssi:0
May 16 21:24:35 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind D4:AD:FC:19:CD:F0, status: 0, reason: Unspecified reason (1), rssi:0
May 16 21:24:35 wlceventd: wlceventd_proc_event(527): eth6: Auth D4:AD:FC:19:CD:F0, status: Successful (0), rssi:0
May 16 21:24:35 wlceventd: wlceventd_proc_event(556): eth6: Assoc D4:AD:FC:19:CD:F0, status: Successful (0), rssi:-47
May 16 21:26:58 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 2C:AA:8E:F0:42:7E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 16 21:26:58 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 2C:AA:8E:F0:42:7E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 16 21:26:58 wlceventd: wlceventd_proc_event(527): eth6: Auth 9C:04:A0:93:F5:EF, status: Successful (0), rssi:0
May 16 21:27:03 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 9C:04:A0:93:F5:EF, status: 0, reason: Unspecified reason (1), rssi:0
May 16 21:27:03 wlceventd: wlceventd_proc_event(527): eth6: Auth 9C:04:A0:93:F5:EF, status: Successful (0), rssi:0
May 16 21:27:03 wlceventd: wlceventd_proc_event(556): eth6: Assoc 9C:04:A0:93:F5:EF, status: Successful (0), rssi:-70
May 16 21:31:32 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 7C:78:B2:FD:22:86, status: 0, reason: Disassociated due to inactivity (4), rssi:0
May 16 21:31:32 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 7C:78:B2:FD:22:86, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 16 21:31:32 wlceventd: wlceventd_proc_event(527): eth6: Auth 7C:78:B2:31:2F:F9, status: Successful (0), rssi:0
May 16 21:31:32 wlceventd: wlceventd_proc_event(556): eth6: Assoc 7C:78:B2:31:2F:F9, status: Successful (0), rssi:-38
May 16 21:34:32 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 7C:78:B2:3B:36:96, status: 0, reason: Disassociated due to inactivity (4), rssi:0
May 16 21:34:32 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 7C:78:B2:3B:36:96, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 16 21:34:32 wlceventd: wlceventd_proc_event(527): eth6: Auth E8:DB:84:E1:9B:4A, status: Successful (0), rssi:0
May 16 21:34:32 wlceventd: wlceventd_proc_event(556): eth6: Assoc E8:DB:84:E1:9B:4A, status: Successful (0), rssi:-46
May 16 21:34:34 wlceventd: wlceventd_proc_event(508): eth6: Disassoc E8:DB:84:E1:9B:4A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 16 21:34:34 wlceventd: wlceventd_proc_event(508): eth6: Disassoc E8:DB:84:E1:9B:4A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 16 21:34:34 wlceventd: wlceventd_proc_event(527): eth6: Auth 08:6A:E5:24:C5:84, status: Successful (0), rssi:0
May 16 21:34:34 wlceventd: wlceventd_proc_event(556): eth6: Assoc 08:6A:E5:24:C5:84, status: Successful (0), rssi:-58
May 16 21:34:52 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 2C:D2:6B:BB:28:DF, status: 0, reason: Disassociated due to inactivity (4), rssi:0
May 16 21:34:52 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 2C:D2:6B:BB:28:DF, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 16 21:34:52 wlceventd: wlceventd_proc_event(527): eth6: Auth 7C:A6:B0:10:78:5B, status: Successful (0), rssi:0
May 16 21:34:52 wlceventd: wlceventd_proc_event(556): eth6: Assoc 7C:A6:B0:10:78:5B, status: Successful (0), rssi:-46
Is this normal log type stuff? I'm still getting that disassociated because sending station error and have added a disassociated due to inactivity line but for the most part its all associated and diosassociated log lines. I read on another post regarding a similar issue that eth6 and eth7 are the radios 2.4Ghz and 5Ghz since 90% of my devices are IoT devices it makes sense to see eth6 primarily as they are almost all 2.4 bound.
I'm thinking of starting to reconnect the other two routers leaving the extenders off but reconnecting them not as aimesh nodes but maybe just as an access point? I've never done this just figured it is something I havent tried might as well get some knowledge from it. What are the downsides or upsiodes to having them as AP nodes instead of AIMESH nodes?