Fwd: nmap-4.22SOC5 traceroute problem

["Luís A. Bastião Silva" <luis.kop () gmail com>]

---------- Forwarded message ----------
From: Luís A. Bastião Silva <luis.kop () gmail com>
Date: 23/08/2007 11:33
Subject: Re: nmap-4.22SOC5 traceroute problem
To: umit-gsoc () lists sourceforge net



2007/8/23, Eddie Bell <ejlbell () gmail com>:
> On 23/08/07, Fyodor <fyodor () insecure org> wrote:
> > Thanks for the update, Eddie.  If we don't have any
> > information on a hop, maybe we should omit it from the XML.
>
> I've changed it but it will make determining time outs a little
> trickier. Umitmapper and nmap.xsl will have to take into account
> breaks in the sequence of ttls instead of just checking if a hop has
> an 'ipaddr' attribute
>
> > On 8/22/07, Luís A. Bastião Silva <luis.kop () gmail com> wrote:
> ....
> > <hop rtt="" ipaddr="" ttl="13"/>
> > <hop rtt="" ipaddr="" ttl="14"/>
>
> This definitely should not happen! Luís you say this occurs on
> windows? I tried it on linux and it works fine, I'll give it a test on
> windows when I get the chance
>
> cheers
> - eddie
yap, it's happen in Windows.
I think that it's not necessary omit from XML file.
But add attributes like this:
<hop rtt="" ipaddr="" ttl="14"/>
I think that's enough to solve this situation. But really line as this does
not show any useful information, but I don't have sure about that.

Eddie try with the release that I refer at my first email.


cheers
-- 
Luis A. Bastiao Silva

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