What's new

[ROG RAPTURE GT-AX11000] Experiences & Discussion

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

i hope this new firmware hasn't opened a "back door" to the router for whoever that was connected to my router from the USA
(5 05:05:28 pppd[1436]: remote IP address 172.16.11.110)
 
am considering doing the same , i have only until 31st Jan to send it back to Amazon. Couldn't be bothered with daily disconnections and rubbish wifi range on a router that cast £320 !

I have a £20 router that blows it away on stability and wifi range!
 
Going to try previous firmware and see if stable over the weekend, if not just going to return it and go back to 68u until either Zenwifi is released or the x89x


Sent from my iPhone using Tapatalk
 
on the asus, when the connection drops, check in the logs in system tools.
Also, does the router claim to still have a wan address or does it show as disconnected?

One more thing to try as you've mentioned BT and the uptime being in the months range. When you get chance, power off the HG612 for 30 minutes. 30 minutes will cause the bt exchange to recognise an inactive line and during this time the network controller is able to update its config and reset the line to a clean state, then give it another go. Stale vdsl connections aren't always the best connection unfortunately.

ok, so ive disabled the daily self-reboot routine on the router and i did the 30 minute disconnection from BT. When it reconnected it did so a bit faster than before (which is nice).
Will monitor routers behavior over next day or so to see if it loses internet connections .

thanks
 
Thanks, but wont powering off the modem trigger a DLM on my line reducing my speed for 10 days ?

im not 100% sure about the Disconnected status, i think it does say that off the top of my head.

here is my log , i think it went down around 5am (SEE RED TEXT);

My first question is, wtf ? May 5 05:05:28 pppd[1436]: peer from calling number F8:13:08:41:CE:19 authorized . F8:13:08:41:CE:19 is a Nokia device ? I have no nokia devices. Was i hacked ?

Clearly , the date and time was also wrong in the logs ? May 5th ? After reboot at 7:45 this am , this corrected itself ...?

Also, 172.16.11.110 is from (see ip lookup below) again was i being hacked ? ;

Name: PRIVATE-ADDRESS-BBLK-RFC1918-IANA-RESERVED
Handle: NET-172-16-0-0-1
Registration Date: 3/15/94
Range: 172.16.0.0-172.31.255.255
Org: Internet Assigned Numbers Authority
Org Handle: IANA
Address: 12025 Waterfront Drive
Suite 300
City: Los Angeles
State/Province: CA
Postal Code: 90292
Country: United States

and even though it says, May 5 05:05:31 WAN Connection: WAN was restored. I still had to reboot the router at 7:45 to get Internet back ?

(Log Info)

May 5 05:05:16 WAN Connection: Ethernet link down.

May 5 05:05:20 acsd: eth6: Selecting 2g band ACS policy
May 5 05:05:20 wlceventd: wlceventd Start...
May 5 05:05:20 GT-AX11000: start https:8443
May 5 05:05:20 GT-AX11000: start httpd:80
May 5 05:05:20 acsd: acsd_main_loop(1059): sync_id: 57063, status:1, misc.error/abort
May 5 05:05:20 httpd: Generating SSL certificate...
May 5 05:05:20 httpds: Generating SSL certificate...
May 5 05:05:20 acsd: eth6: selected channel spec: 0x1908 (10u)
May 5 05:05:20 acsd: eth6: Adjusted channel spec: 0x1908 (10u)
May 5 05:05:20 acsd: eth6: selected channel spec: 0x1908 (10u)
May 5 05:05:20 acsd: acs_set_chspec: 0x1908 (10u) for reason APCS_INIT
May 5 05:05:20 avahi-daemon[1207]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
May 5 05:05:20 disk monitor: be idle
May 5 05:05:20 NAT Tunnel: AAE Service is stopped
May 5 05:05:20 AAE: AAE Service is started
May 5 05:05:20 hour monitor: daemon is starting
May 5 05:05:20 jffs2: valid logs(1)
May 5 05:05:20 miniupnpd[1283]: version 1.9 started
May 5 05:05:20 miniupnpd[1283]: HTTP listening on port 54074
May 5 05:05:20 Mastiff: init
May 5 05:05:20 miniupnpd[1283]: Listening for NAT-PMP/PCP traffic on port 5351
May 5 05:05:20 wlceventd: wlceventd_proc_event(427): eth6: Auth 3C:D9:2B:A6:E2:49, status: 0, reason: d11 RC reserved (0)
May 5 05:05:20 wlceventd: wlceventd_proc_event(455): eth6: Assoc 3C:D9:2B:A6:E2:49, status: 0, reason: d11 RC reserved (0)
May 5 05:05:20 lldpd[1305]: cannot get ethtool link information with GLINKSETTINGS (requires 4.9+): Operation not permitted
May 5 05:05:21 avahi-daemon[1207]: Alias name "GT-AX11000" successfully established.
May 5 05:05:23 pppd[1436]: pppd 2.4.7 started by admin, uid 0
May 5 05:05:23 kernel: SCSI subsystem initialized
May 5 05:05:23 modprobe: module scsi_wait_scan not found in modules.dep
May 5 05:05:23 modprobe: module mbcache not found in modules.dep
May 5 05:05:23 modprobe: module jbd not found in modules.dep
May 5 05:05:23 modprobe: module ext3 not found in modules.dep
May 5 05:05:23 modprobe: module ext4 not found in modules.dep
May 5 05:05:23 modprobe: module ext2 not found in modules.dep
May 5 05:05:23 kernel: tfat: loading out-of-tree module taints kernel.
May 5 05:05:23 modprobe: module btusbdrv not found in modules.dep
May 5 05:05:24 wlceventd: wlceventd_proc_event(427): eth7: Auth 64:C7:53:76:D6:72, status: 0, reason: d11 RC reserved (0)
May 5 05:05:24 wlceventd: wlceventd_proc_event(455): eth7: Assoc 64:C7:53:76:D6:72, status: 0, reason: d11 RC reserved (0)
May 5 05:05:26 wlceventd: wlceventd_proc_event(427): eth7: Auth F0:86:20:3D:2C:85, status: 0, reason: d11 RC reserved (0)
May 5 05:05:26 wlceventd: wlceventd_proc_event(455): eth7: Assoc F0:86:20:3D:2C:85, status: 0, reason: d11 RC reserved (0)
May 5 05:05:26 WAN Connection: Fail to connect with some issues.
May 5 05:05:26 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link UP at 1000 mbps full duplex
May 5 05:05:27 wlceventd: wlceventd_proc_event(427): eth7: Auth C8:3C:85:49:74:3A, status: 0, reason: d11 RC reserved (0)
May 5 05:05:27 wlceventd: wlceventd_proc_event(455): eth7: Assoc C8:3C:85:49:74:3A, status: 0, reason: d11 RC reserved (0)
May 5 05:05:27 kernel: random: nonblocking pool is initialized
May 5 05:05:28 pppd[1436]: Connected to f8:13:08:41:ce:19 via interface eth0
May 5 05:05:28 pppd[1436]: Connect: ppp0 <--> eth0
May 5 05:05:28 pppd[1436]: CHAP authentication succeeded
May 5 05:05:28 pppd[1436]: peer from calling number F8:13:08:41:CE:19 authorized
May 5 05:05:28 pppd[1436]: local IP address **.***.***.***
May 5 05:05:28 pppd[1436]: remote IP address 172.16.11.110
May 5 05:05:28 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
May 5 05:05:28 wan: finish adding multi routes
May 5 05:05:28 miniupnpd[1283]: shutting down MiniUPnPd
May 5 05:05:28 miniupnpd[1649]: version 1.9 started
May 5 05:05:28 miniupnpd[1649]: HTTP listening on port 50505
May 5 05:05:28 miniupnpd[1649]: Listening for NAT-PMP/PCP traffic on port 5351
May 5 05:05:30 BONDING: option disabled
May 5 05:05:31 WAN Connection: WAN was restored.
May 5 05:05:33 start_ddns: update WWW.NO-IP.COM noip, wan_unit 0
May 5 05:05:33 ddns update: ez-ipupdate: starting...
May 5 05:05:33 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
May 5 05:05:34 ddns update: connected to dynupdate.no-ip.com (52.9.108.157) on port 443.
May 5 05:05:34 wlceventd: wlceventd_proc_event(427): eth7: Auth D4:F5:47:84:C4:C6, status: 0, reason: d11 RC reserved (0)
May 5 05:05:34 ntp: start NTP update
May 5 05:05:34 wlceventd: wlceventd_proc_event(455): eth7: Assoc D4:F5:47:84:C4:C6, status: 0, reason: d11 RC reserved (0)
172.16.11.110 is a private IP, ie LAN network, so it's likely that either your ISP is doing is really weird carrier grade NAT or the hd612 is running DHCP also?
Might be worth just giving the modem a factory reset, not seeing much in those logs to indicate the router is at fault tbh.

Another thing to do if with BT for that IP, (unsure of your ISP). Logon to their website and disable the BT openzone service as that bombards modems with crappy IP ranges which a homehub knows how to deal with but most routers end up discarding it.
 
Last edited:
Pulled the trigger on the Asus ROG Rapture GT-AX11000 (regret selling my Asus RT-AC5300), and I was finally able to get it set up. So far, I'm really liking this router.

But.......

It seems I'm still having the same issues I did when I had the Asus RT-AC5300. The Nest Cam will NOT connect to the router, and it seems that using the "Wireless - Smart Connect Rule" will still put most devices on the 5Ghz-2 band [just as the Asus RT-AC5300 did]. I did get the Nest Cam issue resolved by changing the 2.4GHz radio RSSI setting to 'Greater Than -90dBm' and changing the 'VHT' setting to 'All' on all the wifi radios. Now, NO 5Ghz devices will connect to the 5Ghz-1 band, and instead connect to the 5Ghz-2 band.

In regards to the Nest Cam not connecting to the router, the 'System Log' showed the following:

Jan 26 00:15:12 wlceventd: wlceventd_proc_event(427): eth8: Auth xx:xx:xx:xx:xx:xx, status: 0, reason: d11 RC reserved (0)
Jan 26 00:15:12 wlceventd: wlceventd_proc_event(392): eth8: Deauth_ind xx:xx:xx:xx:xx:xx, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)

Any idea what this means?

Has anyone figured out how to get a better "balance" so that both 5GHz bands are balanced w/ connected devices? I'm hoping someone might be able to provide information / settings that would give a more "balanced" connection of devices to each of the 5Ghz bands (5Ghz-1 & 5Ghz-2).

Thanks for the replies :)
 
Last edited:
on the asus, when the connection drops, check in the logs in system tools.
Also, does the router claim to still have a wan address or does it show as disconnected?

One more thing to try as you've mentioned BT and the uptime being in the months range. When you get chance, power off the HG612 for 30 minutes. 30 minutes will cause the bt exchange to recognise an inactive line and during this time the network controller is able to update its config and reset the line to a clean state, then give it another go. Stale vdsl connections aren't always the best connection unfortunately.

"power off the HG612 for 30 minutes. 30 minutes will cause the bt exchange to recognise an inactive line and during this time the network controller is able to update its config and reset the line to a clean state"

So far, this is the best advice i have received in over 2 years. Did what you recommended and my line has now established a much better connection with my exchange!.
until i did this is was getting a rise and fall on a daily basis on my max attainable rate (usually dropped between 10am-6pm). now its rock solid at 82kbps.

better still the router hasn't dropped the pppoe either in the past 2 days (which is a first!).

will monitor over next week and see what happens.

thanks for your excellent advice. I was afraid to do this before as i didn't want a DLM on my line lol !! but am now glad I did it. cheers
 
Last edited:
Glad it's helped.
Dlm isn't always the enemy either, it can screw you if the line profile gets stuck, but generally dlm will only slow you down if the line loses sync a lot and has a lot of CRC errors or frequent disconnects in the space of a few minutes . Once every 24 hours or so/ 30 minute cycle won't count in terms of dlm if powering equipment down.
 
It works like a charm with your settings. Thanks you so much to share them ;)

Thank you for posting, I notice you have Hide SSID set as No for 5GHz-2 (AiMesh), as I walk around my house with three nodes does it auto connect to those or do I have to connect to that Aimesh 5-2? I thought I just connect to 5GHz-1's SSID and it would auto route around.
 
It will auto connect to the 5ghz-2 band if you manually connect once to it as it's a separate ssid if you want to.
I have 90% of devices connected to 5ghz-1 and a few that I want to have full available bandwidth on 5ghz-2. All roams between nodes happily

I don't use smart connect, so don't know if that works any different.
 
Pulled the trigger on the Asus ROG Rapture GT-AX11000 (regret selling my Asus RT-AC5300), and I was finally able to get it set up. So far, I'm really liking this router.

But.......

It seems I'm still having the same issues I did when I had the Asus RT-AC5300. The Nest Cam will NOT connect to the router, and it seems that using the "Wireless - Smart Connect Rule" will still put most devices on the 5Ghz-2 band [just as the Asus RT-AC5300 did]. I did get the Nest Cam issue resolved by changing the 2.4GHz radio RSSI setting to 'Greater Than -90dBm' and changing the 'VHT' setting to 'All' on all the wifi radios. Now, NO 5Ghz devices will connect to the 5Ghz-1 band, and instead connect to the 5Ghz-2 band.

In regards to the Nest Cam not connecting to the router, the 'System Log' showed the following:

Jan 26 00:15:12 wlceventd: wlceventd_proc_event(427): eth8: Auth xx:xx:xx:xx:xx:xx, status: 0, reason: d11 RC reserved (0)
Jan 26 00:15:12 wlceventd: wlceventd_proc_event(392): eth8: Deauth_ind xx:xx:xx:xx:xx:xx, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)

Any idea what this means?

Has anyone figured out how to get a better "balance" so that both 5GHz bands are balanced w/ connected devices? I'm hoping someone might be able to provide information / settings that would give a more "balanced" connection of devices to each of the 5Ghz bands (5Ghz-1 & 5Ghz-2).

Thanks for the replies :)
I am shocked that you are still using that smart connect. You should be having separate 2.4 and 5 Ghz networks. This ends half of the connectivity issues because Asus's algorithm which decides which device will connect which network is as dumb as a dodo.
 
172.16.11.110 is a private IP, ie LAN network, so it's likely that either your ISP is doing is really weird carrier grade NAT or the hd612 is running DHCP also?
Might be worth just giving the modem a factory reset, not seeing much in those logs to indicate the router is at fault tbh.

Another thing to do if with BT for that IP, (unsure of your ISP). Logon to their website and disable the BT openzone service as that bombards modems with crappy IP ranges which a homehub knows how to deal with but most routers end up discarding it.

Modem is just acting as a modem, no DHCP.
Also, given that that strange remote IP address is USA based, and I live in N.Ireland (UK ISP) .... should i not be worried that someone external is connecting to the router ?
 
It's not US based. It is a local internal IP range, so you either have 2 routers on your network or your ISP is using carrier grade NAT to distribute IP's.

If you go to ipchicken what IP range do you get? (Don't type the full address on here just the 1st 2 octets)
 
I am shocked that you are still using that smart connect. You should be having separate 2.4 and 5 Ghz networks. This ends half of the connectivity issues because Asus's algorithm which decides which device will connect which network is as dumb as a dodo.

You don't say......

It was like this back when I had the Asus RT-AC5300. I've always used smart-connect, as it's nice having just one SSID. If I go back to managing the radio's, it will be three SSID's. Now I have to decide which devices go where (5Ghz radio's). :rolleyes:
 
I can get my 5-2 to run at 160 after changing the channel to 100 as recommended within this group but I can’t get my 5-1 to run 160, only goes the 80hz - any ideas?
 
It's not US based. It is a local internal IP range, so you either have 2 routers on your network or your ISP is using carrier grade NAT to distribute IP's.

If you go to ipchicken what IP range do you get? (Don't type the full address on here just the 1st 2 octets)

86.156.

im using one modem, one router and several un-managed switches.
 
Can someone please answer this as I can't get my head around it!

If I have 2.4/5-1 SSID not hidden but my 5GHz-2 set as hide SSID (only want the one showing) does AiMesh still work?
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top