Re: nmap-4.22SOC5 traceroute problem

[João Paulo de Souza Medeiros <ignotus21 () gmail com>]

Hi friends,

    The problem is about a possible differences in XML output in Windows 
a Unix*. In some traces appear the hops with ipaddr="" and in some 
others this attr don't exists, like this:

<trace port="21" proto="tcp">
<hop rtt="--" ipaddr="192.168.254.254" ttl="1"/>
<hop rtt="20.45" ipaddr="200.217.89.32" ttl="2"/>
(...)
<hop rtt="236.06" ipaddr="213.140.52.242" ttl="12"/>
<hop rtt="" ipaddr="" ttl="13"/>
<hop rtt="" ipaddr="" ttl="14"/>
<hop rtt="256.70" ipaddr="149.20.65.114" ttl="15"/>
<hop rtt="247.74" ipaddr="149.20.65.114" ttl="16"/>
<hop rtt="244.69" ipaddr="204.152.191.5" ttl="17"/>
</trace>

    But, this "problem" was fixed in UmitMapper parsing. Other questions 
is: the hops 15 and 16 are the same, this is a routing thing or a problem?

    With Luís' help the UmitMapper can be run on Windows too. Thanks.

Att, ignotus

Luís A. Bastião Silva wrote:
> you are right.
> Now I analyze the xml file of nmap at the Linux and it's the same.
> So after I talk with Joao we conclude that should be a failure at the
> umitMapper. Joao is trying fix it. And if all occurs like we think
> umitMapper should be run in Windows soon.
>
> Thanks all and sorry for something.
>
> Cheers
>
> 2007/8/22, Eddie Bell <ejlbell () gmail com>:
> > Kris is correct. If the hop shouldn't have timed out try a slower timing
> > profile
> >
> > On 22/08/07, Kris Katterjohn <katterjohn () gmail com> wrote:
> > > On 8/22/07, Luís A. Bastião Silva <luis.kop () gmail com> wrote:
> > > > Hi,
> > > >
> > > > I have installed this release: nmap-4.22SOC5-setup.exe.
> > > >
> > > > And I was testing umitMapper with Joao. And we found a trouble.
> > > > It's with nmap -traceroute.I do a simply trace route  with nmap -v
> > > > -traceroute google.com.
> > > >
> > > > In the temporary xml in the tagname hop with attribute ttl="2" don't
> > have
> > > > rtt and ipddr.
> > > > Below the extract of temporary xml:
> > > >
> > > > <trace port="80" proto="tcp">
> > > > <hop ttl="1" rtt="0.00" ipaddr="192.168.1.1"/>
> > > > <hop ttl="2"/>
> > > > <hop ttl="3" rtt="15.00" ipaddr="194.65.174.93" host="
> > > > dial-b1-174-93.telepac.pt"/>
> > > > <hop ttl="4" rtt="16.00" ipaddr="195.8.10.137" host="
> > > > lis2-br1-gi-13-0.cprm.net"/>
> > > > <hop ttl="5" rtt="32.00" ipaddr="195.8.0.69"/>
> > > > <hop ttl="6" rtt="47.00" ipaddr="195.8.0.70"/>
> > > > <hop ttl="7" rtt="47.00" ipaddr="195.66.224.125"/>
> > > > <hop ttl="8" rtt="62.00" ipaddr="209.85.252.42"/>
> > > > <hop ttl="9" rtt="125.00" ipaddr="64.233.175.213"/>
> > > > <hop ttl="10" rtt="141.00" ipaddr="72.14.233.115"/>
> > > > <hop ttl="11" rtt="156.00" ipaddr="66.249.94.96"/>
> > > > <hop ttl="12" rtt="140.00" ipaddr="66.249.94.118"/>
> > > > <hop ttl="13" rtt="140.00" ipaddr="72.14.207.99" host="
> > > > eh-in-f99.google.com
> > > > "/>
> > > > </trace>
> > > >
> > > > If you need some info or more details ask for it. I will send a mail
> > soon
> > > > as
> > > > possible.
> > > I think that's what happens when you don't get a response from that
> > hop.  I
> > > haven't looked at that code in a few months, so I'm just going on what I
> > > remember.
> > >
> > > Try a regular traceroute (better with one that offers TCP, UDP and ICMP)
> > and
> > > see what happens.
> > >
> > > Thanks,
> > > Kris Katterjohn
> > >
> > > _______________________________________________
> > > 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