Re: nmap-4.22SOC5 traceroute problem

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

Yeah sorry I quoted the wrong person :) This is strange as rtt is just
a number so should never appear as a empty string. I would expect, if
something went wrong, it would appear as a negative value.

If I trace the same IP address my results are correct, but I am in a
different location so it is hard to compare.

<hop ttl="13" rtt="38.56" ipaddr="195.99.125.102"/>
<hop ttl="14" rtt="163.86" ipaddr="64.125.31.186"/>

The other strange thing about your results is the attribute ordering.
It should be ttl/rtt/ipaddr but yours are rtt/ipaddr/ttl

Anyway I'll play around with it and try to reproduce your bug

- eddie

p.s. UmitMapper looks great


On 23/08/07, João Medeiros <ignotus21 () gmail com> wrote:
> Hi friends,
>
> This is from my message:
> > ....
> > > <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
>
> This happen in linux with nmap-4.22SOC5.
>
> Att, ignotus.
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://SecLists.Org

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