tcptraceroute, traceroute and IP addresses [was]Re: Level3 funkiness
# traceroute level3.net
When diagnosing things like this try using the IP address and tcptraceroute or some similar tool. NOT plain old traceroute and a DNS name. Especially when writing to a list with participants as technically involved as those on NANOG. scott
I can now get to .com ok, but .net net traces ok but the site doesn't come up in a browser and tr does work. So they have fixed part of the problem, at last from here. C:\Documents and Settings\netman>tracert level3.net Tracing route to level3.net [4.68.95.11] over a maximum of 30 hops: 1 113 ms 126 ms 386 ms argon.socrdu.net [64.132.109.136] 2 * 248 ms 113 ms 64.132.109.130 3 123 ms * 113 ms 64.132.109.129 4 138 ms 126 ms 119 ms 64-132-140-113.static.twtelecom.net [64.132.140.113] 5 137 ms 140 ms 138 ms 66.192.240.22 6 160 ms 128 ms 138 ms te-4-1.car1.washington3.level3.net [4.68.110.89] 7 138 ms 145 ms 146 ms vlan69.csw1.washington1.level3.net [4.68.17.62] 8 132 ms 133 ms 140 ms ae-62-62.ebr2.washington1.level3.net [4.69.134.145] 9 174 ms 159 ms 145 ms ae-2-2.ebr2.chicago2.level3.net [4.69.132.69] 10 188 ms 159 ms 166 ms ae-1-100.ebr1.chicago2.level3.net [4.69.132.113] 11 196 ms 179 ms 200 ms ae-3.ebr2.denver1.level3.net [4.69.132.61] 12 194 ms 182 ms 180 ms ge-9-0.hsa1.denver1.level3.net [4.68.107.35] 13 185 ms 179 ms 199 ms 4.68.94.1 14 176 ms 186 ms 199 ms www.level3.com [4.68.95.11] Trace complete. C:\Documents and Settings\netman>tracert 4.68.95.11 Tracing route to www.level3.com [4.68.95.11] over a maximum of 30 hops: 1 571 ms 119 ms 106 ms argon.socrdu.net [64.132.109.136] 2 125 ms 119 ms 114 ms 64.132.109.130 3 113 ms 119 ms 112 ms 64.132.109.129 4 128 ms 119 ms 118 ms 64-132-140-113.static.twtelecom.net [64.132.140.113] 5 150 ms 132 ms 146 ms 66.192.240.22 6 144 ms 133 ms 139 ms te-4-1.car1.washington3.level3.net [4.68.110.89] 7 127 ms 158 ms 139 ms vlan69.csw1.washington1.level3.net [4.68.17.62] 8 139 ms 137 ms 139 ms ae-62-62.ebr2.washington1.level3.net [4.69.134.145] 9 158 ms 166 ms 167 ms ae-2-2.ebr2.chicago2.level3.net [4.69.132.69] 10 160 ms 165 ms 153 ms ae-1-100.ebr1.chicago2.level3.net [4.69.132.113] 11 189 ms 203 ms 328 ms ae-3.ebr2.denver1.level3.net [4.69.132.61] 12 180 ms 187 ms 191 ms ge-9-0.hsa1.denver1.level3.net [4.68.107.35] 13 201 ms 179 ms 193 ms 4.68.94.1 14 185 ms 179 ms 172 ms www.level3.com [4.68.95.11] Trace complete. C:\Documents and Settings\netman> -----Original Message----- From: Scott Weeks [mailto:surfer@mauigateway.com] Sent: Wednesday, April 15, 2009 7:00 PM To: nanog@nanog.org Subject: tcptraceroute, traceroute and IP addresses [was]Re: Level3 funkiness
# traceroute level3.net
When diagnosing things like this try using the IP address and tcptraceroute or some similar tool. NOT plain old traceroute and a DNS name. Especially when writing to a list with participants as technically involved as those on NANOG. scott
participants (2)
-
Dave Larter
-
Scott Weeks