[mdlug] fun with traceroute

[Adam Tauno Williams]

On Sun, 2013-02-24 at 09:24 -0500, Carl T. Miller wrote:
> Wow.  This worked for me a few weeks ago, and it's not working now.
> Just another example of why ping and traceroute are no longer
> reliable tools for troubleshooting.  

Yep. These days traceroute fails most of the time, at least for me.

> Anyway, I was able to get the full output from another host.

This probably means that some node along the way is now filtering out
ICMP traffic.

> # traceroute -m 100 216.81.59.173
> traceroute to 216.81.59.173 (216.81.59.173), 100 hops max, 60 byte packets
...
> 32  freedom.to.the.galaxy (206.214.251.89)  69.897 ms  73.291 ms
> 33  0-----I-------I-----0 (206.214.251.94)  73.859 ms  70.715 ms
> 34  0------------------0 (206.214.251.97)  71.368 ms  71.097 ms  70.848
> 35  0-----------------0 (206.214.251.102)  70.883 ms  70.870 ms  70.062
...

Weird!  What kind of &*@&@*(@ @&*(@ routing pattern is that?!

> 47  0-----0 (206.214.251.150)  70.443 ms  71.125 ms  71.105 ms
> 48  0----0 (206.214.251.153)  70.502 ms  74.128 ms  74.150 ms
> 49  0---0 (206.214.251.158)  74.087 ms  71.062 ms  70.614 ms
> 50  0--0 (206.214.251.161)  70.640 ms  71.329 ms  70.838 ms
> 51  0-0 (206.214.251.166)  71.043 ms  71.371 ms  71.403 ms
> 52  00 (206.214.251.169)  70.115 ms  70.346 ms  70.917 ms
> 53  I (206.214.251.174)  73.124 ms  71.089 ms  71.598 ms
> 54  By.Ryan.Werber (206.214.251.177)  72.142 ms  71.428 ms  70.691 ms
> 55  Can.You.Find.The.Secret.Keyhole (206.214.251.182)  70.606 ms
> 56  0_-_0 (206.214.251.185)  71.073 ms  72.222 ms  71.644 ms
> 57  read.more.at.beaglenetworks.net (206.214.251.190)  71.755 ms * *