cancel
Showing results for 
Search instead for 
Did you mean: 

AX11000 problems

JeffLo
Level 10
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
545 Views
87 REPLIES 87

JeffLo
Level 10
also update

when i set the new ax11000 i still get this on the logs

Mar 8 14:49:44 kernel: E0:98:06:B4:5D:45 not mesh client, can't update it's ip
Mar 8 14:49:44 kernel: 8C:AA:B5:E7:FA:51 not mesh client, can't update it's ip
Mar 8 14:49:44 kernel: 60:B3:C4:00:A9:6E not mesh client, can't update it's ip

then i added the old ax11000 as a ai mesh node now i dont this this type of log anymore, so asus need to bring back the option to turn of the ai mesh mode

JeffLo wrote:
when i set the new ax11000 i still get this on the logs

Mar 8 14:49:44 kernel: E0:98:06:B4:5D:45 not mesh client, can't update it's ip
Mar 8 14:49:44 kernel: 8C:AA:B5:E7:FA:51 not mesh client, can't update it's ip
Mar 8 14:49:44 kernel: 60:B3:C4:00:A9:6E not mesh client, can't update it's ip



I get similar messages on my RT-AX92U. See other interesting system log messages at https://www.reddit.com/r/ASUS/comments/nij9aq/asus_router_interesting_log_lines/

is there anyone from Asus looking at this ?

not mesh client, can't delete it

using the latest firmware : 3.0.0.4.386_45375-ge5f218b i am still seeing these

chercm wrote:
is there anyone from Asus looking at this ?

not mesh client, can't delete it

using the latest firmware : 3.0.0.4.386_45375-ge5f218b i am still seeing these


I have this too. It used to be "not mesh client, can't update its IP" but has, with recent firmware turned into "not mesh client, can't delete it".

I find this occurs on iMac and Apple devices mostly, but also Sky HD and other devices. When the router singles out one or two of these devices, the messages continue until an AIMesh reboot, and then there's a chance they don't get picked on. Devices on the end of this tend to loose connections with the internet (but not the LAN).

Have you tired binding the MAC & IP?

PapaVictor wrote:
I have this too. It used to be "not mesh client, can't update its IP" but has, with recent firmware turned into "not mesh client, can't delete it".

I find this occurs on iMac and Apple devices mostly, but also Sky HD and other devices. When the router singles out one or two of these devices, the messages continue until an AIMesh reboot, and then there's a chance they don't get picked on. Devices on the end of this tend to loose connections with the internet (but not the LAN).

Have you tired binding the MAC & IP?


I already log in the issue via Web GUI. I hope all user who encounter this issue can report it too. So Asus may look into this issue.

ahfoo wrote:
I already log in the issue via Web GUI. I hope all user who encounter this issue can report it too. So Asus may look into this issue.


Good idea.

I have done some investigation and this normally affects 1-3 devices until a reboot. Then it can change to other devices.

I have seen this on 2.4Ghz, 5Ghz and wired devices - both MAC/IP bound and unbound, both Node bound and unbound.

Devices getting this log entry get inconsistent access to WAN & LAN

PapaVictor wrote:
Good idea.

I have done some investigation and this normally affects 1-3 devices until a reboot. Then it can change to other devices.

I have seen this on 2.4Ghz, 5Ghz and wired devices - both MAC/IP bound and unbound, both Node bound and unbound.

Devices getting this log entry get inconsistent access to WAN & LAN


My AX11000 disconnects wan and lan devices when it 'crashes',lights on AX11000 also go out.
Does it with all stable releases so far,not tested latest yet though - ROG Rapture GT-AX11000 Version 3.0.0.4.386.45934 (2021/11/10)

I'm using a older beta which works,no disconnects at all but I don't use mesh,just lan and wireless.
Plus my config goes modem-RT5300-AX11000 but neither the modem or the RT crash at all.

link to beta if latest is no good for you.......
https://www.asuswebstorage.com/navigate/a/#/s/4187B178A2164574BE178A44D97422DBY

I can confirm same symptoms and issues with RG-AC5300 and ZenWifi PRO XT12.

Log entries, both variants:


kernel: 7C:2F:80:XX:XX:XX not mesh client, can't update it's ip
kernel: C2:EC:70:XX:XX:XX not mesh client, can't delete it


Issues are also same, router seem to disconnect from WAN.
Outage normally between 2-5 minutes.

GT-AC5300 would show red LED for WAN, but fiber modem would show link, so some connection.
ZenWifi router is brand new but have already had a few outages that feel very similar.

GT-AC5300 had two disting versions of outage, one where it seemed to do a semi-reboot, taking all the WAN/LAN ports down, and the other
where web admin page would be unavailable, web traffic to WAN not working but I'd be able to log in via SSH and reboot the router.

And here I thought it was my old GT-AC5300 with a hw problem...

I also agree that older firmware did not have this problem, it's something that have been introduced.

I don't have a fiber modem, but our cable modem did have similar light indicating signal. BUT when I connected my computer directly to the modem to test, no internet. Eventually my ISP stabilized the connection, (with a reduction in maximum speed though). Did you try to connect your computer directly to the modem to verify there was still internet?

Nope, was too slow so router restored connections first.
System log shows router rebooted with a crashlog that I sent to Asus.
Next time I'll double check the upstream connection too as per your suggestion, but at the moment it seems that the router is the cause (reboot).
Last log entry before reboot was

May 10 15:21:11 ddns: ddns update ok
May 5 07:05:19 crashlog: ^A
May 5 07:05:19 crashlog: <6>br0: port 7(wds2.0.1) entered learning state
May 5 07:05:19 crashlog: <6>CFG80211-ERROR) wl_event_handler :
May 5 07:05:19 crashlog: <4>No wdev corresponding to bssidx: 0x0 found! Ignoring event.
May 5 07:05:19 crashlog: <6>CFG80211-ERROR) wl_event_handler :