From owner-freebsd-stable Sun Sep 9 12:58:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 13A4437B40C for ; Sun, 9 Sep 2001 12:58:34 -0700 (PDT) Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15gAir-0002zb-00; Mon, 10 Sep 2001 07:58:29 +1200 Date: Mon, 10 Sep 2001 07:58:29 +1200 (NZST) From: Juha Saarinen To: Kenneth Mays Cc: "stable@freebsd.org" Subject: Re: 4.4RC4 + traceroute v1.3.2 (bug) In-Reply-To: Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 9 Sep 2001, Kenneth Mays wrote: > I seem to have a bug with traceroute. I tested traceroute using networks > using VLANs/VPNs. Strange thing happens. The Microsoft tracert seems to work > fine all the time. The generic UNIX traceroute v1.4a12 which I have compiled > on FreeBSD v4.3R and 4.4RC4 works consistent to the Microsoft tracert > program. > > The problem is with traceroute 1.3.2 which seems to die in certain areas of > the network. I will see "*" responses where the other versions of the > program will give me response times. I also test traceroute 1.4a5 (popular > on Solaris systems) on both a Solaris 2.6 and FreeBSD 4.3R box which gave > bad results. Traceroute 1.4a12 and tracert worked fine. > I even tested Neoworx's Neotrace against traceroute 1.3.2 and found the same > issues in which traceroute 1.3.2 failed in certain areas. Tracert and > traceroute 1.4a12 were consistent to Neotrace Express v3.x. > > Programs tested on FreeBSD 4.3R and 4.4RC4 test machines: > 1. traceroute 1.3.2 > 2. traceroute 1.4a5 > 3. traceroute 1.4a12 (wins every time!) > > Programs tested on Win98SE/NTSP6a test machines: > 1. tracert (built-in) > 2. Neoworx's Neotrace Express 3.x > 3. Solarwinds traceroute tool (not mentioned above but used). Could be because Windows tracert uses ICMP packets instead of UDP. Some network administrators filter all UDP... Traceroute in 4.3 appears to be an older variant that doesn't support the -I switch (to toggle ICMP). -- Regards, Juha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message