[clue-tech] a network mystery - traceroute

[Collins Richey]

On 4/2/07, David L. Anselmi <anselmi at anselmi.us> wrote:
> Jed S. Baer wrote:
> [...]
> > I dunno if this is still useful to you, Collins, but here's my results,
> > after twiddling my router's firewall settings.
>
> Here are my results from a Comcast box.  You'll notice that both are
> pretty much the same except the UDP is blocked towards the end.  Their
> network is big enough that coming from Littleton makes a difference
> compared to your route from Aurora.  Also, this IP is in NY it seems so
> it's a little ways away.
>
> And traceroute warns you that there are several IPs for www.comcast.net,
> so if it picks different ones each time you'll see different paths, even
> if the routes are fairly stable.  I ran mine to the same IP as your
> Windows trace.  But the ICMP vs. UDP difference is enough to explain
> your results.
>
>
> ~$ traceroute -I 204.127.205.8
> traceroute to 204.127.205.8 (204.127.205.8), 30 hops max, 40 byte packets
>   1  * * *
>   2  ge-2-4-ur01.littleton.co.denver.comcast.net (68.86.105.89)  14.728
> ms  9.993 ms  24.424 ms
>   3  te-8-2-ar01.denver.co.denver.comcast.net (68.86.103.33)  9.263 ms
> 10.207 ms  9.462 ms
>   4  68.86.103.142 (68.86.103.142)  19.223 ms  17.102 ms  11.903 ms
>   5  12.116.159.13 (12.116.159.13)  10.456 ms  12.819 ms  9.472 ms
>   6  tbr2013801.dvmco.ip.att.net (12.123.207.142)  50.605 ms  53.091 ms
>   53.989 ms
>   7  tbr1-cl32.cgcil.ip.att.net (12.122.10.117)  51.916 ms  52.039 ms
> 60.583 ms
>   8  12.122.10.153 (12.122.10.153)  54.577 ms  58.118 ms  60.381 ms
>   9  cr1.n54ny.ip.att.net (12.122.1.189)  53.530 ms  56.999 ms  55.226 ms
> 10  br1-a340s10.n54ny.ip.att.net (12.127.0.78)  56.497 ms  55.353 ms
> 59.235 ms
> 11  12.122.81.245 (12.122.81.245)  70.931 ms  52.606 ms  50.537 ms
> 12  mdf1-gsr12-2-pos-7-0.nyc3.attens.net (12.122.255.162)  50.608 ms
> 52.265 ms  50.334 ms
> 13  sccsbix12-1-4.attbi.com (63.240.64.46)  60.586 ms  58.037 ms  52.546 ms
> 14  * * *
> 15  * * *
> 16  www.comcast.net (204.127.205.8)  52.240 ms  53.895 ms  52.170 ms
>
> ~$ traceroute 204.127.205.8
> traceroute to 204.127.205.8 (204.127.205.8), 30 hops max, 40 byte packets
>   1  * * *
>   2  ge-2-4-ur01.littleton.co.denver.comcast.net (68.86.105.89)  11.896
> ms  11.857 ms  11.542 ms
>   3  te-8-2-ar01.denver.co.denver.comcast.net (68.86.103.33)  21.991 ms
>   11.415 ms  12.643 ms
>   4  68.86.103.142 (68.86.103.142)  17.365 ms  13.933 ms  17.026 ms
>   5  12.116.159.13 (12.116.159.13)  12.855 ms  11.381 ms  18.133 ms
>   6  tbr2013801.dvmco.ip.att.net (12.123.207.142)  54.765 ms  53.666 ms
>   53.059 ms
>   7  tbr1-cl32.cgcil.ip.att.net (12.122.10.117)  66.193 ms  53.323 ms
> 54.345 ms
>   8  12.122.10.153 (12.122.10.153)  56.239 ms  56.056 ms  57.501 ms
>   9  cr1.n54ny.ip.att.net (12.122.1.189)  54.591 ms  54.501 ms  57.653 ms
> 10  br1-a340s10.n54ny.ip.att.net (12.127.0.78)  56.285 ms  58.787 ms
> 58.931 ms
> 11  12.122.81.245 (12.122.81.245)  65.175 ms  54.660 ms  55.564 ms
> 12  mdf1-gsr12-2-pos-7-0.nyc3.attens.net (12.122.255.162)  57.221 ms
> 62.127 ms  55.026 ms
> 13  * * *
> 14  * * *
> 15  * * *
> 16  * * *
>

Meanwhile, I've discovered that the glitches I am experiencing are not
merely DNS. When the hang occurs, I can't ping anything with an IP
address either. I 'll have to gather the data and get on the comcast
forum.

My recent experience requires a network restart to cure the hang which
makes me think that they're dropping the lease.

-- 
Collins Richey
     If you fill your heart with regrets of yesterday and the worries
     of tomorrow, you have no today to be thankful for.