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.
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?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 3C9:2B:A6:E2:49, status: 0, reason: d11 RC reserved (0)
May 5 05:05:20 wlceventd: wlceventd_proc_event(455): eth6: Assoc 3C9: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:766:72, status: 0, reason: d11 RC reserved (0)
May 5 05:05:24 wlceventd: wlceventd_proc_event(455): eth7: Assoc 64:C7:53:766: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)
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.
It works like a charm with your settings. Thanks you so much to share them
It works like a charm with your settings. Thanks you so much to share them
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.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
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.
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.
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)
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!