>> I'd like to change the default maxttl from 30 to
>> 64 (this matches the kernel default ttl too).  Apart from causing longer
>> reports when packets go in circles, can anyone see a reason not to bump
>> this up ?
>
>Ping has long used a TTL of 255.  Why not do something similar for
>traceroute?  To prevent one from seeing 200+ failure lines traceroute
>could simply stop upping the ttl whenever the past N TTL settings
>failed.  (Eg. if the past 5-10 traceroute TTL's didn't get a reply,
>stop incrementing the TTL and exit.)

the difference between ping and traceroute is that ping starts off by
attempting to "get there", whereas traceroute starts off by assuming
it can't.

there are reasons for not giving up after 5-10 "hops" that don't
respond...see the traceroute source for examples.

otoh, another option to specify the number of drops after which
traceroute gives up might be a neat idea.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."