Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!wuarchive!uunet!shelby!agate!garnet.berkeley.edu!cliff
From: cliff@garnet.berkeley.edu (Cliff Frost)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Third party traceroute (source-route traceroute)
Message-ID: <1991Feb20.182538.6043@agate.berkeley.edu>
Date: 20 Feb 91 18:25:38 GMT
References: <9102200056.AA00350@seka.scc.com> <EMV.91Feb20005703@poe.aa.ox.com>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Reply-To: cliff@garnet.berkeley.edu (Cliff Frost)
Organization: ucb
Lines: 28

In article <EMV.91Feb20005703@poe.aa.ox.com>, emv@ox.com (Ed Vielmetti) writes:
|> 
|> As far as I know, the traceroute package on zerkalo and the 4.3
|> bsd-reno traceroute on (e.g.) wuarchive.wustl.edu are the latest of
|> the publically available traceroute implementations for BSD Unix.
|> 
|> There is no way to know what all else other people might have hacked
|> into the code, in their own effort to make it complete.  If someone has
|> done this they haven't spoken up.
|> 

OK, I'll speak up.  The Zerkalo package is wonderful.  It is also available
on ftp.cc.berkeley.edu, along with my two trivial hacks:

1)  The -n option now works.

2)  It attempts to detect assymetric routes (the Open Jaw routing problem).

    It does this by examining the TTL in the ICMP Time Exceeded messages
    returned by each hop.  It turns out that this method is flawed because
    there are at least 6 commonly used initial values for TTL in ICMP
    messages (29, 30, 59, 60, 255, and TTL_in_packet_received).  

So far I have found this second feature useful exactly once.  Other times
it has been interesting, but nothing more.

	Cliff Frost
	UC Berkeley