cancel
Showing results for 
Search instead for 
Did you mean: 

ASUS GT-AX11000 Firmware version 9.0.0.4.386.41994 (Beta Version)

cmcher
Level 7
10,048 Views
24 REPLIES 24

CapricornDog
Level 7
Link is bad

ahfoo wrote:
Try here.

https://rog.asus.com/sg/networking/rog-rapture-gt-ax11000-model/helpdesk_bios


That works, thanks, i have not tried this yet, i might give it a test at the weekend though.

JeffLo
Level 10
ive been having to many problems with this GT-AX11000 i think its time to return it and find something better, what you guys think? any recommendations for a better router?

chris_k
Level 8
Been running it for a few days without any problems. I believe its just an update to dnsmasq to fix several security issues.

JeffLo
Level 10
its just sad asus would release a top flagship router with lots of bugs, that lower end cheaper price routers work without any problems

JeffLo
Level 10
Feb 10 11:09:55 wlceventd: wlceventd_proc_event(508): eth7: Disassoc 06:37:79:F9:48:8C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 10 11:09:55 wlceventd: wlceventd_proc_event(508): eth7: Disassoc 06:37:79:F9:48:8C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 10 11:09:56 wlceventd: wlceventd_proc_event(527): eth6: Auth 5A:60:B4:FE:E5:C2, status: Successful (0), rssi:0
Feb 10 11:09:56 wlceventd: wlceventd_proc_event(556): eth6: Assoc 5A:60:B4:FE:E5:C2, status: Successful (0), rssi:0
Feb 10 11:09:59 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 11:09:59 kernel: 5A:60:B4:FE:E5:C2 not mesh client, can't update it's ip
Feb 10 11:09:59 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 11:09:59 kernel: 5A:60:B4:FE:E5:C2 not mesh client, can't update it's ip
Feb 10 11:11:23 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 11:25:02 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 11:35:11 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 11:38:48 wlceventd: wlceventd_proc_event(527): eth6: Auth E0:98:06:B4:5D:45, status: Successful (0), rssi:0
Feb 10 11:38:48 wlceventd: wlceventd_proc_event(556): eth6: Assoc E0:98:06:B4:5D:45, status: Successful (0), rssi:0
Feb 10 11:38:48 wlceventd: wlceventd_proc_event(527): eth6: Auth 8C:AA:B5:E7:FA:51, status: Successful (0), rssi:0
Feb 10 11:38:48 wlceventd: wlceventd_proc_event(556): eth6: Assoc 8C:AA:B5:E7:FA:51, status: Successful (0), rssi:0
Feb 10 11:38:48 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 11:38:48 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 11:39:18 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 11:40:37 wlceventd: wlceventd_proc_event(527): eth6: Auth 1C:15:1F:B1:F7:1F, status: Successful (0), rssi:0
Feb 10 11:40:37 wlceventd: wlceventd_proc_event(556): eth6: Assoc 1C:15:1F:B1:F7:1F, status: Successful (0), rssi:0
Feb 10 11:40:40 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 11:40:48 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 11:41:09 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 1C:15:1F:B1:F7:1F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 10 11:41:09 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 1C:15:1F:B1:F7:1F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 10 11:41:12 wlceventd: wlceventd_proc_event(527): eth6: Auth 1C:15:1F:B1:F7:1F, status: Successful (0), rssi:0
Feb 10 11:41:12 wlceventd: wlceventd_proc_event(556): eth6: Assoc 1C:15:1F:B1:F7:1F, status: Successful (0), rssi:0
Feb 10 11:41:14 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 11:42:19 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 11:50:02 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 1C:15:1F:B1:F7:1F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 10 11:50:02 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 1C:15:1F:B1:F7:1F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 10 12:01:08 kernel: 5A:8B:4C:FF:43:3E not mesh client, can't update it's ip
Feb 10 12:01:08 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 12:01:43 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 12:12:30 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 34:79:16:D0:91:2B, status: 0, reason: Unspecified reason (1), rssi:0
Feb 10 12:12:30 wlceventd: wlceventd_proc_event(527): eth6: Auth 34:79:16:D0:91:2B, status: Successful (0), rssi:0
Feb 10 12:12:30 wlceventd: wlceventd_proc_event(537): eth6: ReAssoc 34:79:16:D0:91:2B, status: Successful (0), rssi:0
Feb 10 12:23:10 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 5A:60:B4:FE:E5:C2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 10 12:23:10 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 5A:60:B4:FE:E5:C2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 10 12:23:10 wlceventd: wlceventd_proc_event(527): eth7: Auth 06:37:79:F9:48:8C, status: Successful (0), rssi:0
Feb 10 12:23:10 wlceventd: wlceventd_proc_event(556): eth7: Assoc 06:37:79:F9:48:8C, status: Successful (0), rssi:0
Feb 10 12:23:11 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 12:23:11 kernel: 06:37:79:F9:48:8C not mesh client, can't update it's ip
Feb 10 12:23:11 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 12:23:11 kernel: 06:37:79:F9:48:8C not mesh client, can't update it's ip
Feb 10 12:24:11 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 12:28:44 wlceventd: wlceventd_proc_event(508): eth7: Disassoc 06:37:79:F9:48:8C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 10 12:28:44 wlceventd: wlceventd_proc_event(508): eth7: Disassoc 06:37:79:F9:48:8C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 10 12:29:02 wlceventd: wlceventd_proc_event(527): eth6: Auth 5A:60:B4:FE:E5:C2, status: Successful (0), rssi:0
Feb 10 12:29:02 wlceventd: wlceventd_proc_event(556): eth6: Assoc 5A:60:B4:FE:E5:C2, status: Successful (0), rssi:0
Feb 10 12:29:05 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 12:29:05 kernel: 5A:60:B4:FE:E5:C2 not mesh client, can't update it's ip
Feb 10 12:29:05 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 12:29:05 kernel: 5A:60:B4:FE:E5:C2 not mesh client, can't update it's ip
Feb 10 12:30:18 kernel: D4:3D:7E:9B:37:FB not mesh client, can't update it's ip
Feb 10 13:04:47 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe832 (36/160)
Feb 10 13:04:47 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Feb 10 13:04:47 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe832
Feb 10 13:04:47 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe932 (40/160)
Feb 10 13:04:47 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Feb 10 13:04:47 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe932
Feb 10 13:04:47 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xea32 (44/160)
Feb 10 13:04:47 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Feb 10 13:04:47 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xea32
Feb 10 13:04:47 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Feb 10 13:04:47 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Feb 10 13:04:47 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xeb32
Feb 10 14:17:01 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe832 (36/160)
Feb 10 14:17:01 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Feb 10 14:17:01 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe832
Feb 10 14:17:01 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xe932 (40/160)
Feb 10 14:17:01 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Feb 10 14:17:01 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xe932
Feb 10 14:17:02 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xea32 (44/160)
Feb 10 14:17:02 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Feb 10 14:17:02 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xea32
Feb 10 14:17:02 acsd: acs_candidate_score_intf(995): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Feb 10 14:17:02 acsd: acs_candidate_score_bgnoise(1312): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Feb 10 14:17:02 acsd: acs_candidate_score_txop(1563): eth7: txop check failed for chanspec: 0xeb32


anyone know why this is? like not mesh the client cant update its ip it my kids computer with wired connection
also bgnoise check failed for chanspec:?

major bug after the like 2 weeks or 1 week (random) of use, a factory reset is needed to fix the router else you cant surf the net even with wan pppoe connected to isp, doing a reboot or on/off will only let me surf like 3mins to 5mins then no more internet

this other probs i still have

1. Client device reconnect, make the device to offline and online again.
2. system stability. wan pppoe gets disconnected and reconnect
3. surfing is unstable sometimes still can surf the need to refresh again and again is it the dnsmasq security problems?

using a cheap tenda ac2100 doest have any problems with this (had to buy a different router to test , its only like 25usd and it doesnt have this problems so sad

JeffLo
Level 10
Feb 13 20:15:56 kernel: 90:2B:D2:86:A7:E1 not mesh client, can't update it's ip
Feb 13 20:15:56 kernel: 18:B5:91:15:9A:6A not mesh client, can't update it's ip
Feb 13 20:16:25 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 90:2B:D2:86:A7:E1, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Feb 13 20:16:25 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 90:2B:D2:86:A7:E1, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 13 20:16:29 kernel: 90:2B:D2:86:A7:E1 not mesh client, can't update it's ip
Feb 13 20:16:29 kernel: 18:B5:91:15:9A:6A not mesh client, can't update it's ip
Feb 13 21:03:36 kernel: 90:2B:D2:86:A7:E1 not mesh client, can't update it's ip
Feb 13 21:03:36 kernel: 18:B5:91:15:9A:6A not mesh client, can't update it's ip
Feb 13 21:45:51 kernel: 90:2B:D2:86:A7:E1 not mesh client, can't update it's ip
Feb 13 21:45:51 kernel: 18:B5:91:15:9A:6A not mesh client, can't update it's ip
Feb 13 22:07:59 kernel: 90:2B:D2:86:A7:E1 not mesh client, can't update it's ip
Feb 13 22:07:59 kernel: 18:B5:91:15:9A:6A not mesh client, can't update it's ip
Feb 13 22:37:26 kernel: 90:2B:D2:86:A7:E1 not mesh client, can't update it's ip
Feb 13 22:37:26 kernel: 18:B5:91:15:9A:6A not mesh client, can't update it's ip
Feb 13 22:41:32 kernel: Warning: ct_time_p->intv 0 ct->blog_key[BLOG_PARAM1_DIR_ORIG 0] 0x0 ct->blog_key[BLOG_PARAM1_DIR_REPLY 1] 0x60000075

still getting random logs
like this
Feb 13 21:45:51 kernel: 18:B5:91:15:9A:6A not mesh client, can't update it's ip
Feb 13 22:07:59 kernel: 90:2B:D2:86:A7:E1 not mesh client, can't update it's ip

this 2 in not part of my network i show them when i connected to check whats goin on dont have internet and my pppoe was disconnected and show that 2 ip and with a name i dont know, when i check on view client list it showed up a few secs and was gone, and after a few min pppoe just connected back, pppoe keeps droping on random also to many bugs on this router