Page 1 of 3 1 2 3 LastLast
Results 1 to 10 of 25
  1. #1
    ROG Member Array
    Join Date
    Dec 2019
    Reputation
    10
    Posts
    5

    ASUS GT-AX11000 Firmware version 9.0.0.4.386.41994 (Beta Version)


  2. #2
    ROG Member Array CapricornDog PC Specs
    CapricornDog PC Specs
    Laptop (Model)Asus K501UX
    MotherboardAsus Rog Strix Z270F
    ProcessorIntel I7 7700K
    Memory (part number)16 GB Corsair
    Graphics Card #1NVidia Titan TX
    MonitorPhillips BDM4037U 40" 4K
    Storage #1Samsung 950Pro M.2 500GB
    Storage #2Seagate Barracuda Pro 2TB 7200RPM
    CPU CoolerCorsair AIO.
    CaseCorsair
    Keyboard Logitech MK710
    Mouse Logitech MK700
    Headset/Speakers JVC Sounbar
    OS Win10 Pro 64Bit
    Network RouterAsus ROG GT-AX11000
    CapricornDog's Avatar
    Join Date
    Jul 2017
    Reputation
    10
    Posts
    11

    Link is bad

  3. #3
    ROG Guru: Yellow Belt Array ahfoo's Avatar
    Join Date
    Jan 2020
    Reputation
    10
    Posts
    131

    Quote Originally Posted by CapricornDog View Post
    Link is bad
    Try here.

    https://rog.asus.com/sg/networking/r.../helpdesk_bios

  4. #4
    ROG Guru: White Belt Array
    Join Date
    Nov 2018
    Reputation
    31
    Posts
    118

    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?

  5. #5
    ROG Member Array CapricornDog PC Specs
    CapricornDog PC Specs
    Laptop (Model)Asus K501UX
    MotherboardAsus Rog Strix Z270F
    ProcessorIntel I7 7700K
    Memory (part number)16 GB Corsair
    Graphics Card #1NVidia Titan TX
    MonitorPhillips BDM4037U 40" 4K
    Storage #1Samsung 950Pro M.2 500GB
    Storage #2Seagate Barracuda Pro 2TB 7200RPM
    CPU CoolerCorsair AIO.
    CaseCorsair
    Keyboard Logitech MK710
    Mouse Logitech MK700
    Headset/Speakers JVC Sounbar
    OS Win10 Pro 64Bit
    Network RouterAsus ROG GT-AX11000
    CapricornDog's Avatar
    Join Date
    Jul 2017
    Reputation
    10
    Posts
    11

    Quote Originally Posted by ahfoo View Post
    That works, thanks, i have not tried this yet, i might give it a test at the weekend though.

  6. #6
    ROG Enthusiast Array
    Join Date
    Jul 2018
    Reputation
    11
    Posts
    68

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

  7. #7
    ROG Guru: White Belt Array
    Join Date
    Nov 2018
    Reputation
    31
    Posts
    118

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

  8. #8
    ROG Guru: White Belt Array
    Join Date
    Nov 2018
    Reputation
    31
    Posts
    118

    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:160:91:2B, status: 0, reason: Unspecified reason (1), rssi:0
    Feb 10 12:12:30 wlceventd: wlceventd_proc_event(527): eth6: Auth 34:79:160:91:2B, status: Successful (0), rssi:0
    Feb 10 12:12:30 wlceventd: wlceventd_proc_event(537): eth6: ReAssoc 34:79:160: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:?

  9. #9
    ROG Guru: White Belt Array
    Join Date
    Nov 2018
    Reputation
    31
    Posts
    118

    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

  10. #10
    ROG Guru: White Belt Array
    Join Date
    Nov 2018
    Reputation
    31
    Posts
    118

    Feb 13 20:15:56 kernel: 90:2B2: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:2B2: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:2B2: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:2B2: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:2B2: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:2B2: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:2B2: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:2B2: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:2B2: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

Page 1 of 3 1 2 3 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •