Page 2 of 5 FirstFirst 1 2 3 4 ... LastLast
Results 11 to 20 of 42
  1. #11
    ROG Guru: White Belt Array
    Join Date
    Nov 2018
    Reputation
    31
    Posts
    120

    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
    Last edited by JeffLo; 01-25-2021 at 01:45 AM.

  2. #12
    New ROGer Array
    Join Date
    Apr 2020
    Reputation
    10
    Posts
    3

    Red face

    Quote Originally Posted by Howie411 View Post
    So the other day I upgraded again and then did a full reset. I still lost the Sonos sub, but it at least allowed me to re-add it this time using the new firmware.
    Great to hear its working for you> Did you have to modify any of your 2.4 channel settings?

  3. #13
    ROG Guru: White Belt Array
    Join Date
    Nov 2018
    Reputation
    31
    Posts
    120

    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:160: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:160:91:2B, status: Successful (0), rssi:0
    Jan 25 21:45:30 wlceventd: wlceventd_proc_event(490): eth7: Deauth_ind 34:79:160:91:2B, status: 0, reason: Unspecified reason (1), rssi:0
    Jan 25 21:45:30 wlceventd: wlceventd_proc_event(526): eth7: Auth 34:79:160:91:2B, status: Successful (0), rssi:0
    Jan 25 21:45:31 wlceventd: wlceventd_proc_event(555): eth7: Assoc 34:79:160:91:2B, status: Successful (0), rssi:0
    Jan 25 21:46:06 wlceventd: wlceventd_proc_event(490): eth7: Deauth_ind 34:79:160: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:160:91:2B, status: Successful (0), rssi:0
    Jan 25 21:46:43 wlceventd: wlceventd_proc_event(555): eth7: Assoc 34:79:160: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:160: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:160:91:2B, status: Successful (0), rssi:0
    Jan 25 22:14:23 wlceventd: wlceventd_proc_event(555): eth7: Assoc 34:79:160: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

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

    i get this alot

    dnsmasq[3121]: Maximum number of concurrent DNS queries reached (max: 150)

    and i always have to refresh the page cause sometimes it doenst load saying something about DNS problem

  5. #15
    ROG Member Array
    Join Date
    Aug 2015
    Reputation
    10
    Posts
    22

    Quote Originally Posted by Locoone View Post
    Great to hear its working for you> Did you have to modify any of your 2.4 channel settings?


    Spoke to soon. While my sonos is working, other random devices on my 2.4 ghz network randomly have been dropping in and out.

  6. #16
    New ROGer Array
    Join Date
    Jan 2021
    Reputation
    10
    Posts
    2

    after a few problems all is good

    Hi, i bought an AX11000 last week and upgraded to 3.0.0.4.386_41700 before I did anything else.

    After that I moved our 20 or so devices to the Asus and then I set up the vpn fusion connecting to a nordvpn server and all was good.
    The final step was to remove our existing router and connect the Asus directly to the FTTH 1gbs gpon internet using PPoE and IPTV, which went fine.
    A few hours later I noticed the internet connection light was red on the router which was confirmed by checking the Asus app but the internet was actually there the same.
    To cut along story short after a lot of looking at the syslog and with help from forum member on SNB i've managed to get everything going. The issue was the NTP server. The router couldn't get the correct time so that messed everything up. I've finally managed to get it going well and its been solid for over 24hrs.

  7. #17
    ROG Member Array
    Join Date
    Feb 2020
    Reputation
    10
    Posts
    21

    I second the question

    Quote Originally Posted by btrach144 View Post
    Has this fixed AIProtection for anyone?
    I second this question (as do all the other posters....).

    I do not see anything in the release notes related to AIProtection counters.

    I'll report back after I give it a try.

  8. #18
    ROG Member Array
    Join Date
    Feb 2020
    Reputation
    10
    Posts
    21

    Update

    Quote Originally Posted by TheFirf View Post
    I second this question (as do all the other posters....).

    I do not see anything in the release notes related to AIProtection counters.

    I'll report back after I give it a try.
    I thought the new firmware today solved it, I thought I saw a count, but then looked again and all were '0'. Trying to find the test link that should cause the count to go up, but can't find it... will wait longer...

    UPDATE: Counters do seem to be working now, could not find link to test it, but apparently I hit a few incidentally.
    Last edited by TheFirf; 01-27-2021 at 05:17 PM. Reason: Update

  9. #19
    ROG Guru: Yellow Belt Array ahfoo's Avatar
    Join Date
    Jan 2020
    Reputation
    10
    Posts
    165

    Appreciate if anyone can provide or share such site address. Thank you.

  10. #20
    ROG Member Array
    Join Date
    Feb 2020
    Reputation
    10
    Posts
    21

    Link to test AIProtection

    Quote Originally Posted by ahfoo View Post
    Appreciate if anyone can provide or share such site address. Thank you.
    According to my AIProtection details, the site that recorded hits was "wrs49.winshipway.com" which I found just searching for test links. That said, BE CAREFUL using it, as I don't know how malicious it is or if it is not blocked by AIProtection for you, could cause damage...

    So please use with caution if you decide to use it to test.

    Counters are certainly going up slower than I remember from when it worked before, but it could also be I have not been doing a lot of browsing...

    Good luck and hope this helps!

Page 2 of 5 FirstFirst 1 2 3 4 ... LastLast

Tags for this Thread

Posting Permissions

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