[nmglug] routing oddity

[Aaron]

I have an odd routing problem.
I cannot see work from home.
I cannot see home from work.
I can see both, both ways from my ISP.

So... I need to do two hops to connect home <--> work,
one to my ISP, then to the destination.

Here's a traceroute from home to work:

traceroute to tau (68.35.161.117), 30 hops max, 52 byte packets
 1  raven (192.168.1.2)  0.230 ms  0.109 ms  0.106 ms
 2  10.0.0.1 (10.0.0.1)  0.944 ms  0.814 ms  0.829 ms
 3  dachou-qwest.swcp.com (216.184.13.1)  42.320 ms  40.832 ms  45.367 ms
 4  tenkuu.swcp.com (198.59.115.1)  41.565 ms  41.437 ms  44.482 ms
 5  53_76_134_204.osogrande.com (204.134.76.53)  66.628 ms  41.760 ms
42.103 ms
 6  66-194-1-121.static.twtelecom.net (66.194.1.121)  42.600 ms  43.861
ms  44.008 ms
 7  dist-02-ge-3-0-0-508.albq.twtelecom.net (66.192.247.136)  44.115 ms
 42.835 ms  43.744 ms
 8  66.192.245.24 (66.192.245.24)  66.089 ms  76.452 ms  66.143 ms
 9  peer-01-so-0-0-0-0.dlfw.twtelecom.net (64.129.248.21)  65.775 ms
66.130 ms  68.413 ms
10  ggr3-p322.dlstx.ip.att.net (192.205.33.205)  65.800 ms  69.872 ms
65.576 ms
11  tbr2032601.dlstx.ip.att.net (12.123.16.206)  68.743 ms  68.553 ms
70.089 ms
12  gar4-p390.dlstx.ip.att.net (12.123.16.101)  67.332 ms  66.390 ms
66.989 ms
13  12.118.225.10 (12.118.225.10)  91.158 ms  92.005 ms  89.280 ms
14  68.35.172.65 (68.35.172.65)  84.028 ms  84.181 ms  84.261 ms
15  s01e1.svalley.nm.albuq.comcast.net (68.86.206.85)  91.150 ms  90.840
ms  89.578 ms
16  68.86.207.153 (68.86.207.153)  84.977 ms  91.251 ms  85.073 ms
17  68.86.207.150 (68.86.207.150)  90.946 ms  92.134 ms  91.184 ms
18  ubr01.broadway.nm.albuq.comcast.net (68.86.206.194)  88.853 ms
88.760 ms  89.008 ms
19  * * *


Comcast will not allow me to traceroute.
They logged into the router at work, and claimed that after some 19
or so hops, the last machine they could see was (216.184.13.51)
which I bet is an interface to dachou at SWCP, my home ISP.

SWCP claims no problems, no blocking, no filtering.
Comcast claims the same.

Any idea why this route could be getting hosed... BOTH WAYS,
yet seemingly at different nodes?

                  aaron