Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!caen!ox.com!ox.com!emv From: emv@ox.com (Ed Vielmetti) Newsgroups: comp.protocols.tcp-ip Subject: Re: Third party traceroute (source-route traceroute) Message-ID: Date: 20 Feb 91 05:57:03 GMT References: <9102200056.AA00350@seka.scc.com> Sender: usenet@ox.com (Usenet News Administrator) Organization: OTA Limited Partnership, Ann Arbor MI. Lines: 27 In-Reply-To: enger@SEKA.SCC.COM's message of 20 Feb 91 00:56:05 GMT In article <9102200056.AA00350@seka.scc.com> enger@SEKA.SCC.COM (Robert M. Enger) writes: The version of traceroute on Zerkalo.harvard.edu is a composite of the various available sources and enhancements (including source-route ability). IF THE VERSION OF TRACEROUTE ON ZERKALO IS NOT THE MOST COMPLETE, I WOULD APPRECIATE IT IF SOMEONE WOULD SET US STRAIGHT. THANKS!! 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. By the way, how's the "noctool2" group's efforts coming along? Send me some mail (if you can read my mangled address), I have some contributions to make. --Ed Edward Vielmetti emv@ox.com (note: the gateway may be mangling my address. please advise if you get this by mail and the From: line is weird.)