Re: [Exp PATCH] Consolidation bug in traceroute

["Eddie Bell" <ejlbell () gmail com>]

Yes, go for it

thanks
 - eddie

On 16/04/07, Kris Katterjohn <katterjohn () gmail com> wrote:
> Eddie Bell wrote:
> > > Or have you had output, before the patch, with a
> > > fully-consolidated trace without this problem?
> >
> > No I have never seen this but I think your patch fixes it.
> >
> > Although it is strange I still cannot reproduce it. I found a couple
> > of hosts to test it on but I get this.
> >
> > 1   66.56  192.168.1.254
> > 2   29.55  217.47.67.147
> > 3   29.33  217.47.67.13
> > 4   30.43  212.140.206.1
> > 5   31.97  217.41.173.146
> > 6   29.58  217.41.173.58
> >
> > ....
> >
> > 1   --> 5
> > 6   32.45 217.41.173.58
> >
> > I've seen this many times but perhaps the bug you found occurs under
> > different conditions? This is the problem with testing traceroute,
> > nobody has the same path of initial hosts :)
> >
> > - eddie
>
> I get that same output a lot, with or without the patch, where the
> consolidation goes to the destination's hop distance - 1, then outputs
> the last hop on a separate line.  I, for one, don't know what to do
> about it :)
>
> So, in your opinion, should this patch be applied to /nmap ?
>
> Thanks,
> Kris Katterjohn

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org