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!
25,505 Views
37 REPLIES 37

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

Do you have any idea on what the sending station is either leaving or left means?

If I am not mistaken, sending station leaving and disassociating devices are normal mesh operations. When your device is determined to be closer to another WIfI broadcast, AIMesh will roam and connect to the better signal, hence you see these messages all the time.



I have seen sooooooo many people complaining though about the random disconnects assosciated with the “device is not mesh client, cant update IP“ and I have also been experiancing this. However, I think I am the only person on this message board with more information on this.

While everybody is quick to complain and post troubleshooting, nobody has actually identified the devices on their network causing this

I have 90-100 devices connected to my AX11000 but only 3 of them spit this error back. Those devices all happen to be my DirecTV recievers. I have the whole home package so these recievers have the ability to create their own little network without needing my network, so I am assuming this is the reason it is reported as not mesh client eventhough I assign IP manually to every single device (Hence how I know what has been reporting the error)


so for those troubleshooting, please post which devices are causing the “not mesh client cant update IP� and whether or not it has additional network connectiviy of some sort. Could it be related?


FYI whats more interesting is most posts that I see on this that show users MAC address in question seem to match the same type of equipment……..Mac addresses begin with

08:EB:74:Xx:Xx:xx not mesh client, can't update it's ip
1C:3A:DE:XX:XX:XX
10:77:B1:xx:xx:xx


All directv genies

I am not 100% sure about this. But I too was seeing many (way too many) "Disassociated because sending station is leaving" and similar/related items in the log on my new GS-AX3000 router. In my case, it was not just that having them in the log was an issue but I could tell from the client list connection times that devices were actually disconnecting and re-connecting again. In my case, ALL of these were for IoT/Smart Home devices on the 2.4G wifi. I read elsewhere that beam forming only really works with devices that know how to deal with it properly. I figured that many of my devices were old and/or cheap and perhaps could not do so properly. So I decided to disable all beam forming on that wifi and it appears that the vast majority of this has stopped. I have one device, an outdoor camera, that is the furthest away from the router and I have seen it loose connection and reconnect in this way when before (with beam forming) it seemed pretty solid. Of course, YMMV. Cheers

RedSector73
Level 12
Try using merlin firmware
https://sourceforge.net/projects/asuswrt-merlin/files/GT-AXE11000/

You can always flash back to Asus firmware, but I've always found merlin was better when I was using Asus Routers.

RedSector73 wrote:
Try using merlin firmware
https://sourceforge.net/projects/asuswrt-merlin/files/GT-AXE11000/

You can always flash back to Asus firmware, but I've always found merlin was better when I was using Asus Routers.


Yeah I tried Merlin, didnt notice a change but will try it again.

Also I wanted to note that looking up the IP it reports as already taken and it is not connected according to the router. So it reports it in use but then doesn't have it listed in the Network Map.

RedSector73 wrote:
Try using merlin firmware
https://sourceforge.net/projects/asuswrt-merlin/files/GT-AXE11000/

You can always flash back to Asus firmware, but I've always found merlin was better when I was using Asus Routers.


If I switch over to Merlin, can it then download newer releases through the admin?

MasterC
Community Admin
Community Admin
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/1nTP7tAK0z79ORy-MTF0eCtuYqDU7SJIy/view?usp=sharing
_____________________________________________________________
FPS, Racing, and VR Gamer / Tech Enthusiast / ROG Admin

MasterC@ROG wrote:
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/1nTP7tAK0z79ORy-MTF0eCtuYqDU7SJIy/view?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.

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

superdeleted wrote:
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.
_____________________________________________________________
FPS, Racing, and VR Gamer / Tech Enthusiast / ROG Admin

MasterC@ROG wrote:
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.