[TriLUG] OT: Able to reach amazon.com?

[Mike Johnson]

Tanner Lovelace [lovelace at wayfarer.org] wrote:
 
> Unfortunately traceroute has become not quite as useful a tool
> as it used to be when people started filtering ICMP packets.
> If Amazon's machines don't respond to pings, traceroute won't
> work. Their web servers, however, can still be up and available. 

For what it's worth, Linux's default traceroute behavior is to
use UDP packets.  Use the -I switch to get ICMP.  However, I
just found a tool called tcptraceroute.  It uses tcp packets to
get trace information.  You can define which ports it should
use, but it uses port 80 by default.

For comparison:
# /usr/sbin/traceroute www.amazon.com
...
20  177-136.amazon.com (207.171.177.136)  100.948 ms  102.600 ms  99.719 ms
21  * * *

# /usr/sbin/tcptraceroute www.amazon.com
...
20  177-136.amazon.com (207.171.177.136)  100.162 ms  101.320 ms  100.969 ms
21  www.amazon.com (207.171.181.16) [open]  100.288 ms  101.746 ms  103.578 ms


Kinda cool, no?

Check it out at:
http://michael.toren.net/code/tcptraceroute/

Mike
-- 
"Let the power of Ponch compel you!  Let the power of Ponch compel you!"
   -- Zorak on Space Ghost

GNUPG Key fingerprint = ACD2 2F2F C151 FB35 B3AF  C821 89C4 DF9A 5DDD 95D1
GNUPG Key = http://www.enoch.org/mike/mike.pubkey.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 230 bytes
Desc: not available
URL: <http://www.trilug.org/pipermail/trilug/attachments/20020221/32d880f7/attachment.pgp>