Re: nmap-4.22SOC5 traceroute problem

[Fyodor <fyodor () insecure org>]

On Wed, Aug 22, 2007 at 11:50:43PM +0100, Eddie Bell wrote:
> Kris is correct. If the hop shouldn't have timed out try a slower timing profile

Thanks for the update, Eddie.  If we don't have any information on a
hop, maybe we should omit it from the XML.  Including a record like
<hop ttl="2"/> seems a little confusing and unnecessary.  Could you
take those out?  If you don't have time, I'll do it.

Thanks,
-F

> 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>

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