AX11000 problems

[JeffLo]

ax11000 been trouble shooting this since last year
the common prob like wifi drop outs and other stuff, but whats wierd is its like a memory leak, after like 2 weeks or more all wifi wont have internet, its connected but zero data will pass thru its like the router is blocking all traffic up and down, but the lan side is fine (sometimes wifi and lan), i swap diff router all is good diff model brand and a cheap one too so its not my isp

the only way i can fix this is by factory reset, reboot and on/off doesnt fix this, is like a memory leak on pc but you need to reset factory defaults to fix it, so i looking for something to replace this ax11000, but if the hardware is the same with the axe11000 just the wifi6E so im afraid its going to have the same problems im having

but i do hope my prob is a isolated case, but some other commong prob ive read on the net with the ax11000 im also getting currently on the beta firmware but still the probs are thier

these are the common errors i see in the system log it flooded with this types of entries

Feb 21 11:05:22 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe832 (36/160)
Feb 21 11:05:22 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Feb 21 11:05:22 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe832
Feb 21 11:05:22 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe932 (40/160)
Feb 21 11:05:22 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Feb 21 11:05:22 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe932
Feb 21 11:05:22 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xea32 (44/160)
Feb 21 11:05:22 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Feb 21 11:05:22 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xea32
Feb 21 11:05:22 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Feb 21 11:05:22 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Feb 21 11:05:22 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xeb32
Feb 21 11:16:24 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe832 (36/160)
Feb 21 11:16:24 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Feb 21 11:16:24 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe832
Feb 21 11:16:24 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe932 (40/160)
Feb 21 11:16:24 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Feb 21 11:16:24 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe932
Feb 21 11:16:24 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xea32 (44/160)
Feb 21 11:16:24 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Feb 21 11:16:24 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xea32
Feb 21 11:16:24 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Feb 21 11:16:24 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Feb 21 11:16:24 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xeb32
Feb 21 11:27:26 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe832 (36/160)
Feb 21 11:27:26 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Feb 21 11:27:26 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe832
Feb 21 11:27:26 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe932 (40/160)
Feb 21 11:27:26 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Feb 21 11:27:26 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe932
Feb 21 11:27:26 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xea32 (44/160)
Feb 21 11:27:26 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Feb 21 11:27:26 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xea32
Feb 21 11:27:26 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Feb 21 11:27:26 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Feb 21 11:27:26 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xeb32
Feb 21 11:38:27 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe832 (36/160)
Feb 21 11:38:27 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Feb 21 11:38:27 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe832
Feb 21 11:38:27 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe932 (40/160)
Feb 21 11:38:27 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Feb 21 11:38:27 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe932
Feb 21 11:38:27 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xea32 (44/160)
Feb 21 11:38:27 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Feb 21 11:38:27 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xea32
Feb 21 11:38:27 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Feb 21 11:38:27 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Feb 21 11:38:27 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xeb32
Feb 21 11:49:29 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe832 (36/160)
Feb 21 11:49:29 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Feb 21 11:49:29 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe832
Feb 21 11:49:29 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe932 (40/160)
Feb 21 11:49:29 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Feb 21 11:49:29 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe932
Feb 21 11:49:29 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xea32 (44/160)
Feb 21 11:49:29 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Feb 21 11:49:29 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xea32
Feb 21 11:49:29 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Feb 21 11:49:29 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Feb 21 11:49:29 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xeb32
Feb 21 12:00:31 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe832 (36/160)
Feb 21 12:00:31 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Feb 21 12:00:31 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe832
Feb 21 12:00:31 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe932 (40/160)
Feb 21 12:00:31 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Feb 21 12:00:31 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe932
Feb 21 12:00:31 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xea32 (44/160)
Feb 21 12:00:31 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)

and also the

Feb 15 21:30:43 kernel: nf_conntrack: expectation table full
Feb 15 21:30:44 kernel: nf_conntrack: expectation table full
Feb 15 21:30:44 kernel: nf_conntrack: expectation table full
Feb 15 21:30:44 kernel: nf_conntrack: expectation table full
Feb 15 21:30:44 kernel: nf_conntrack: expectation table full
Feb 15 21:30:44 kernel: nf_conntrack: expectation table full
Feb 15 21:30:44 kernel: nf_conntrack: expectation table full
Feb 15 21:30:44 kernel: nf_conntrack: expectation table full
Feb 15 21:30:44 kernel: nf_conntrack: expectation table full
Feb 15 21:31:52 kernel: nf_conntrack: expectation table full
Feb 15 21:31:52 kernel: nf_conntrack: expectation table full

this types of entries

[superdeleted]

So read over this history and it seems you still haven't found a solution? That is discerning as I have this same issue. Pages and pages of the log entries about not mesh client, cant update it's IP or can't delete it or something like eth6: Disassoc 7C:78:B2:31:52:0A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8).


Mine also seemed fine these first couple months I have had it until It one day just would'nt connect. Once I did that reboot then it just tanked. 10+ resets/reboots later and it is stable in the sense it not dropping the connection all together but my smart home devices are still being being randomly disconnected (with the above log entries being reported) and there is no rhyme or reason to the devices at that time. It literally is a different selection of a handful of devices out of my 130+ that are infected that time around.

I've been through Asus support for a couple weeks now and we haven't produced a solution. They also have side stepped my question of what do these logs actually mean.. read it and I understand what it is doing but why is it doing it? When it says not mesh client cant update is it saying that my device isn't a part of my network (since I am setup in a mesh system)

Anyways first asus had me complete a few of their knowledge faqs that most of the switches just caused more problems. The I was escalated to high support who reviewed my case for almost a weekend they came back just saying to try the basic knowledge base faqs - it is like they didn't even review my case or what steps I had already done and just suggested the same thing agin. I replied saying they were running me in circles (though I was a bit more forward about what I personnally personaly said to them and now today their response is to setup the RMA request. So now I am guessing I am waiting for that to come to me to send All this time down is making it a struggle and my work is suffering because of it.

If anyone has any info on what could be going on please reply. If anyone wants any data or for me to try whatever process or change.I am open to everything on. I have countless log files saved im happy to share as well.

update - wanted to note I'm on the AXE11000

[JeffLo]

the not mesh client is gone but i have this new entries whichs wasnt thier before

Mar 11 11:48:57 kernel: 192.168.50.133 already exist in UDB, can't add it
Mar 11 11:49:32 kernel: 192.168.50.133 already exist in UDB, can't add it
Mar 11 12:14:23 kernel: 192.168.50.133 already exist in UDB, can't add it
Mar 11 12:29:38 kernel: 192.168.50.133 already exist in UDB, can't add it
Mar 11 12:29:38 kernel: 192.168.50.133 already exist in UDB, can't add it
Mar 11 12:31:12 kernel: 192.168.50.133 already exist in UDB, can't add it

anyone know what UDB means? the 192.168.50.133 is one of my pc

[Saltgrass]

OK, I don't know what UDB is and don't remember seeing it on my logs. I suppose it could be some type of Data Base.. And, of course you know what that device is..

You should be able to tell what devices have the MAC addresses you show regarding the AiMesh situation. If you go to the AiMesh section, does it show anything regarding AiMesh components? You already know about situations where a neighbor has some devices you are picking up..

There is an option to remove current nodes.. If you knew which devices were being referenced, you could look at them directly and set them back to normal routers or something like a Media Bridge, depending on your needs. If you just switched to a new router that did not have those devices in it memory, the behavior might seem to be normal.

[JeffLo]

update:

the " not mesh client, can't update it's ip " is back

so far net is ok

[JeffLo]

ok this is what i observe now, " not mesh client, can't update it's ip " it also chokes my internet connection for a couple of mins, observe it already when page dont load or cant click anylink due to no internet, i just right away to the system log and check then last entry with the time on the system log and i see this " not mesh client, can't update it's ip "

its short of choking the connection, something is really broken with the firmware code
"

[Saltgrass]

You did say the MAC addresses associated with the "Not AiMesh Client" were a couple of your computers?

If so, have you tried turning them off for a while? Can you see what IP address they are using?

[JeffLo]

also now ive notice , sometimes when i get the dns_prob, err timeout and other problems that has blank browser and telling me no connection i check router it has blinking red light and in wan isp disconnects and later reconnects after a few secound, i cant browse with that, and in the old ax11000 i have to manually refresh the page or hit enter again on the url to reload the page, but in this new ax11000 it will auto reload the page a few secs later, it like its choking but somehow manage to reconnect, but the wierd part is everytime this happens it saying isp disconnected but the online games is still going they dont get disconnected not even lagging, ive manage to notice it while i was browsing, and currently 2 of my kids where playing valorant and i ask them if they disconnected

nope they did not

it only affects the browsing, its kinda wierd, online games not affected, it should also be down right if the wan is disconnected and later reconnected, i think this is a bug on the firmware that affects DNS i think or something, but games not affected

but my old ax11000 has also i think a little hardware prob

[JeffLo]

yes, currently i notice is everytime a connection goes to the router its doing a aimesh check i think thats why the "Not AiMesh Client", if the client keeps droping then the "Not AiMesh Client" keeps showing in the logs, so the wifi is droping a lot same as what others reported unstable wifi

[Saltgrass]

I would think the AiMesh situation was from the Router trying to change an IP address on a Device it thinks is a AiMesh Client. So, what is an AiMesh client.. a device communicating through an AiMesh Node? Didn't you say you are not using AiMesh and have never used it? If the old router had it and the new router also picked it up, something is going on..

Gaming routers have options to set bandwidth for certain streams. Online gaming is probably one of its priorities. The router has several ways to watch network traffic. It might be interesting to get acquainted with that process to see if you notice anything.

Yesterday, I noticed in the System log, a MAC address that started with F4 was being added and removed every 18 seconds. I can not find that MAC address on my system and at 4:16 pm it stopped showing up. I may have made some changes regarding security settings on my Router which stopped it but I still don't know what it was. Possibly, a neighbor or someone sitting in a car trying to hack my network.

I will also say the Wi-Fi Radar option for the Router does not work effectively or I don't know how to use it. The info it provides is inaccurate and meaningless.

[JeffLo]

Saltgrass wrote:
I would think the AiMesh situation was from the Router trying to change an IP address on a Device it thinks is a AiMesh Client. So, what is an AiMesh client.. a device communicating through an AiMesh Node? Didn't you say you are not using AiMesh and have never used it? If the old router had it and the new router also picked it up, something is going on..

before i dont have aimesh now with the extra ax11000 i tried it, it doesnt matter it still checks for aimesh with on with out any other router in the network,

yeah it should not be checking, i think the firmware need to be fix