AC66U Connection Unstable

[RJB6464]

I have had the RT-AC66U for about 1 year. Performance has been good up until the last couple of months. I am suddenly getting random bursts of disconnects. It will be stable for hours, then it suddenly start having issues where everyone loses internet connection, regardless of range to the wireless. Rebooting the router resets for a few minutes, but then will do it again within a few minutes. This can last for hours. I do not believe it is a traffic issue because it can happen at 3:00 AM as easily as 7PM.

A few points:

1. I have up to 15 clients connected at one time. I have b/g protection enabled so all are N or 4G. I run a separate AP for allowing g clients (PS3, etc.) to connect.

2. I have upgraded to the latest Asus firmware.

3. All clients are 2.4ghz except 1. But the disconnects seem to effect both bandwiths.

4. I am in a reasonably crowded wireless space with many connections nearby. I have run inSSIDer 3 and selected the channel with the least amount of traffic.

5. I am currently running on 20/40 bandwith. I have tried both 20 and 40 with no visable effect.

6. I have reset router to factory defaults. No help.

7. I am hooked to a cable modem.

8. I have always had some range issues. While the router is mounted high on the same floor as most of the receiving hardware, the signal does pass through multiple walls at a 45 degree angle.

I am looking for a protocol to address this so I do not spend a lot of time on things that will be completely ineffective. Things I was considering.

A. AC dual band receivers for the PC's furthest from the Router (AC1900?).

B. If I go with A, Setting up another router I have unused as a wireless N access point.

3. Higher gain antenna (recommendations?)

4. Setting up my extra wireless N router as an access point.

5. New router.

Any suggestions or help are appreciated.

Thanks.

 

[RJB6464]

OK,

This is what I did:

1. Installed Merlin version of firmware version 3.0.0.4.376.470

2. Reset to default and rebuilt from scratch.

3. Reset modem for 15 minutes

4. Installed 2 x PCE-AC68 Adaptor's in the most heavily traffic used PC's. Set them for 5ghz (Units were on 2.4ghz N with most everyone else.)

5. Set up my unused RT-N56U as an N access point.

That done, it did seem to improve everyone's performance and lag.
BUT, I am still getting intermittent drops.

I would appear that my router is still active. It looks to me like my router is losing communications with either the cable modem or TW's back end somewhere. I would like to establish whether this is a setting I have wrong, or do I need to contact TW?

Here is a copy of the Log from the latest drop.
I would appreciate any assistance from someone more qualified than I to assess why this is happening.

Oct 7 14:12:16 WAN Connection: Ethernet link down.
Oct 7 14:12:16 stop_nat_rules: apply the redirect_rules!
Oct 7 14:12:20 dnsmasq[3266]: exiting on receipt of SIGTERM
Oct 7 14:12:20 dnsmasq[3518]: started, version 2.72test3 cachesize 1500
Oct 7 14:12:20 dnsmasq[3518]: warning: interface ppp1* does not currently exist
Oct 7 14:12:20 dnsmasq[3518]: asynchronous logging enabled, queue limit is 5 messages
Oct 7 14:12:20 dnsmasq-dhcp[3518]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Oct 7 14:12:20 dnsmasq[3518]: read /etc/hosts - 5 addresses
Oct 7 14:12:20 dnsmasq[3518]: using nameserver 209.18.47.61#53
Oct 7 14:12:20 dnsmasq[3518]: using nameserver 209.18.47.62#53
Oct 7 14:12:28 WAN Connection: Ethernet link up.
Oct 7 14:12:28 rc_service: wanduck 321:notify_rc restart_wan_if 0
Oct 7 14:12:28 kernel: Attempt to kill tasklet from interrupt
Oct 7 14:12:28 dnsmasq[3518]: read /etc/hosts - 5 addresses
Oct 7 14:12:28 kernel: br0: port 1(vlan1) entering disabled state
Oct 7 14:12:28 miniupnpd[3294]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Oct 7 14:12:28 miniupnpd[3294]: Failed to get IP for interface eth0
Oct 7 14:12:28 miniupnpd[3294]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Oct 7 14:12:28 dnsmasq[3518]: using nameserver 209.18.47.61#53
Oct 7 14:12:28 dnsmasq[3518]: using nameserver 209.18.47.62#53
Oct 7 14:12:28 dnsmasq[3518]: read /etc/hosts - 5 addresses
Oct 7 14:12:28 dnsmasq[3518]: using nameserver 209.18.47.61#53
Oct 7 14:12:28 dnsmasq[3518]: using nameserver 209.18.47.62#53
Oct 7 14:12:28 kernel: br0: port 1(vlan1) entering listening state
Oct 7 14:12:28 kernel: br0: port 1(vlan1) entering learning state
Oct 7 14:12:28 kernel: br0: topology change detected, propagating
Oct 7 14:12:28 kernel: br0: port 1(vlan1) entering forwarding state
Oct 7 14:12:28 dnsmasq[3518]: read /etc/hosts - 5 addresses
Oct 7 14:12:34 WAN Connection: ISP's DHCP did not function properly.
Oct 7 14:13:00 dnsmasq[3518]: read /etc/hosts - 5 addresses
Oct 7 14:13:00 dnsmasq[3518]: using nameserver 209.18.47.61#53
Oct 7 14:13:00 dnsmasq[3518]: using nameserver 209.18.47.62#53
Oct 7 14:13:00 rc_service: udhcpc 3526:notify_rc start_firewall
Oct 7 14:13:00 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Oct 7 14:13:00 dnsmasq[3518]: exiting on receipt of SIGTERM
Oct 7 14:13:00 dnsmasq[3533]: started, version 2.72test3 cachesize 1500
Oct 7 14:13:00 dnsmasq[3533]: warning: interface ppp1* does not currently exist
Oct 7 14:13:00 dnsmasq[3533]: asynchronous logging enabled, queue limit is 5 messages
Oct 7 14:13:00 dnsmasq-dhcp[3533]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Oct 7 14:13:00 dnsmasq[3533]: read /etc/hosts - 5 addresses
Oct 7 14:13:00 dnsmasq[3533]: using nameserver 209.18.47.61#53
Oct 7 14:13:00 dnsmasq[3533]: using nameserver 209.18.47.62#53
Oct 7 14:13:00 rc_service: udhcpc 3526:notify_rc stop_upnp
Oct 7 14:13:00 rc_service: udhcpc 3526:notify_rc start_upnp
Oct 7 14:13:00 rc_service: waitting "stop_upnp" via udhcpc ...
Oct 7 14:13:00 miniupnpd[3294]: shutting down MiniUPnPd
Oct 7 14:13:01 dhcp client: bound 76.169.160.238 via 76.169.160.1 during 74217 seconds.
Oct 7 14:13:01 miniupnpd[3562]: HTTP listening on port 49168
Oct 7 14:13:01 miniupnpd[3562]: Listening for NAT-PMP/PCP traffic on port 5351
Oct 7 14:13:04 WAN Connection: WAN was restored.

 

[RMerlin]

Oct 7 14:12:16 WAN Connection: Ethernet link down.

That line here indicates that either your modem crashed and rebooted, or there is a problem with the Ethernet connection between the router and the modem. This is definitely not a router problem (unless the Ethernet WAN port would be defective).

 

[RJB6464]

That line here indicates that either your modem crashed and rebooted, or there is a problem with the Ethernet connection between the router and the modem. This is definitely not a router problem (unless the Ethernet WAN port would be defective).

Thank you for the response. Not very knowledgeable about the log entries, so I was giving myself a crash course (via the internet) in how to read them. Was coming to the same conclusion. Your answer was welcome reinforcement that I was on the right track.

Reset the modem (Surfboard 6141) (15 mins, no power) and changed the ethernet cable to a CAT6 I had. Going to see if that does the trick. Figured my next steps were:

1. Change Modem (lease from TW).
2. Check ethernet port on Router (is there a way to test? Or just not worth the bother?)

I purchased the router in 7/13, so not sure if the warranty still runs.

Any other suggestions are always welcome.

BTW, love the site. Been lurking for years. You do a great job!

 

[john9527]

It could also be related to your cable signal levels....this thread was about COMCAST but tells you how to access your modem logs and some basic info on reading the modem data.

http://forums.smallnetbuilder.com/showthread.php?t=19041

 

[RJB6464]

Thanks for the advice. Was traveling, but the family reported the problem continued. Happened to me and pulled this off the modem log:

Oct 12 2014 18:58:44 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=94:cc:b9:45:2c:c9;CMTS-MAC=00:01:5c:68:30:75;CM-QOS=1.1;CM-VER=3.0;
Oct 12 2014 18:58:44 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:cc:b9:45:2c:c9;CMTS-MAC=00:01:5c:68:30:75;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:19 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:cc:b9:45:2c:c9;CMTS-MAC=00:01:5c:68:30:75;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=94:cc:b9:45:2c:c9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Oct 12 2014 18:58:01 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=94:cc:b9:45:2c:c9;CMTS-MAC=00:01:5c:68:30:75;CM-QOS=1.1;CM-VER=3.0;
Oct 12 2014 18:57:18 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:cc:b9:45:2c:c9;CMTS-MAC=00:01:5c:68:30:75;CM-QOS=1.1;CM-VER=3.0;
Oct 12 2014 18:47:16 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=94:cc:b9:45:2c:c9;CMTS-MAC=00:01:5c:68:30:75;CM-QOS=1.1;CM-VER=3.0;
Oct 12 2014 18:47:16 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:cc:b9:45:2c:c9;CMTS-MAC=00:01:5c:68:30:75;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:21 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:cc:b9:45:2c:c9;CMTS-MAC=00:01:5c:68:30:75;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=94:cc:b9:45:2c:c9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Oct 12 2014 18:46:30 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=94:cc:b9:45:2c:c9;CMTS-MAC=00:01:5c:68:30:75;CM-QOS=1.1;CM-VER=3.0;
Oct 12 2014 18:46:04 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=94:cc:b9:45:2c:c9;CMTS-MAC=00:01:5c:68:30:75;CM-QOS=1.1;CM-VER=3.0;
Oct 12 2014 18:46:03 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=94:cc:b9:45:2c:c9;CMTS-MAC=00:01:5c:68:30:75;CM-QOS=1.1;CM-VER=3.0;
Oct 12 2014 18:46:02 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:cc:b9:45:2c:c9;CMTS-MAC=00:01:5c:68:30:75;CM-QOS=1.1;CM-VER=3.0;

So I contacted TW. They sent an updated code to the modem and said everything looked good. Only problem they could see was my ping time was "excessive".

Earlier this year the whole neighborhood went out and they found the wires in the vault corroded due to water intrusion. They restrung cable for the whole neighborhood.

Said they are going to send a technician on Friday. Let's see how it goes.