Package: traceroute
Version: 1:2.0.17-1
Severity: wishlist
Tags: upstream

Hi Daniel,

The traceroute manpage says, concerning its output format:

        This program attempts to trace the route an IP packet would
        follow to some internet host by launching probe packets with a
        small ttl (time to live) then listening for an ICMP "time
        exceeded" reply from a gateway. We start our probes with a ttl
        of one and increase by one until we get an ICMP "port unreach‐
        able" (or TCP reset), which means we got to the "host", or hit a
        max (which defaults to 30 hops). Three probes (by default) are
        sent at each ttl setting and a line is printed showing the ttl,
        address of the gateway and round trip time of each probe. [...]

By contrast, FreeBSD's traceroute manpage says:

        Tracking the route one's packets follow (or finding the
        miscreant gateway that's discarding your packets) can be
        difficult. Traceroute utilizes the IP protocol ‘time to live’
        field and attempts to elicit an ICMP TIME_EXCEEDED response from
        each gateway along the path to some host.

        [...]

        A sample use and output might be:

        [yak 71]% traceroute nis.nsf.net.
        traceroute to nis.nsf.net (35.1.1.48), 64 hops max, 38 byte packet
        1  helios.ee.lbl.gov (128.3.112.1)  19 ms  19 ms  0 ms
        2  lilac-dmc.Berkeley.EDU (128.32.216.1)  39 ms 39 ms  19 ms
        3  lilac-dmc.Berkeley.EDU (128.32.216.1)  39 ms 39 ms  19 ms
        [...]
        11  nic.merit.edu (35.1.1.48)  239 ms  239 ms  239 ms

        Note that lines 2 & 3 are the same. This is due to a buggy
        kernel on the 2nd hop system - lilac-dmc.Berkeley.EDU - that
        forwards packets with a zero ttl (a bug in the distributed
        version of 4.3BSD).  Note that you have to guess what path the packets
        are taking cross-country since the NSFNet (129.140) doesn't supply
        address-to-name translations for its NSSes.

Notice:

 - explanation of purpose
 - clear summary of how it works and how to use it
 - examples
 - related information for the puzzled reader

I would have appreciated all these things. :)

What do you think?
Jonathan



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to