cancel
Showing results for 
Search instead for 
Did you mean: 

GT-AXE11000 - can someone please explain to me what's going on with this?

superdeleted
Level 7
I have hit my limit. Been over 2 weeks troubleshooting with Asus Support and they either can't or they won't explain to me what these log files mean and ultimately why they are happening. I attached what anmounts to the smallest of slivers to what my router has been spitting out over the last couple weeks. I mean I have books and books of this stuff now.

Every search I turn up only a couple threads with people experiencing the same thing but none of reach an answer or if they did it wasn't posted. Asus support won't even address the lines with me. happy to just send me constant faqs to follow that I told them I had already tried them all before I reached out to them because I know thats step one with any support but alas they just keep wanting me to reset like my time means nothing and I could reconnect 120+ devices on the regular. They used to always just reconnect (when I had the AX-86U) but now every reset seems to mean stumbling through 50% of my IoT devices trying to get them to reconnect which is why I would like to understand what is going on in the logs. Some of it I know what it is saying but I don't understand why it would be happening and other parts I just plain am clueless as to what the heck is happening. The main culprits in the log file are as follows:

May 13 00:20:14 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 34:20:03:5C:27:4E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

or

May 13 00:20:17 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 34:20:03:7A:FE:AD, status: 0, reason: Unspecified reason (1), rssi:0

or

May 13 00:20:25 kernel: 7C:78:B2:A8:91:C0 not mesh client, can't update it's ip

or

May 13 00:22:24 kernel: 7E:78:B2:2C:975 not mesh client, can't delete it

and last but not least the one that seems obvious in meaning but reasoning why I dont get:

May 13 00:02:52 kernel: 192.168.50.231 is used by someone else, can't use it


I am happy to share data anyone wants if they can give even the slightest insight. Support finally has given me a RMA number but is it even worth it? I mean I really hope its just a bad unit, if not it'll hit down to my soul spending 600 bucks to get what I thought would be top of the line. As it stands now I am about to switch back to one of my AC86U nodes because at least there I was stable with my devices.

Couple quick things to note about my notes. The router literally never stops until it forces me to reboot because my LAN wont even connect. Otherwise these lines are on constant write. I have also tried tracking the MACs being called out each time but after a couple days of skimming and checking there is no rhyme or reason that I can tell. It's a random group out of all my IoT devices, never the same ones so not sure I can rule out anything as being "the trouble spot" plus like I mentioned I had all the same devices on my AX-86U without much problems. The GT-11000 originally seemed to work fine too I don't know what even happened just one day I would wake up with some device not responding or whatever. The MACs don't seem to pinpoint a singular device or even device grouping.

So thank you for letting me rave and vent for a min. I am a big fan of Asus equipment but this one has started [putting a sour taste in my mouth and it is starting to hurt my work from home requirement.

So anything ANYONE can shed line on dealing with this please let me know. I'm happy to pull any data or cfg file settings or follow whatever troubleshooting anybody has gladly.

Also if I am set to DHCP why is it constantly trying/testing the device of it being aimesh node or why does it want to keep changing the ip of the devices or wanting to delete them?

I am in an AImesh system. Veryv large house with all nodes connected via ethernet backhaul



Thanks ROG Forum!
23,822 Views
37 REPLIES 37

jzchen
Level 14
Hmm. Where to start?....

Very often I check firmware on my 3 ASUS routers (1 router 2 nodes AiMesh) to verify it is the latest. So let's start with that. How many ASUS routers do you have connected together? You have at least 1 GT-AXE11000, are they all updated to latest firmware? You can list them and firmware if you want...

Are you able to find device 192.168.50.231? Under Advanced Settings -> LAN DHCP Server tab under Manual Assignment is Enable Manual Assignment Yes or No? If No select Yes then add that device MAC and the IP 192.168.50.231 on the list. Change that device setting to accept assigned IP address.

EDIT- Do you have non-ASUS access points/router type devices?

jzchen wrote:
Hmm. Where to start?....

Very often I check firmware on my 3 ASUS routers (1 router 2 nodes AiMesh) to verify it is the latest. So let's start with that. How many ASUS routers do you have connected together? You have at least 1 GT-AXE11000, are they all updated to latest firmware? You can list them and firmware if you want...

Are you able to find device 192.168.50.231? Under Advanced Settings -> LAN DHCP Server tab under Manual Assignment is Enable Manual Assignment Yes or No? If No select Yes then add that device MAC and the IP 192.168.50.231 on the list. Change that device setting to accept assigned IP address.

EDIT- Do you have non-ASUS access points/router type devices?


Thanks for the reply! Currently I have all asus networking devices and all with the most updated firmwares (according to the check from a gui). I will confirm that is accurate from the websiute though. My devices are:

1. Asus GT-AXE11000 - 3.0.0.4.386_47875-g7b7d10a
2. Asus RT-AX86U - 3.0.0.4.386_46061-g9a06866
3. Asus RT-AC86U - 3.0.0.4.386_48260-gd4c241c
4. Asus RP-AX56 - 3.0.0.4.386_42860-gcedf3e6
5. Asus RP-AC55 - 3.0.0.4.384_83394-g96badd4

All are hard lined and in ethernet backhaul mode. I do get a warning regarding the RP-AC55 not supporting the feature and that it might have system issues but I have already removed it from the equation for long periods and have had no change except that a few of my devices at that far end of the house have a harder time connecting. When it is connected as an AIMESH node those devices connect. I have recorded nothing different otherwise so I have recently added it back into the fold.

I might be a noob with that second suggestion. My router right now is set to NO for manual assignment. I know how to lookup and find my devices mac addresses but not sure how I would come about the IP when I haven't set any device to use a specific IP they are all supposed to be dynamic. One of the reasons why I'm confused seeing that log because none of my devices have been set to use an assigned IP. At one point I wondered though if maybe I should just go and assign IP's to all my devices but that would be a pretty involved input process (over 130 devices) so have just never gone through with it. If you think that could help I would be willing to try.

Asus has now RMA'd my AXE110000 and wanted me to ship it back to them but the shipping was crazy expensive so I was hoping to find some more things to try before that but nothing has really come up. Luckily I pleaded my case to another support repo who got approval to send me a prepaid mailer to ship it to them. Hoping to do that tomorrow. Just gonna have to move the AX86U back to the forefront for now.

Please update the firmware of your RP-AC55 to 3.0.0.4.384.83577 . ASUS non-US website says this is AiMesh but ASUS US website does not. Either way the 83577 is the latest. Both have same firmware and firmware details confirm AiMesh for this....

Check for firmware update on the web GUI for RT-AX86U, or ask ASUS to send you firmware for your RT-AX86U (may be beta because my RT-AX86U has it): 3.0.0.4.386_48377 . This is my current firmware, but few devices connect to mine compared to you....

Not sure about the device that seems to be set to static IP address. Maybe it's a printer of scanner????

jzchen wrote:
Please update the firmware of your RP-AC55 to 3.0.0.4.384.83577 . ASUS non-US website says this is AiMesh but ASUS US website does not. Either way the 83577 is the latest. Both have same firmware and firmware details confirm AiMesh for this....

Check for firmware update on the web GUI for RT-AX86U, or ask ASUS to send you firmware for your RT-AX86U (may be beta because my RT-AX86U has it): 3.0.0.4.386_48377 . This is my current firmware, but few devices connect to mine compared to you....

Not sure about the device that seems to be set to static IP address. Maybe it's a printer of scanner????


I'll take a look at my craft printer, the main printer I checked and it was set to DHCP. Both are Epson.

My RP-AC55 reports no errors and is AIMESH it is the AC50 that I get that error with but I am going right now to check asus non-us and will grab latest firmwares. I'll look for beta as well.

Better grab US firmware. It's the same says AiMesh. The description of the repeater does not...

I thought I saw a (5) limit on number of AiMesh nodes. If so set up maybe one bridge per 5 routers/APs....

jzchen wrote:
Please update the firmware of your RP-AC55 to 3.0.0.4.384.83577 . ASUS non-US website says this is AiMesh but ASUS US website does not. Either way the 83577 is the latest. Both have same firmware and firmware details confirm AiMesh for this....

Check for firmware update on the web GUI for RT-AX86U, or ask ASUS to send you firmware for your RT-AX86U (may be beta because my RT-AX86U has it): 3.0.0.4.386_48377 . This is my current firmware, but few devices connect to mine compared to you....

Not sure about the device that seems to be set to static IP address. Maybe it's a printer of scanner????


Sorry you had it correct on the 55. I had a brain bubble.

I am unable to find any beta firmware for the ax86u and the most recent asus global shows is 46061. Which non-us asus were you going to?

jzchen wrote:
Please update the firmware of your RP-AC55 to 3.0.0.4.384.83577 . ASUS non-US website says this is AiMesh but ASUS US website does not. Either way the 83577 is the latest. Both have same firmware and firmware details confirm AiMesh for this....

Check for firmware update on the web GUI for RT-AX86U, or ask ASUS to send you firmware for your RT-AX86U (may be beta because my RT-AX86U has it): 3.0.0.4.386_48377 . This is my current firmware, but few devices connect to mine compared to you....

Not sure about the device that seems to be set to static IP address. Maybe it's a printer of scanner????


I'm thinking this thing is just busted.

Do you have any idea on what the sending station is either leaving or left means? or why its checking all these devices whether they are mesh devices or not? Seems strange to me. Going to print out a books worth of logs to send with the rma...

Hopefully my AX86U is ready to take back on the full load again, and this time without an extra AC86U (used to have 2 in my setup but when the axe came along that second one just seemed redundant and I don't want to over saturate so it currently up for sale.

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....

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?