[mythtv-users] Zap2it outage?

[Anthony Floyd]

On 2/9/06, Scott M. Sorrentino <scott at sorrentino.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Have you tried a traceroute or, even better, tcptraceroute to the zap2it site?
> That should give you a good idea of where the path is broken
> (and whom to blame).
>

Good call.  Tracepath (Part of Gentoo's IPUtils package) shows this from home:

 1:  192.168.2.30 (192.168.2.30)                            0.211ms pmtu 1500
 1:  192.168.2.2 (192.168.2.2)                              1.173ms
 2:  10.67.128.1 (10.67.128.1)                             14.420ms
 3:  rd1bb-ge4-0-1.vc.shawcable.net (64.59.159.226)        13.121ms
 4:  rc1bb-pos15-0.vc.shawcable.net (66.163.69.70)         14.793ms
 5:  rc1wt-pos2-2.wa.shawcable.net (66.163.76.54)          16.963ms
 6:  ge-6-7.car4.Seattle1.Level3.net (4.79.106.1)          30.372ms
 7:  ge-1-0-0-55.gar1.Seattle1.Level3.net (4.68.105.137)  asymm  8  17.322ms
 8:  att-level3-oc48.Seattle1.Level3.net (4.68.127.110)    15.730ms
 9:  12.122.84.38 (12.122.84.38)                          asymm 18  70.788ms
10:  tbr2-cl11.cgcil.ip.att.net (12.122.10.61)            asymm 17  70.517ms
11:  gar3-p370.cgcil.ip.att.net (12.123.6.5)              asymm 15  69.154ms

... and everything beyond that times out.

Where as from the work machine (some bits omitted to protect the innocent):

...
 5:  72.51.24.189 (72.51.24.189)                            1.499ms
 6:  oc48pos5-0.sea-dis-2.peer1.net (216.187.88.226)        5.154ms
 7:  216.187.88.178 (216.187.88.178)                        6.317ms
 8:  12.127.70.61 (12.127.70.61)                          asymm 13   5.615ms
 9:  tbr2-p012502.st6wa.ip.att.net (12.123.203.178)       asymm 20  72.089ms
10:  tbr2-cl11.cgcil.ip.att.net (12.122.10.61)            asymm 19  72.412ms
11:  gar3-p370.cgcil.ip.att.net (12.123.6.5)              asymm 17  70.112ms
12:  mdf1-gsr12-2-pos-7-0.chi1.attens.net (12.122.255.194) asymm 18  74.196ms
13:  mdf1-bi8k-1-eth-2-3.chi1.attens.net (63.240.128.190) asymm 19  73.108ms

... and then timeouts beyond that.

So, I see that the work packets have been routed through *.attens.net
where the home packets seem to be dropped there.  However, they both
make it to the same *.att.net routers.

So, what's attens.net?  Well, it seems to be part of AT&T's network. 
Why would my home packets get dropped there?

At least the problem doesn't seem to be my own ISP killing the packets.

Anthony.