From a140d208b5ecc0e726bc4300cd21ab1f869df7c7 Mon Sep 17 00:00:00 2001 From: fenner Date: Mon, 30 Sep 1996 19:09:55 +0000 Subject: Virgin import of LBL traceroute version 1.3.2. Obtained from: ftp://ftp.ee.lbl.gov/traceroute.tar.Z on 30-Sep-1996. --- contrib/traceroute/README | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 contrib/traceroute/README (limited to 'contrib/traceroute/README') diff --git a/contrib/traceroute/README b/contrib/traceroute/README new file mode 100644 index 0000000..fa789ed --- /dev/null +++ b/contrib/traceroute/README @@ -0,0 +1,29 @@ +@(#) $Header: README,v 1.7 96/07/06 02:08:32 leres Exp $ (LBL) + +TRACEROUTE 1.3 +Lawrence Berkeley National Laboratory +Network Research Group +traceroute@ee.lbl.gov +ftp://ftp.ee.lbl.gov/traceroute.tar.Z + +Traceroute is a system administrators utility to trace the route +ip packets from the current system take in getting to some +destination system. See the comments at the front of the +program for a description of its use. + +This program uses raw ip sockets and must be run as root (or installed +setuid to root). + +A couple of awk programs to massage the traceroute output are +included. "mean.awk" and "median.awk" compute the mean and median time +to each hop, respectively. I've found that something like + + traceroute -q 7 foo.somewhere >t + awk -f median.awk t | graph + +can give you a quick picture of the bad spots on a long path (median is +usually a better noise filter than mean). + +Problems, bugs, questions, desirable enhancements, source code +contributions, etc., should be sent to the email address +"traceroute@ee.lbl.gov". -- cgit v1.1