Router possible intermittent dropping Internet

videobruce

Limp Gawd
Joined
Jan 21, 2005
Messages
412
TP-Link TL-WDT3600 running dd-wrt F/W

I've been having a problem with loosing Internet access. The following is going under the assumption that it may be this Router. The F/W is ww-drt.
The problem has happened more than once, mostly recently. I did upgrade the F/W to 33772 from 33555 a week ago, I don't know if that has made matters worse.

This is all wired Networking, not WiFi.

Specifically, what appears to be happening is it starts out with high latency, or lack of responding to clicking on links withing web pages. It sits for second, then responds. It gets worse until I loose the Internet altogether. Once the Modem rebooted by itself, the other times I did am manual reboot or reset.
I'm not sure it's a Modem (or Spectrum problem, believe it or not). I already have changed out the Modem a couple of weeks ago for a similar problem which doing so did correct.

Now, I'm running a backup Router (Asus RT-N12 D1) which pales compared to the 3600. The dropping the connection hasn't happened yet, but it's too early to tell.

This problem is made worse by the lame and inaccurate indicator LED's on this Zoom 5341 Modem. They can all show ok including the "Online" LED (which is poorly named), but with no Internet access. RF levels are ok, both up & downstream, S/N ratios are also.
Other than thru my browser, I really know that access is lost when one or both 'line' LED's on my OBi202 ATA go dark.

It just seems that something is 'knocking' me 'Offline' or chocking access. The last two times I was just jumping around within & between web sites and forums. Surely nothing 'taxing'. I eventually get 'Could not connect' (mostly timeouts) or similar messages when I go to navigate.

Other than updating the F/W, I have even reset the Router to defaults. I looked at the Router log (which took some navigating around to get it enabled), but it didn't seem to show anything meaningful. I don't have that log I can post.

I really don't want to get another Router, but this is ridiculous.
 
To make matters worse (to troubleshoot) I can do a download 'binge' for an hour or more, maxing out my Internet connection (60M down 5M up) with 10-15 separate downloads and there isn't a glitch (when one would figure that would kill things).
 
Interesting. Well, when something happens like this either it was the upgrade or something else. If it was something else, the Asus will start to show it too. I think time will give you the answer. (n)
 
Put the stock firmware back on the 3600 and see if it happens. DDWRT is good on a lot of hardware, but isn’t a fix all for everything.
 
It's been over 3 days with the Asus, an no issue. Putting the stock F/W back in is a real chore that I'd rather not go thru. I'm planning to put a older version of ww-drt in, but not as old as the one I had from 2 1/2 years ago.

When this happens, running a TraceRoute program returns something like this;
 

Attachments

  • CMTS down 11-11-17.png
    CMTS down 11-11-17.png
    122.4 KB · Views: 11
I would just downgrade the version of ddwrt to the one that worked. Sometimes upgrades cause problems too. With the Asus being solid, that shows your connection isn't the culprit.
 
That all changed yesterday, at least twice it dropped. Once the Modem went into what appears to be a dual reboot cycle, the other time it recovered by itself (no reboot).

Status
SNMP Event Log

Time Priority Description

Mon Dec 11 15:13:51 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Mon Dec 11 15:13:37 2017 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=fc:4a:...
Mon Dec 11 15:13:37 2017 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=fc:4a:...
Mon Dec 11 15:13:16 2017 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Mon Dec 11 15:12:48 2017 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Mon Dec 11 15:12:34 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Mon Dec 11 15:12:34 2017 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Mon Dec 11 15:12:32 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Mon Dec 11 15:12:32 2017 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Mon Dec 11 15:12:25 2017 Warning (5) MDD message timeout;CM-MAC=fc:4a:e9:0a:4e:18;CMTS-MAC=00:01:5...
Mon Dec 11 15:12:25 2017 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Mon Dec 11 15:12:19 2017 Warning (5) MDD message timeout;CM-MAC=fc:4a:e9:0a:4e:18;CMTS-MAC=00:01:5...
Mon Dec 11 15:12:18 2017 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Mon Dec 11 15:11:21 2017 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=fc:4a:...
Mon Dec 11 15:11:21 2017 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=fc:4a:...
Mon Dec 11 15:10:58 2017 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Mon Dec 11 15:10:34 2017 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=fc:4a:...
Mon Dec 11 15:10:34 2017 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=fc:4a:...
Mon Dec 11 15:10:12 2017 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=fc:4a:e9:0a...
Mon Dec 11 15:09:20 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Mon Dec 11 15:08:47 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...

Mon Dec 11 12:03:11 2017 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=fc:4a:...
Mon Dec 11 12:03:11 2017 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=fc:4a:...
Mon Dec 11 12:02:47 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Mon Dec 11 12:01:50 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Mon Dec 11 11:57:21 2017 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=fc:4a:...
Mon Dec 11 11:57:21 2017 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=fc:4a:...
Mon Dec 11 11:56:53 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Mon Dec 11 11:56:20 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...

Thu Dec 07 13:37:23 2017 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=fc:4a:...
Thu Dec 07 13:37:23 2017 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=fc:4a:...
Thu Dec 07 11:25:01 2017 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=fc:4a:...
Thu Dec 07 11:25:01 2017 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=fc:4a:...
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=fc:4a:e9:0a...
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
 
Okay, so then it does look like you need to get your Internet checked out. Luckily, as long as you're seeing an error even with a system directly connected, it's up to your ISP to fix it.
 
Back
Top