Date: Sun, 09 Sep 2001 11:24:24 -0400 From: "Kenneth Mays" <kmays2000@hotmail.com> To: stable@freebsd.org Subject: 4.4RC4 + traceroute v1.3.2 (bug) Message-ID: <LAW2-F149HU3NAPMfev000181bb@hotmail.com>
next in thread | raw e-mail | index | archive | help
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). Ken Mays 4.4RC4 _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?LAW2-F149HU3NAPMfev000181bb>