Author Topic: Host connection lost continues (Read 468 times)

wareagle33 · « **on:** December 05, 2007, 11:49:48 AM »

Here is a new ping plot. using ~250 pings at 2.5 second interval, it clearly shows the bulk of lost packets in near the end on the line. It looks loike an AT&T router.

Target Name: N/A
IP: 206.16.60.38
Date/Time: 12/5/2007 11:37:16 AM to 12/5/2007 11:47:17 AM

Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 241 0 0.0 0 100 0 [10.10.220.1]
2 241 0 0.0 0 149 1 [172.17.107.65]
3 241 1 0.4 2 312 13 rrcs-71-42-119-1.sw.biz.rr.com [71.42.119.1]
4 241 2 0.8 7 211 14 gig3-0-0.austtxa-pe-rtr01.texas.rr.com [24.93.60.157]
5 241 0 0.0 7 188 13 gig2-0-0.wacotxmhe-p-rtr01.texas.rr.com [24.93.60.159]
6 241 0 0.0 5 209 12 gig3-0-0.wacotxmhe-pe-rtr01.texas.rr.com [24.93.60.129]
7 241 4 1.7 7 206 16 gig2-0-0.dllatxl3-p-rtr01.texas.rr.com [24.93.60.131]
8 241 0 0.0 7 23 8 gig4-2-0.dllatxl3-rtr1.texas.rr.com [24.93.60.62]
9 67 1 1.5 11 193 23 [4.79.180.65]
10 241 0 0.0 12 192 21 ae-23-79.car3.Dallas1.Level3.net [4.68.19.69]
11 240 2 0.8 13 199 22 gr1-a340s2.wswdc.ip.att.net [192.205.34.137]
12 240 1 0.4 13 17 15 tbr1.dlstx.ip.att.net [12.123.16.194]
13 240 1 0.4 12 192 18 gar5.dlstx.ip.att.net [12.123.16.209]
14 240 1 0.4 14 25 15 mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
15 239 40 16.7 14 736 18 mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
16 240 1 0.4 13 17 14 [206.16.60.38]

Skuzzy · « **Reply #1 on:** December 05, 2007, 12:16:49 PM »

This is actually pretty interesting. Here is the trace back to you.
---
traceroute 71.42.119.1
traceroute to 71.42.119.1 (71.42.119.1), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.670 ms 0.629 ms 0.550 ms
2 mdf1-gsr12-1-gig-1-1.dal1.attens.net (63.241.192.201) 0.247 ms 0.173 ms 0.160 ms
3 12.122.255.77 (12.122.255.77) 1.054 ms 0.881 ms 0.833 ms
4 12.123.16.214 (12.123.16.214) 1.863 ms 1.968 ms 2.493 ms
5 12.122.86.209 (12.122.86.209) 1.052 ms 1.046 ms 0.997 ms
6 br2-a340s5.wswdc.ip.att.net (192.205.34.138) 1.362 ms 1.375 ms 1.326 ms
7 vlan89.csw3.Dallas1.Level3.ne t (4.68.19.190) 9.874 ms 9.783 ms 1.586 ms
8 ae-81-81.ebr1.Dallas1.Level3.net (4.69.136.129) 10.001 ms 8.524 ms 2.251 ms
9 ae-5-5.car1.Houston1.Level3.net (4.69.132.229) 6.453 ms 6.526 ms 6.264 ms
10 ROADRUNNER.car1.Houston1.Leve l3.net (4.79.88.22) 6.283 ms 6.246 ms 6.273 ms
11 gig1-3.hstntxl3-p-rtr01.texas.rr.com (24.93.60.65) 6.307 ms 6.503 ms 6.272 ms
12 gig3-0-0.hstntxl3-pe-rtr01.texas.rr.com (24.93.60.141) 10.751 ms 10.860 ms 10.819 ms
13 gig2-0-0.hstntxtid-p-rtr01.texas.rr.com (24.93.60.143) 11.113 ms 10.807 ms 10.755 ms
14 gig3-0-0.hstntxtid-pe-rtr01.texas.rr.com (24.93.60.145) 10.756 ms 10.836 ms 10.793 ms
15 gig2-0-0.snantx6000-p-rtr01.texas.rr.com (24.93.60.147) 10.863 ms 10.842 ms 10.874 ms
16 gig3-0-0.snantx6000-pe-rtr01.texas.rr.com (24.93.60.149) 10.867 ms 11.014 ms 10.686 ms
17 gig2-0-0.austtxrdc-p-rtr01.texas.rr.com (24.93.60.151) 10.925 ms 10.895 ms 10.835 ms
18 gig3-0-0.austtxrdc-pe-rtr01.texas.rr.com (24.93.60.153) 10.858 ms 10.746 ms 10.836 ms
19 gig2-0-0.austtxa-p-rtr01.texas.rr.com (24.93.60.155) 11.089 ms * 11.289 ms

Note, the last hop? It times out. This looks like a pure Internet related congestion issue, nothing more than that. Not a lot you or I can do about it.

Although Road Runner sure likes to bounce around in Houston, for some reason. 6 hops just in Houston. I would call it bad routing, but I do not have enough data on the Houston area to make that call.

The thing about traceroutes is the last hop almost always reflects a problem in the return paht back to you. It is a limitation of how traces work.

Level3 is just getting worse and worse. Seems everyone who has any problems has them in the path.

wareagle33 · « **Reply #2 on:** December 05, 2007, 03:37:02 PM »

OK, thanks. I guess the real culprit is Al Gore

Skuzzy · « **Reply #3 on:** December 05, 2007, 04:04:22 PM »

Well, it is interesting to note the route back to you is via Dallas, Houston, San Antonio, then finally Austin, when the route coming from you goies from Autsin to Waco to Dallas.

Somebody seems to be routing in a rather bizarre manner.