On Mon, 22 Oct 2001, Jim Sabatke wrote:
I've run a couple of traceroutes to two URLs that I can't connect to. I'm no traceroute expert, but I think the asterisks are bad. Asterisks indicate a timeout (no response) from that router.
First one: my.monster.com
root@yoda:/var/named > traceroute my.monster.com traceroute to my.monster.com (63.112.169.4), 30 hops max, 40 byte packets 1 as17.nwbl1.wi.voyager.net (169.207.80.59) 138 ms 129 ms 130 ms
11 191.ATM11-0-0.GW1.BOS1.ALTER.NET (146.188.176.233) 160 ms 159 ms 170 ms 12 monster-gw.customer.alter.net (157.130.16.34) 150 ms 149 ms 150 ms 13 * * * 14 * * * 15 * * * /etc. / 'trailing' non-response like this means to me that there is a link down, and the site in question is unavaliable at the moment. Notice the name of
/snip/ the last router that DID respond: monster-gw... It appears that the problem is within monster.com's own internal network.
Second bayt.com
root@yoda:/var/named > traceroute bayt.com traceroute to bayt.com (167.216.251.183), 30 hops max, 40 byte packets 1 as17.nwbl1.wi.voyager.net (169.207.80.59) 137 ms 128 ms 120 ms
/snip/
7 fe10-0-0-ny-access2.digisle.net (167.216.160.2) 149 ms 139 ms 140 ms 8 * * * 9 * fe10-0-0-ny-access2.digisle.net (167.216.160.2) 160 ms !A * root@yoda:/var/named >
Hop 8 didn't respond, and hop 9 only responded on the second attempt. The response received was not the normal 'TTL exceeded', but instead, was 'Access to the requested network is prohibited'. Don't thank me, thank `info traceroute` for this explanation... -- Rick Green "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -Benjamin Franklin