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

[superdeleted]

Aiprotection just warns me of 2 things. Having remote access from WAN on and for having UPnP enabled. The UPnp I use to make my plex service work without any issues and the access from WAN I leave on for the smart control options. I did go ahead and turn it off to see if anything changed but still same events. Talking with ASUS Tech Support and they want me to RMA it again. Look like thats what I will be doing I guess. I do miss aimesh so would be nice to usethat feature again if there is an actual hardware issue in my routerIt is just very inconvenient.

[RedSector73]

For Plex instead of using UPnP

https://forums.plex.tv/t/how-to-port...-router/476336

[jzchen]

For remote access from WAN I have it turned off, no warning from AiProtection. My understanding is this is for access to WebGUI for the router configuration pages. I am able to check the Deltran WiFi charger from away, (so long as it has signal to my network). I'm curious if turning it off affects any smart function? Background that I Googled:

https://www.asus.com/support/FAQ/100...5BSign%20In%5D.

[VDash54]

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:3AE:XX:XX:XX
10:77:B1:xx:xx:xx


All directv genies

[Mystik1]

Try using merlin firmware
https://sourceforge.net/projects/asu...s/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?

[dpwhite]

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