Help me read this pathping/fix TWC issues

I

InorganicMatter

[H]F Junkie
Joined
Oct 19, 2004
Messages
15,461
My internet has been terribly unstable the last few months. I've been through two modems and one router, yet the problems persist. I am near convinced the issue is upstream with TWC. My modem is a SB6141, and my router is a WRT54GL running Tomato.

It goes thru two phases. Sometimes it's terribly slow and times out constantly. Then, sometimes it decides to just stop working until I reboot the modem.

Every time it goes down for good, I can dig thru http://192.168.100.1/cmLogs.htm, and see entries like this:

Code: 
Aug 18 2013 21:13:58 	5-Warning 	B502.6 	TEK Invalid - Invalid Key Sequence Number;CM-MAC=e8:6d:52:6e:77:97;CMTS-MAC=00:01:5c:45:6a:47;CM-QOS=1.1;CM-VER=3.0;
Aug 18 2013 11:36:39 	5-Warning 	T202.0 	Lost MDD Timeout;CM-MAC=e8:6d:52:6e:77:97;CMTS-MAC=00:01:5c:45:6a:47;CM-QOS=1.1;CM-VER=3.0;
Aug 18 2013 11:36:20 	3-Critical 	R04.0 	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:6e:77:97;CMTS-MAC=00:01:5c:45:6a:47;CM-QOS=1.1;CM-VER=3.0;
Aug 18 2013 11:36:15 	5-Warning 	T202.0 	Lost MDD Timeout;CM-MAC=e8:6d:52:6e:77:97;CMTS-MAC=00:01:5c:45:6a:47;CM-QOS=1.1;CM-VER=3.0;
Aug 18 2013 11:36:14 	5-Warning 		DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=e8:6d:52:6e:77:97;CMTS-MAC=00:01:5c:45:6a:47;CM-QOS=1.1;CM-VER=3.0;
Aug 18 2013 11:35:47 	6-Notice 		MDD Recovery following MDD Loss;CM-MAC=e8:6d:52:6e:77:97;CMTS-MAC=00:01:5c:45:6a:47;CM-QOS=1.1;CM-VER=3.0;
Aug 18 2013 11:35:45 	5-Warning 	T202.0 	Lost MDD Timeout;CM-MAC=e8:6d:52:6e:77:97;CMTS-MAC=00:01:5c:45:6a:47;CM-QOS=1.1;CM-VER=3.0;
Aug 18 2013 11:35:44 	5-Warning 		DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=e8:6d:52:6e:77:97;CMTS-MAC=00:01:5c:45:6a:47;CM-QOS=1.1;CM-VER=3.0;

I did some searching and saw a suggestion to run a pathping, to try and figure out where I have packet loss along the line. Here is what it generally looks like:

Code: 
Tracing route to 63.240.104.93 over a maximum of 30 hops

  0  Stevoman-HTPC [192.168.1.144] 
  1  192.168.1.1 
  2     *        *     cpe-76-185-8-1.tx.res.rr.com [76.185.8.1] 
  3  tge7-2.dllxtx5101h.texas.rr.com [70.125.218.121] 
  4  tge8-1.dllxtx5102h.texas.rr.com [24.175.39.113] 
  5  tge0-9-0-7.dllatx10-cr02.texas.rr.com [24.175.38.208] 
  6  agg21.hstntxl3-cr01.texas.rr.com [24.175.49.8] 
  7  ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108] 
  8  107.14.17.141 
  9  ip65-47-204-109.z204-47-65.customer.algx.net [65.47.204.109] 
 10  192.205.36.101 
 11  cr2.dlstx.ip.att.net [12.122.100.90] 
 12  cr1.attga.ip.att.net [12.122.28.173] 
 13  cr2.wswdc.ip.att.net [12.122.1.174] 
 14  cr2.n54ny.ip.att.net [12.122.3.37] 
 15  cr1.n54ny.ip.att.net [12.122.2.13] 
 16  gar1.nw2nj.ip.att.net [12.122.131.81] 
 17  12.122.251.10 
 18  mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.240.65.22] 
 19     *        *        *     
Computing statistics for 450 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Stevoman-HTPC [192.168.1.144] 
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1 
                                0/ 100 =  0%   |
  2   17ms     0/ 100 =  0%     0/ 100 =  0%  cpe-76-185-8-1.tx.res.rr.com [76.185.8.1] 
                                0/ 100 =  0%   |
  3   15ms     0/ 100 =  0%     0/ 100 =  0%  tge7-2.dllxtx5101h.texas.rr.com [70.125.218.121] 
                                0/ 100 =  0%   |
  4   17ms     0/ 100 =  0%     0/ 100 =  0%  tge8-1.dllxtx5102h.texas.rr.com [24.175.39.113] 
                                0/ 100 =  0%   |
  5   23ms     0/ 100 =  0%     0/ 100 =  0%  tge0-9-0-7.dllatx10-cr02.texas.rr.com [24.175.38.208] 
                                0/ 100 =  0%   |
  6   20ms     0/ 100 =  0%     0/ 100 =  0%  agg21.hstntxl3-cr01.texas.rr.com [24.175.49.8] 
                                0/ 100 =  0%   |
  7   28ms     0/ 100 =  0%     0/ 100 =  0%  ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108] 
                                0/ 100 =  0%   |
  8   27ms     0/ 100 =  0%     0/ 100 =  0%  107.14.17.141 
                                0/ 100 =  0%   |
  9   26ms     0/ 100 =  0%     0/ 100 =  0%  ip65-47-204-109.z204-47-65.customer.algx.net [65.47.204.109] 
                                0/ 100 =  0%   |
 10   29ms     0/ 100 =  0%     0/ 100 =  0%  192.205.36.101 
                              100/ 100 =100%   |
 11  ---     100/ 100 =100%     0/ 100 =  0%  cr2.dlstx.ip.att.net [12.122.100.90] 
                                0/ 100 =  0%   |
 12  ---     100/ 100 =100%     0/ 100 =  0%  cr1.attga.ip.att.net [12.122.28.173] 
                                0/ 100 =  0%   |
 13  ---     100/ 100 =100%     0/ 100 =  0%  cr2.wswdc.ip.att.net [12.122.1.174] 
                                0/ 100 =  0%   |
 14  ---     100/ 100 =100%     0/ 100 =  0%  cr2.n54ny.ip.att.net [12.122.3.37] 
                                0/ 100 =  0%   |
 15  ---     100/ 100 =100%     0/ 100 =  0%  cr1.n54ny.ip.att.net [12.122.2.13] 
                                0/ 100 =  0%   |
 16  ---     100/ 100 =100%     0/ 100 =  0%  gar1.nw2nj.ip.att.net [12.122.131.81] 
                                0/ 100 =  0%   |
 17  ---     100/ 100 =100%     0/ 100 =  0%  12.122.251.10 
                                0/ 100 =  0%   |
 18  ---     100/ 100 =100%     0/ 100 =  0%  mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.240.65.22] 

Trace complete.

A second one, from my laptop:

Code: 
Tracing route to 63.240.104.93 over a maximum of 30 hops

  0  Stevoman-MBP [192.168.1.136] 
  1  192.168.1.1 
  2  cpe-76-185-8-1.tx.res.rr.com [76.185.8.1] 
  3  tge7-2.dllxtx5101h.texas.rr.com [70.125.218.121] 
  4  tge8-1.dllatx1a-er02.texas.rr.com [24.175.39.113] 
  5  tge0-9-0-7.dllatx10-cr02.texas.rr.com [24.175.38.208] 
  6  agg21.hstntxl3-cr01.texas.rr.com [24.175.49.8] 
  7  ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108] 
  8  107.14.17.141 
  9  ip65-47-204-109.z204-47-65.customer.algx.net [65.47.204.109] 
 10  192.205.36.101 
 11  cr2.dlstx.ip.att.net [12.122.100.90] 
 12  cr1.attga.ip.att.net [12.122.28.173] 
 13  cr2.wswdc.ip.att.net [12.122.1.174] 
 14  cr2.n54ny.ip.att.net [12.122.3.37] 
 15  cr1.n54ny.ip.att.net [12.122.2.13] 
 16  gar1.nw2nj.ip.att.net [12.122.131.81] 
 17  12.122.251.6 
 18  mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.240.65.22] 
 19     *        *        *     
Computing statistics for 450 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Stevoman-MBP [192.168.1.136] 
                                0/ 100 =  0%   |
  1    1ms     1/ 100 =  1%     1/ 100 =  1%  192.168.1.1 
                                0/ 100 =  0%   |
  2   16ms     1/ 100 =  1%     1/ 100 =  1%  cpe-76-185-8-1.tx.res.rr.com [76.185.8.1] 
                                0/ 100 =  0%   |
  3   15ms     2/ 100 =  2%     2/ 100 =  2%  tge7-2.dllxtx5101h.texas.rr.com [70.125.218.121] 
                                0/ 100 =  0%   |
  4   15ms     0/ 100 =  0%     0/ 100 =  0%  tge8-1.dllatx1a-er02.texas.rr.com [24.175.39.113] 
                                1/ 100 =  1%   |
  5   21ms     1/ 100 =  1%     0/ 100 =  0%  tge0-9-0-7.dllatx10-cr02.texas.rr.com [24.175.38.208] 
                                0/ 100 =  0%   |
  6   24ms     1/ 100 =  1%     0/ 100 =  0%  agg21.hstntxl3-cr01.texas.rr.com [24.175.49.8] 
                                0/ 100 =  0%   |
  7   23ms     1/ 100 =  1%     0/ 100 =  0%  ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108] 
                                0/ 100 =  0%   |
  8   28ms     1/ 100 =  1%     0/ 100 =  0%  107.14.17.141 
                                0/ 100 =  0%   |
  9   52ms     1/ 100 =  1%     0/ 100 =  0%  ip65-47-204-109.z204-47-65.customer.algx.net [65.47.204.109] 
                                0/ 100 =  0%   |
 10   34ms     1/ 100 =  1%     0/ 100 =  0%  192.205.36.101 
                               99/ 100 = 99%   |
 11  ---     100/ 100 =100%     0/ 100 =  0%  cr2.dlstx.ip.att.net [12.122.100.90] 
                                0/ 100 =  0%   |
 12  ---     100/ 100 =100%     0/ 100 =  0%  cr1.attga.ip.att.net [12.122.28.173] 
                                0/ 100 =  0%   |
 13  ---     100/ 100 =100%     0/ 100 =  0%  cr2.wswdc.ip.att.net [12.122.1.174] 
                                0/ 100 =  0%   |
 14  ---     100/ 100 =100%     0/ 100 =  0%  cr2.n54ny.ip.att.net [12.122.3.37] 
                                0/ 100 =  0%   |
 15  ---     100/ 100 =100%     0/ 100 =  0%  cr1.n54ny.ip.att.net [12.122.2.13] 
                                0/ 100 =  0%   |
 16  ---     100/ 100 =100%     0/ 100 =  0%  gar1.nw2nj.ip.att.net [12.122.131.81] 
                                0/ 100 =  0%   |
 17  ---     100/ 100 =100%     0/ 100 =  0%  12.122.251.6 
                                0/ 100 =  0%   |
 18  ---     100/ 100 =100%     0/ 100 =  0%  mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.240.65.22] 

Trace complete.

The loss at 192.205.36.101 fluctuates. I've seen 89%, 99%, and in this one it was 100%. I'm guessing this is very wrong, yes?

Does anyone have suggestions? I've talked to TWC many times, and the monkeys on the line always insist "there's no outages in my area". :rolleyes: Bad modem? Something wrong with a hop in/near my apartment? HALP!!
 
It looks like its just blocking Icmp at that point. Your issues sound more related to local issues. Have you checked your splitters, cables, signal strength, etc?

Traceroute and ping are different parts of icmp and can be blocked/ allowed seperately.
 
Last edited:
Traceroute is not a part if ICMP. A traceroute is just playing with the TTL. Normally, it is UDP.

To the OP: The fact that you can ping several hops beyond your router with minimal loss means the connection is working fine at that moment. I suppose when the connection goes down, you will get stalled at the first hop behind your router?
 
Last edited:
Had similar issues with TWC internet dropping, had digital cable installed and while the tech was here I mentioned my issues, he then replaced all the ends on my coaxial cables and no issues since. The explanation I received from the tech was static builds up in the line over time and with bad ends it destroys the signal. maybe something worth looking into?
 
TCM said:
Traceroute is not a part if ICMP. A traceroute is just playing with the TTL. Normally, it is UDP.

To the OP: The fact that you can ping several hops beyond your router with minimal loss means the connection is working fine at that moment. I suppose when the connection goes down, you will get stalled at the first hop behind your router?
Click to expand...

Traceroute uses ICMP. To block it you use an ICMP opinion.
 
"This program attempts to trace the route an IP packet would follow to some internet host by launching UDP probe packets with a small ttl (time to live) then listening for an ICMP "time exceeded" reply from a gateway."

That's a traceroute that existed before Windows and its "tracert" abomination even knew what TCP/IP was.
 
Thanks all, I called TWC (again, for like the 5th time), and the script monkey finally acknowledged a problem with my connection to the node. Tech is coming out Thursday, we'll see.
 
You must log in or register to reply here.
Back
Top