cancel
Showing results for 
Search instead for 
Did you mean: 

GT-AX11000 New Firmware Release Version 3.0.0.4.386.41700

D_McD_EMS_USMC
Level 7
New firmware released:

https://rog.asus.com/us/networking/rog-rapture-gt-ax11000-model/helpdesk_download/

1. AiMesh 2.0 - System optimization: one click in AiMesh to optimize the topology - System Ethernet backhaul mode, all nodes will only connect by ethernet, all bands will be released for wireless clients. - System factory default and reboot. - Client device reconnect, make the device to offline and online again. - Client device binding to specific AP. - Guest WiFi on all Mesh nodes (all node need to upgrade to 3.0.0.4.386 firmware) - Access nodes USB application. Connection priority and Ethernet backhaul mode introduction https://www.asus.com/support/FAQ/1044184 How to setup ASUS AiMesh or ZenWiFi Mesh Ethernet backhaul under different conditions https://www.asus.com/support/FAQ/1044151/

*2. New Family interface in ASUS router App. ASUS Router App for iOS must greater or equal to iOS v1.0.0.5.75 Android version greater or equal to v1.0.0.5.74

*3. The unit of the WiFi time scheduler goes to 1 minute.

*4. Support IPSec IKE v1 and IKE v2, and you can use the Windows 10 native VPN client program to connect to the router's IPSec VPN server. The Windows 10 new FAQ is in https://www.asus.com/support/FAQ/1033576

*5. 2.4 and 5G on the network map could be configured in the same tab.

*6. Captcha for login can be disabled in administration -> system.

*7. Printer server port can be disabled on the USB app page.

*8. Clients which connect to the guest network can be viewed in the network map -->view list --> interface

*9. Fix Lets encrypt not working properly. 10. Add IPTV supports for specific region.*
239 Views
41 REPLIES 41

JeffLo
Level 10
ive been having connection issue since i started using the GT-AX11000 i keep getting diconnected and conncted every now and then , connected to a fiber router/modem with bridge mode i dont have this problem with a lower end asus ac1300 router

its like every 2weeks of usage i have to factory reset the router and it goes back to normal, then it will start to go crazy again , i have done this reset 3 times already

JeffLo
Level 10
anyone know whats the problem here?

Jan 25 13:43:43 dnsmasq[3121]: Maximum number of concurrent DNS queries reached (max: 150)
Jan 25 21:45:06 wlceventd: wlceventd_proc_event(490): eth7: Deauth_ind 34:79:16:D0:91:2B, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Jan 25 21:45:26 wlceventd: wlceventd_proc_event(526): eth7: Auth 34:79:16:D0:91:2B, status: Successful (0), rssi:0
Jan 25 21:45:30 wlceventd: wlceventd_proc_event(490): eth7: Deauth_ind 34:79:16:D0:91:2B, status: 0, reason: Unspecified reason (1), rssi:0
Jan 25 21:45:30 wlceventd: wlceventd_proc_event(526): eth7: Auth 34:79:16:D0:91:2B, status: Successful (0), rssi:0
Jan 25 21:45:31 wlceventd: wlceventd_proc_event(555): eth7: Assoc 34:79:16:D0:91:2B, status: Successful (0), rssi:0
Jan 25 21:46:06 wlceventd: wlceventd_proc_event(490): eth7: Deauth_ind 34:79:16:D0:91:2B, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Jan 25 21:46:43 wlceventd: wlceventd_proc_event(526): eth7: Auth 34:79:16:D0:91:2B, status: Successful (0), rssi:0
Jan 25 21:46:43 wlceventd: wlceventd_proc_event(555): eth7: Assoc 34:79:16:D0:91:2B, status: Successful (0), rssi:0
Jan 25 21:51:26 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe832 (36/160)
Jan 25 21:51:26 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Jan 25 21:51:26 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe832
Jan 25 21:51:26 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe932 (40/160)
Jan 25 21:51:26 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Jan 25 21:51:26 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe932
Jan 25 21:51:26 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xea32 (44/160)
Jan 25 21:51:26 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Jan 25 21:51:26 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xea32
Jan 25 21:51:26 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Jan 25 21:51:26 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Jan 25 21:51:26 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xeb32
Jan 25 22:02:28 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe832 (36/160)
Jan 25 22:02:28 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Jan 25 22:02:28 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe832
Jan 25 22:02:28 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe932 (40/160)
Jan 25 22:02:28 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Jan 25 22:02:28 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe932
Jan 25 22:02:28 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xea32 (44/160)
Jan 25 22:02:28 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Jan 25 22:02:28 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xea32
Jan 25 22:02:28 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Jan 25 22:02:28 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Jan 25 22:02:28 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xeb32
Jan 25 22:13:08 wlceventd: wlceventd_proc_event(490): eth7: Deauth_ind 34:79:16:D0:91:2B, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Jan 25 22:14:23 wlceventd: wlceventd_proc_event(526): eth7: Auth 34:79:16:D0:91:2B, status: Successful (0), rssi:0
Jan 25 22:14:23 wlceventd: wlceventd_proc_event(555): eth7: Assoc 34:79:16:D0:91:2B, status: Successful (0), rssi:0
Jan 25 22:34:16 wlceventd: wlceventd_proc_event(526): eth6: Auth C2:6B:44:F5:8A:E8, status: Successful (0), rssi:0
Jan 25 22:34:16 wlceventd: wlceventd_proc_event(555): eth6: Assoc C2:6B:44:F5:8A:E8, status: Successful (0), rssi:0
Jan 25 22:39:14 kernel: Warning: ct_time_p->intv 0 ct->blog_key[BLOG_PARAM1_DIR_ORIG 0] 0x0 ct->blog_key[BLOG_PARAM1_DIR_REPLY 1] 0xa00007b2
Jan 25 22:39:14 kernel: Warning: ct_time_p->intv 0 ct->blog_key[BLOG_PARAM1_DIR_ORIG 0] 0x0 ct->blog_key[BLOG_PARAM1_DIR_REPLY 1] 0x60000671
Jan 25 22:39:14 kernel: Warning: ct_time_p->intv 0 ct->blog_key[BLOG_PARAM1_DIR_ORIG 0] 0x0 ct->blog_key[BLOG_PARAM1_DIR_REPLY 1] 0xa00001da
Jan 25 22:39:14 kernel: Warning: ct_time_p->intv 0 ct->blog_key[BLOG_PARAM1_DIR_ORIG 0] 0xa000013b ct->blog_key[BLOG_PARAM1_DIR_REPLY 1] 0xa000013b
Jan 25 22:39:14 kernel: Warning: ct_time_p->intv 0 ct->blog_key[BLOG_PARAM1_DIR_ORIG 0] 0xa00007cc ct->blog_key[BLOG_PARAM1_DIR_REPLY 1] 0xa00007cc
Jan 25 22:39:14 kernel: Warning: ct_time_p->intv 0 ct->blog_key[BLOG_PARAM1_DIR_ORIG 0] 0xa0000458 ct->blog_key[BLOG_PARAM1_DIR_REPLY 1] 0xa0000458
Jan 25 22:39:14 kernel: Warning: ct_time_p->intv 0 ct->blog_key[BLOG_PARAM1_DIR_ORIG 0] 0x6000043c ct->blog_key[BLOG_PARAM1_DIR_REPLY 1] 0x6000043c
Jan 25 22:39:14 kernel: Warning: ct_time_p->intv 0 ct->blog_key[BLOG_PARAM1_DIR_ORIG 0] 0x20000804 ct->blog_key[BLOG_PARAM1_DIR_REPLY 1] 0x20000804
Jan 25 22:39:14 kernel: Warning: ct_time_p->intv 0 ct->blog_key[BLOG_PARAM1_DIR_ORIG 0] 0x60000834 ct->blog_key[BLOG_PARAM1_DIR_REPLY 1] 0x0
Jan 25 22:39:14 kernel: Warning: ct_time_p->intv 0 ct->blog_key[BLOG_PARAM1_DIR_ORIG 0] 0x600008b8 ct->blog_key[BLOG_PARAM1_DIR_REPLY 1] 0x600008b8
Jan 25 22:42:35 kernel: Warning: ct_time_p->intv 0 ct->blog_key[BLOG_PARAM1_DIR_ORIG 0] 0xa00004e5 ct->blog_key[BLOG_PARAM1_DIR_REPLY 1] 0x0
Jan 25 22:42:35 kernel: Warning: ct_time_p->intv 0 ct->blog_key[BLOG_PARAM1_DIR_ORIG 0] 0x60000702 ct->blog_key[BLOG_PARAM1_DIR_REPLY 1] 0x60000702
Jan 25 22:42:35 kernel: Warning: ct_time_p->intv 0 ct->blog_key[BLOG_PARAM1_DIR_ORIG 0] 0xa00004bf ct->blog_key[BLOG_PARAM1_DIR_REPLY 1] 0xa00004bf

JeffLo
Level 10
same not mesh client cant update its ip with random mac address like sometime is my computers or TV or other stuff
like this

Feb 12 20:12:40 kernel: 60:B3:C4:00:A9:6E not mesh client, can't update it's ip



also this

kernel: nf_conntrack: expectation table full
Feb 12 19:58:27 kernel: nf_conntrack: expectation table full
Feb 12 19:58:27 kernel: nf_conntrack: expectation table full
Feb 12 19:58:27 kernel: nf_conntrack: expectation table full
Feb 12 19:58:27 kernel: nf_conntrack: expectation table full
Feb 12 19:58:27 kernel: nf_conntrack: expectation table full
Feb 12 19:58:27 kernel: nf_conntrack: expectation table full
Feb 12 19:58:27 kernel: nf_conntrack: expectation table full
Feb 12 19:58:27 kernel: nf_conntrack: expectation table full
Feb 12 19:58:27 kernel: nf_conntrack: expectation table full
Feb 12 19:58:39 kernel: nf_conntrack: expectation table full
Feb 12 19:58:39 kernel: nf_conntrack: expectation table full
Feb 12 19:58:40 kernel: nf_conntrack: expectation table full
Feb 12 19:58:40 kernel: nf_conntrack: expectation table full
Feb 12 19:59:28 kernel: nf_conntrack: expectation table full
Feb 12 19:59:28 kernel: nf_conntrack: expectation table full
Feb 12 19:59:28 kernel: nf_conntrack: expectation table full
Feb 12 19:59:28 kernel: nf_conntrack: expectation table full
Feb 12 19:59:28 kernel: nf_conntrack: expectation table full
Feb 12 19:59:28 kernel: nf_conntrack: expectation table full
Feb 12 19:59:28 kernel: nf_conntrack: expectation table full
Feb 12 19:59:28 kernel: nf_conntrack: expectation table full
Feb 12 19:59:28 kernel: nf_conntrack: expectation table full
Feb 12 19:59:28 kernel: nf_conntrack: expectation table full
Feb 12 20:00:33 kernel: nf_conntrack: expectation table full
Feb 12 20:00:33 kernel: nf_conntrack: expectation table full
Feb 12 20:00:33 kernel: nf_conntrack: expectation table full
Feb 12 20:00:33 kernel: nf_conntrack: expectation table full
Feb 12 20:00:33 kernel: nf_conntrack: expectation table full
Feb 12 20:00:33 kernel: nf_conntrack: expectation table full
Feb 12 20:00:33 kernel: nf_conntrack: expectation table full
Feb 12 20:00:33 kernel: nf_conntrack: expectation table full
Feb 12 20:00:33 kernel: nf_conntrack: expectation table full
Feb 12 20:00:33 kernel: nf_conntrack: expectation table full
Feb 12 20:00:40 kernel: nf_conntrack: expectation table full
Feb 12 20:01:33 kernel: nf_conntrack: expectation table full
Feb 12 20:01:33 kernel: nf_conntrack: expectation table full
Feb 12 20:01:33 kernel: nf_conntrack: expectation table full
Feb 12 20:01:33 kernel: nf_conntrack: expectation table full
Feb 12 20:01:33 kernel: nf_conntrack: expectation table full
Feb 12 20:01:33 kernel: nf_conntrack: expectation table full
Feb 12 20:01:33 kernel: nf_conntrack: expectation table full
Feb 12 20:01:33 kernel: nf_conntrack: expectation table full
Feb 12 20:01:33 kernel: nf_conntrack: expectation table full
Feb 12 20:02:33 kernel: nf_conntrack: expectation table full
Feb 12 20:02:33 kernel: nf_conntrack: expectation table full
Feb 12 20:02:33 kernel: nf_conntrack: expectation table full
Feb 12 20:02:33 kernel: nf_conntrack: expectation table full
Feb 12 20:02:33 kernel: nf_conntrack: expectation table full
Feb 12 20:02:33 kernel: nf_conntrack: expectation table full
Feb 12 20:02:33 kernel: nf_conntrack: expectation table full
Feb 12 20:02:33 kernel: nf_conntrack: expectation table full
Feb 12 20:02:33 kernel: nf_conntrack: expectation table full
Feb 12 20:02:33 kernel: nf_conntrack: expectation table full
Feb 12 20:02:38 kernel: nf_conntrack: expectation table full
Feb 12 20:02:38 kernel: nf_conntrack: expectation table full
Feb 12 20:02:38 kernel: nf_conntrack: expectation table full
Feb 12 20:02:38 kernel: nf_conntrack: expectation table full
Feb 12 20:03:33 kernel: nf_conntrack: expectation table full
Feb 12 20:03:33 kernel: nf_conntrack: expectation table full
Feb 12 20:03:33 kernel: nf_conntrack: expectation table full
Feb 12 20:03:33 kernel: nf_conntrack: expectation table full
Feb 12 20:03:33 kernel: nf_conntrack: expectation table full
Feb 12 20:03:33 kernel: nf_conntrack: expectation table full
Feb 12 20:03:33 kernel: nf_conntrack: expectation table full
Feb 12 20:03:33 kernel: nf_conntrack: expectation table full
Feb 12 20:03:33 kernel: nf_conntrack: expectation table full
Feb 12 20:03:33 kernel: nf_conntrack: expectation table full
Feb 12 20:04:33 kernel: nf_conntrack: expectation table full
Feb 12 20:04:33 kernel: nf_conntrack: expectation table full
Feb 12 20:04:33 kernel: nf_conntrack: expectation table full
Feb 12 20:04:33 kernel: nf_conntrack: expectation table full
Feb 12 20:04:33 kernel: nf_conntrack: expectation table full
Feb 12 20:04:33 kernel: nf_conntrack: expectation table full
Feb 12 20:04:33 kernel: nf_conntrack: expectation table full
Feb 12 20:04:33 kernel: nf_conntrack: expectation table full
Feb 12 20:04:33 kernel: nf_conntrack: expectation table full
Feb 12 20:04:33 kernel: nf_conntrack: expectation table full
Feb 12 20:04:39 kernel: nf_conntrack: expectation table full
Feb 12 20:04:39 kernel: nf_conntrack: expectation table full
Feb 12 20:04:39 kernel: nf_conntrack: expectation table full
Feb 12 20:05:33 kernel: nf_conntrack: expectation table full
Feb 12 20:05:33 kernel: nf_conntrack: expectation table full
Feb 12 20:05:33 kernel: nf_conntrack: expectation table full
Feb 12 20:05:33 kernel: nf_conntrack: expectation table full
Feb 12 20:05:33 kernel: nf_conntrack: expectation table full
Feb 12 20:05:33 kernel: nf_conntrack: expectation table full
Feb 12 20:05:33 kernel: nf_conntrack: expectation table full
Feb 12 20:05:33 kernel: nf_conntrack: expectation table full
Feb 12 20:05:33 kernel: nf_conntrack: expectation table full
Feb 12 20:05:33 kernel: nf_conntrack: expectation table full
Feb 12 20:06:33 kernel: nf_conntrack: expectation table full
Feb 12 20:06:33 kernel: nf_conntrack: expectation table full
Feb 12 20:06:33 kernel: nf_conntrack: expectation table full
Feb 12 20:06:33 kernel: nf_conntrack: expectation table full
Feb 12 20:06:33 kernel: nf_conntrack: expectation table full
Feb 12 20:06:33 kernel: nf_conntrack: expectation table full
Feb 12 20:06:33 kernel: nf_conntrack: expectation table full
Feb 12 20:06:33 kernel: nf_conntrack: expectation table full
Feb 12 20:06:33 kernel: nf_conntrack: expectation table full
Feb 12 20:06:33 kernel: nf_conntrack: expectation table full
Feb 12 20:06:38 kernel: nf_conntrack: expectation table full
Feb 12 20:06:38 kernel: nf_conntrack: expectation table full
Feb 12 20:07:33 kernel: nf_conntrack: expectation table full
Feb 12 20:07:33 kernel: nf_conntrack: expectation table full
Feb 12 20:07:33 kernel: nf_conntrack: expectation table full
Feb 12 20:07:33 kernel: nf_conntrack: expectation table full
Feb 12 20:07:33 kernel: nf_conntrack: expectation table full
Feb 12 20:07:33 kernel: nf_conntrack: expectation table full
Feb 12 20:07:33 kernel: nf_conntrack: expectation table full
Feb 12 20:07:33 kernel: nf_conntrack: expectation table full
Feb 12 20:07:33 kernel: nf_conntrack: expectation table full
Feb 12 20:07:33 kernel: nf_conntrack: expectation table full
Feb 12 20:07:38 kernel: nf_conntrack: expectation table full
Feb 12 20:07:39 kernel: nf_conntrack: expectation table full
Feb 12 20:08:38 kernel: nf_conntrack: expectation table full
Feb 12 20:08:38 kernel: nf_conntrack: expectation table full
Feb 12 20:08:38 kernel: nf_conntrack: expectation table full
Feb 12 20:08:38 kernel: nf_conntrack: expectation table full
Feb 12 20:08:38 kernel: nf_conntrack: expectation table full
Feb 12 20:08:38 kernel: nf_conntrack: expectation table full
Feb 12 20:08:38 kernel: nf_conntrack: expectation table full
Feb 12 20:08:38 kernel: nf_conntrack: expectation table full
Feb 12 20:08:38 kernel: nf_conntrack: expectation table full
Feb 12 20:08:38 kernel: nf_conntrack: expectation table full
Feb 12 20:09:37 kernel: nf_conntrack: expectation table full
Feb 12 20:09:37 kernel: nf_conntrack: expectation table full
Feb 12 20:09:37 kernel: nf_conntrack: expectation table full
Feb 12 20:09:37 kernel: nf_conntrack: expectation table full
Feb 12 20:09:37 kernel: nf_conntrack: expectation table full
Feb 12 20:09:37 kernel: nf_conntrack: expectation table full
Feb 12 20:09:37 kernel: nf_conntrack: expectation table full
Feb 12 20:09:37 kernel: nf_conntrack: expectation table full
Feb 12 20:09:37 kernel: nf_conntrack: expectation table full
Feb 12 20:09:37 kernel: nf_conntrack: expectation table full
Feb 12 20:10:38 kernel: nf_conntrack: expectation table full
Feb 12 20:10:38 kernel: nf_conntrack: expectation table full
Feb 12 20:10:38 kernel: nf_conntrack: expectation table full
Feb 12 20:10:38 kernel: nf_conntrack: expectation table full
Feb 12 20:10:38 kernel: nf_conntrack: expectation table full
Feb 12 20:10:38 kernel: nf_conntrack: expectation table full
Feb 12 20:10:38 kernel: nf_conntrack: expectation table full
Feb 12 20:10:38 kernel: nf_conntrack: expectation table full
Feb 12 20:10:38 kernel: nf_conntrack: expectation table full
Feb 12 20:10:38 kernel: nf_conntrack: expectation table full
Feb 12 20:11:29 kernel: 60:B3:C4:00:A9:6E not mesh client, can't update it's ip
Feb 12 20:11:38 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe832 (36/160)
Feb 12 20:11:38 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Feb 12 20:11:38 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe832
Feb 12 20:11:38 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe932 (40/160)
Feb 12 20:11:38 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Feb 12 20:11:38 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe932
Feb 12 20:11:38 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xea32 (44/160)
Feb 12 20:11:38 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Feb 12 20:11:38 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xea32
Feb 12 20:11:38 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Feb 12 20:11:38 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Feb 12 20:11:38 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xeb32
Feb 12 20:11:38 kernel: nf_conntrack: expectation table full
Feb 12 20:11:38 kernel: nf_conntrack: expectation table full
Feb 12 20:11:38 kernel: nf_conntrack: expectation table full
Feb 12 20:11:38 kernel: nf_conntrack: expectation table full
Feb 12 20:11:38 kernel: nf_conntrack: expectation table full
Feb 12 20:11:38 kernel: nf_conntrack: expectation table full
Feb 12 20:11:38 kernel: nf_conntrack: expectation table full
Feb 12 20:11:38 kernel: nf_conntrack: expectation table full
Feb 12 20:11:38 kernel: nf_conntrack: expectation table full
Feb 12 20:11:38 kernel: nf_conntrack: expectation table full
Feb 12 20:12:17 ntp: start NTP update
Feb 12 20:12:38 kernel: nf_conntrack: expectation table full
Feb 12 20:12:38 kernel: nf_conntrack: expectation table full
Feb 12 20:12:38 kernel: nf_conntrack: expectation table full
Feb 12 20:12:38 kernel: nf_conntrack: expectation table full
Feb 12 20:12:38 kernel: nf_conntrack: expectation table full
Feb 12 20:12:38 kernel: nf_conntrack: expectation table full
Feb 12 20:12:38 kernel: nf_conntrack: expectation table full
Feb 12 20:12:38 kernel: nf_conntrack: expectation table full
Feb 12 20:12:38 kernel: nf_conntrack: expectation table full
Feb 12 20:12:38 kernel: nf_conntrack: expectation table full
Feb 12 20:12:40 kernel: 60:B3:C4:00:A9:6E not mesh client, can't update it's ip
Feb 12 20:13:39 kernel: nf_conntrack: expectation table full
Feb 12 20:13:39 kernel: nf_conntrack: expectation table full
Feb 12 20:13:39 kernel: nf_conntrack: expectation table full
Feb 12 20:13:39 kernel: nf_conntrack: expectation table full
Feb 12 20:13:39 kernel: nf_conntrack: expectation table full
Feb 12 20:13:39 kernel: nf_conntrack: expectation table full
Feb 12 20:13:39 kernel: nf_conntrack: expectation table full
Feb 12 20:13:39 kernel: nf_conntrack: expectation table full
Feb 12 20:13:39 kernel: nf_conntrack: expectation table full
Feb 12 20:13:39 kernel: nf_conntrack: expectation table full
Feb 12 20:14:39 kernel: nf_conntrack: expectation table full
Feb 12 20:14:39 kernel: nf_conntrack: expectation table full
Feb 12 20:14:39 kernel: nf_conntrack: expectation table full
Feb 12 20:14:39 kernel: nf_conntrack: expectation table full
Feb 12 20:14:39 kernel: nf_conntrack: expectation table full
Feb 12 20:14:39 kernel: nf_conntrack: expectation table full
Feb 12 20:14:39 kernel: nf_conntrack: expectation table full
Feb 12 20:14:39 kernel: nf_conntrack: expectation table full
Feb 12 20:14:39 kernel: nf_conntrack: expectation table full
Feb 12 20:14:39 kernel: nf_conntrack: expectation table full
Feb 12 20:15:38 kernel: nf_conntrack: expectation table full
Feb 12 20:15:38 kernel: nf_conntrack: expectation table full
Feb 12 20:15:38 kernel: nf_conntrack: expectation table full
Feb 12 20:15:38 kernel: nf_conntrack: expectation table full
Feb 12 20:15:38 kernel: nf_conntrack: expectation table full
Feb 12 20:15:38 kernel: nf_conntrack: expectation table full
Feb 12 20:15:38 kernel: nf_conntrack: expectation table full
Feb 12 20:15:38 kernel: nf_conntrack: expectation table full
Feb 12 20:15:38 kernel: nf_conntrack: expectation table full
Feb 12 20:15:39 kernel: nf_conntrack: expectation table full
Feb 12 20:16:38 kernel: nf_conntrack: expectation table full
Feb 12 20:16:38 kernel: nf_conntrack: expectation table full
Feb 12 20:16:38 kernel: nf_conntrack: expectation table full
Feb 12 20:16:38 kernel: nf_conntrack: expectation table full
Feb 12 20:16:38 kernel: nf_conntrack: expectation table full
Feb 12 20:16:38 kernel: nf_conntrack: expectation table full
Feb 12 20:16:38 kernel: nf_conntrack: expectation table full
Feb 12 20:16:38 kernel: nf_conntrack: expectation table full
Feb 12 20:16:38 kernel: nf_conntrack: expectation table full
Feb 12 20:16:38 kernel: nf_conntrack: expectation table full
Feb 12 20:17:24 kernel: 60:B3:C4:00:A9:6E not mesh client, can't update it's ip
Feb 12 20:17:38 kernel: nf_conntrack: expectation table full
Feb 12 20:17:38 kernel: nf_conntrack: expectation table full
Feb 12 20:17:38 kernel: nf_conntrack: expectation table full
Feb 12 20:17:38 kernel: nf_conntrack: expectation table full
Feb 12 20:17:38 kernel: nf_conntrack: expectation table full
Feb 12 20:17:38 kernel: nf_conntrack: expectation table full
Feb 12 20:17:38 kernel: nf_conntrack: expectation table full
Feb 12 20:17:38 kernel: nf_conntrack: expectation table full
Feb 12 20:17:38 kernel: nf_conntrack: expectation table full
Feb 12 20:17:38 kernel: nf_conntrack: expectation table full
Feb 12 20:18:38 kernel: nf_conntrack: expectation table full
Feb 12 20:18:38 kernel: nf_conntrack: expectation table full
Feb 12 20:18:38 kernel: nf_conntrack: expectation table full
Feb 12 20:18:38 kernel: nf_conntrack: expectation table full
Feb 12 20:18:38 kernel: nf_conntrack: expectation table full
Feb 12 20:18:38 kernel: nf_conntrack: expectation table full
Feb 12 20:18:38 kernel: nf_conntrack: expectation table full
Feb 12 20:18:38 kernel: nf_conntrack: expectation table full
Feb 12 20:18:39 kernel: nf_conntrack: expectation table full
Feb 12 20:18:39 kernel: nf_conntrack: expectation table full
Feb 12 20:19:38 kernel: nf_conntrack: expectation table full
Feb 12 20:19:38 kernel: nf_conntrack: expectation table full
Feb 12 20:19:38 kernel: nf_conntrack: expectation table full
Feb 12 20:19:38 kernel: nf_conntrack: expectation table full
Feb 12 20:19:39 kernel: nf_conntrack: expectation table full
Feb 12 20:19:39 kernel: nf_conntrack: expectation table full
Feb 12 20:19:39 kernel: nf_conntrack: expectation table full
Feb 12 20:19:39 kernel: nf_conntrack: expectation table full
Feb 12 20:19:39 kernel: nf_conntrack: expectation table full
Feb 12 20:19:39 kernel: nf_conntrack: expectation table full
Feb 12 20:20:39 kernel: nf_conntrack: expectation table full
Feb 12 20:20:39 kernel: nf_conntrack: expectation table full
Feb 12 20:20:39 kernel: nf_conntrack: expectation table full
Feb 12 20:20:39 kernel: nf_conntrack: expectation table full
Feb 12 20:20:39 kernel: nf_conntrack: expectation table full
Feb 12 20:20:39 kernel: nf_conntrack: expectation table full
Feb 12 20:20:39 kernel: nf_conntrack: expectation table full
Feb 12 20:20:39 kernel: nf_conntrack: expectation table full
Feb 12 20:20:39 kernel: nf_conntrack: expectation table full
Feb 12 20:20:39 kernel: nf_conntrack: expectation table full
Feb 12 20:21:39 kernel: nf_conntrack: expectation table full
Feb 12 20:21:39 kernel: nf_conntrack: expectation table full
Feb 12 20:21:39 kernel: nf_conntrack: expectation table full
Feb 12 20:21:39 kernel: nf_conntrack: expectation table full
Feb 12 20:21:39 kernel: nf_conntrack: expectation table full
Feb 12 20:21:39 kernel: nf_conntrack: expectation table full
Feb 12 20:21:39 kernel: nf_conntrack: expectation table full
Feb 12 20:21:39 kernel: nf_conntrack: expectation table full
Feb 12 20:21:39 kernel: nf_conntrack: expectation table full
Feb 12 20:21:39 kernel: nf_conntrack: expectation table full
Feb 12 20:22:38 kernel: nf_conntrack: expectation table full
Feb 12 20:22:38 kernel: nf_conntrack: expectation table full
Feb 12 20:22:38 kernel: nf_conntrack: expectation table full
Feb 12 20:22:38 kernel: nf_conntrack: expectation table full
Feb 12 20:22:38 kernel: nf_conntrack: expectation table full
Feb 12 20:22:38 kernel: nf_conntrack: expectation table full
Feb 12 20:22:38 kernel: nf_conntrack: expectation table full
Feb 12 20:22:38 kernel: nf_conntrack: expectation table full
Feb 12 20:22:38 kernel: nf_conntrack: expectation table full
Feb 12 20:22:39 kernel: nf_conntrack: expectation table full

JeffLo
Level 10
and this bugs will go away if i reset router and will comeback again after a random time, before it was like more then 2weeks, then 1 week and now sometimes just a few days, its hard to keep on factory reset and set everything up again, like connefting my other gadgets like RGB lights in the rooms and setting up Mi gadgets like fans and other stuffs one by one

JeffLo
Level 10
ok somethign wierd i notice again, sometime my mobile phone wont have internet if its connected to the ax-11000 i have to turn the phone wifi off/on to get a connection again and i think i now know whats the problem, its also something that i notice on my other pc that i give a static ip address, sometimes i get this wired bug that it wont have any internet connection and the fix is i have to change its ip address, like if im using 192.168.1.100 i need to change it to 192.168.1.101 or some other numbers why this has happen a few times already and never have i encountered this with previous router before, its like the ax-11000 would just out of nowhere block or not give internet connection to that ip address

in my mobile phone i think its the same only i didnt list the ip it have previous and its on DCHP so may its giving a new ip when i swicht the wifi of and on again to reconnect

JeffLo
Level 10
if you dont have any problems with your current firmware then dont update , new updates are not 100% trouble free, it might solve a previous one then add another new problem

if it aint broken dont fix it

so i think devnulldump is right asus need to put the off button option back to the ai mesh settings , so it doenst try to keep finding a mesh node and corrupts the router

JeffLo
Level 10
heres a update, i have a 2nd ax11000 lets call it new ax11000

i have the [MacAddress] not mesh client, can't update it's ip on the first ax11000 its a standlone router i dont have ai mesh node only needed 1 router

new ax11000 set it up same thing standalone i still get the [MacAddress] not mesh client, can't update it's ip in the logs, then after a few days i was curios added the first ax11000 as a ai mesh node, now i dont get that random [MacAddress] not mesh client, can't update it's ip

wierd i think its a bug

JeffLo wrote:
heres a update, i have a 2nd ax11000 lets call it new ax11000

i have the [MacAddress] not mesh client, can't update it's ip on the first ax11000 its a standlone router i dont have ai mesh node only needed 1 router

new ax11000 set it up same thing standalone i still get the [MacAddress] not mesh client, can't update it's ip in the logs, then after a few days i was curios added the first ax11000 as a ai mesh node, now i dont get that random [MacAddress] not mesh client, can't update it's ip

wierd i think its a bug



Thanks for your information. As long as i'm using one standalone ax11000 i will postpone the firmware update. The moment there is a need for a second wireless node, i will setup AI mesh and gonna update all nodes to the latest firmware.

It's very weird you don't have the error when there is AI mesh configured and when there is no AI mesh you getting also the "[MacAddress] not mesh client, can't update it's ip" errors.
Seems indeed like a bug to me.

the logs were flooded with those rubbish logs that i need to clear it for the router to work properly. hope some one from Asus is looking at thisÂ*