Page 2 of 4 FirstFirst 1 2 3 4 LastLast
Results 11 to 20 of 35
  1. #11
    New ROGer Array
    Join Date
    Feb 2022
    Reputation
    10
    Posts
    167

    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/HomeNetwork...ng_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....

  2. #12
    New ROGer Array
    Join Date
    May 2022
    Reputation
    10
    Posts
    17

    Quote Originally Posted by jzchen View Post
    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/HomeNetwork...ng_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 E8B:84:E1:9B:4A, status: Successful (0), rssi:0
    May 16 21:18:10 wlceventd: wlceventd_proc_event(556): eth6: Assoc E8B:84:E1:9B:4A, status: Successful (0), rssi:-46
    May 16 21:18:13 wlceventd: wlceventd_proc_event(508): eth6: Disassoc E8B: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 E8B: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:FC4: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:FC4: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:692: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:692: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:519, status: Successful (0), rssi:0
    May 16 21:24:32 wlceventd: wlceventd_proc_event(556): eth6: Assoc F0:F0:A4:E0:519, status: Successful (0), rssi:-64
    May 16 21:24:33 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind F0:F0:A4:E0:519, status: 0, reason: Unspecified reason (1), rssi:0
    May 16 21:24:33 wlceventd: wlceventd_proc_event(527): eth6: Auth F0:F0:A4:E0:519, status: Successful (0), rssi:0
    May 16 21:24:33 wlceventd: wlceventd_proc_event(556): eth6: Assoc F0:F0:A4:E0:519, status: Successful (0), rssi:-61
    May 16 21:24:34 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind F0:F0:A4:E0:519, status: 0, reason: Unspecified reason (1), rssi:0
    May 16 21:24:34 wlceventd: wlceventd_proc_event(527): eth6: Auth F0:F0:A4:E0:519, status: Successful (0), rssi:0
    May 16 21:24:34 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind F0:F0:A4:E0:519, status: 0, reason: Unspecified reason (1), rssi:0
    May 16 21:24:34 wlceventd: wlceventd_proc_event(527): eth6: Auth F0:F0:A4:E0:519, status: Successful (0), rssi:0
    May 16 21:24:34 wlceventd: wlceventd_proc_event(556): eth6: Assoc F0:F0:A4:E0:519, status: Successful (0), rssi:-60
    May 16 21:24:34 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind F0:F0:A4:E0:519, 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 E8B:84:E1:9B:4A, status: Successful (0), rssi:0
    May 16 21:34:32 wlceventd: wlceventd_proc_event(556): eth6: Assoc E8B:84:E1:9B:4A, status: Successful (0), rssi:-46
    May 16 21:34:34 wlceventd: wlceventd_proc_event(508): eth6: Disassoc E8B: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 E8B: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 2C2:6B:BB:28F, status: 0, reason: Disassociated due to inactivity (4), rssi:0
    May 16 21:34:52 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 2C2:6B:BB:28F, 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?

  3. #13
    New ROGer Array
    Join Date
    Feb 2022
    Reputation
    10
    Posts
    167

    Just Checked My Log

    I haven't checked my log because I've been happy with network performance. But my log is riddled by the exact same Deauth Auth DisAssoc ReAssoc plus the not mesh client. Along with other stuff that looks like switching nodes I guess:

    21:00:56 roamast: sta 5E:3B:6C:15:79:BA ap 04:42:1A:4F:48:74 rcpi 82
    May 16 21:00:56 roamast: after rssi -69
    May 16 21:00:56 roamast: sta 5E:3B:6C:15:79:BA ap 7C:10:C9:4E:B9:EC rcpi 90
    May 16 21:00:56 roamast: after rssi -65
    May 16 21:00:56 roamast: determine candidate node [30:5A:3A:C4:3F:5C](rssi: -38dbm) for client [5E:3B:6C:15:79:BA](rssi: -69dbm) to roam

    I guess it's normal???

    I have smart connect enabled...

  4. #14
    Administrator Array MasterC@ROG's Avatar
    Join Date
    Aug 2014
    Reputation
    166
    Posts
    2,094

    Hi There,

    Instead of trying to work out how to interpret the logs, it's easier to use the feedback function from within the router web GUI. Or have you done that already?

    In case you aren't sure about how to do that, here is a guide:
    https://drive.google.com/file/d/1nTP...ew?usp=sharing

  5. #15
    New ROGer Array
    Join Date
    May 2022
    Reputation
    10
    Posts
    17

    Quote Originally Posted by MasterC@ROG View Post
    Hi There,

    Instead of trying to work out how to interpret the logs, it's easier to use the feedback function from within the router web GUI. Or have you done that already?

    In case you aren't sure about how to do that, here is a guide:
    https://drive.google.com/file/d/1nTP...ew?usp=sharing
    Yeah I have used it a couple times at their request. Each time it has sort of felt like a black hole though because I do it and I don't seem to get a response or follow up from it.

  6. #16
    Administrator Array MasterC@ROG's Avatar
    Join Date
    Aug 2014
    Reputation
    166
    Posts
    2,094

    What issues are you having? Or do you just want to know how to read the log?

    Quote Originally Posted by superdeleted View Post
    Yeah I have used it a couple times at their request. Each time it has sort of felt like a black hole though because I do it and I don't seem to get a response or follow up from it.

  7. #17
    New ROGer Array
    Join Date
    May 2022
    Reputation
    10
    Posts
    17

    Quote Originally Posted by MasterC@ROG View Post
    What issues are you having? Or do you just want to know how to read the log?
    Connectivity issues with my devices. Never the same ones always a random sampling it seems out of my 130ish. I however since have switched all my AIMESH nodes to Access Points it "seems" more stable and those specific logs went away so Im guessing it was that RP-55 node (why didnt it have that problem with the ax or ac86u?) but still have like a solid amount to get readded to the network since a bunch had to be switched to connect to whatever AP closest. Plus I am still seeing the disconnects but I have also noticed that they eventually reconnect on their own which they weren't doing before.

    I want to understand the logs so that maybe it clues me into something that is happening over here externally I could adjust I don't know. If I look deep down I think its really because I went from an AX86U that even though ultimately failed and was rma replaced by Asus was solid until that point or even better the AC86U which seems to have performed the best out all three of them yet this router is suppose to be one of their top shelf kind of router, double the cost of the AX I paid for and 3-4x more than the AC.

  8. #18
    Administrator Array MasterC@ROG's Avatar
    Join Date
    Aug 2014
    Reputation
    166
    Posts
    2,094

    Around 130... woah... are you running this for a business? Personally I'm at 25+ and that's already slightly OTT. As each band gets populated (and yours must be very populated), just try a different band (AX11000 is tri-band).

    Sorry, we don't have guides for logs, not something general users want to study nor would we expect them to. You can send off some feedback and private message me your email, I'll help to push the right people.

    Trying to test and optimize networking performance is very technical, far more difficult than a single PC. Every single person has a different scenario, even changing the angle of the antenna can alter the reception or performance. The best thing you can do is follow the guides we have online (YouTUbe), like using an Ethernet backhaul or direct line of sight between the nodes, placing units near windows or staircases if not possible, etc.
    Last edited by MasterC@ROG; 05-20-2022 at 07:42 AM.

  9. #19
    New ROGer Array
    Join Date
    May 2022
    Reputation
    10
    Posts
    17

    Quote Originally Posted by MasterC@ROG View Post
    Around 130... woah... are you running this for a business? Personally I'm at 25+ and that's already slightly OTT. As each band gets populated (and yours must be very populated), just try a different band (AX11000 is tri-band).

    Sorry, we don't have guides for logs, not something general users want to study nor would we expect them to. You can send off some feedback and private message me your email, I'll help to push the right people.

    Trying to test and optimize networking performance is very technical, far more difficult than a single PC. Every single person has a different scenario, even changing the angle of the antenna can alter the reception or performance. The best thing you can do is follow the guides we have online (YouTUbe), like using an Ethernet backhaul or direct line of sight between the nodes, placing units near windows or staircases if not possible, etc.
    Yeah I totally get it and understand. Originally I went to school for this stuff but that was 20 years ago now so much I've missed out on with the features on these things today (god I sound old). I think I just have a hard time letting go when I don't fully understand. Really I'm just trying to learn enough to decide if I really should be RMAing it or not. I am on ethernet backhaul. I run network cables wherever I can so all my nodes were connected via that way, plus then I have two rooms connecting via additional switches that way everything that has the ability to connect with a CAT cable is. The wifi devices are all IoT things, and I have pretty much most things you can think of "smart".

    I'm about to remove the AXE and go back to the setup before to see if I get the results I had before this ROG router because when I had just the ACs or the AX and AC I still had the random disconnect but thos eevents were further apart but if I go back and continue with same results it could maybe just point to something external thats changed.

    As far as the logs I am pretty sure those first ones I questioned were caused by the AC55 node since removing that from the network I havent seen one since. It was either that or changing the nodes to access points. Not sure why it would cause it with the AXE though and not the AX but I also never checked the logs before my original AX died so for all I know it was hitting the same wall.

    And now I'm just droning on. I really do appreciate your input and the time you spent thinking about this. This thread got me to a much better place than where I started it from which I am super grateful for.

  10. #20
    New ROGer Array
    Join Date
    Feb 2022
    Reputation
    10
    Posts
    167

    Did you update the firmware for that AC55 unit there is/was an updated firmware version?

Page 2 of 4 FirstFirst 1 2 3 4 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •