Re: Problem with --traceroute option with 6.00 and 6.25

[Daniel Miller <bonsaiviking () gmail com>]

Bardok,

Can you repeat the problem scan with -oX trace.xml to save XML output? I am
interested in the /nmaprun/host/status element, specifically the reason and
reason_ttl attributes. Other useful info for debugging: Does a normal port
scan work? What is the output of nmap --route-dst www.google.com? nmap
--iflist? What kind of interface are you using (ethernet, vpn, wireless,
etc.)?

Dan


On Thu, Jul 4, 2013 at 2:12 AM, Jorge García - Bardok <bardok () gmail com>wrote:

> Hi,
>
> I've just updated the nmap version I use with my students at school in
> order to have all prepared for next year (sec. school, we teach them what a
> network topology is using zenmap). Since this new version only two hosts
> appear in traceroute.
>
> This is the output with 6.25 (zenmap quick traceroute, both Windows and
> Linux, also tried with 6.00 from the Ubuntu repo and a compiled 6.25):
>
> ------------------------------------------
> Starting Nmap 6.25 ( http://nmap.org ) at 2013-07-04 09:04 Hora de verano
> romance
> Nmap scan report for www.google.com (173.194.40.148)
> Host is up (0.0020s latency).
> Other addresses for www.google.com (not scanned): 173.194.40.146
> 173.194.40.145 173.194.40.147 173.194.40.144
> rDNS record for 173.194.40.148: par10s10-in-f20.1e100.net
>
> TRACEROUTE (using port 80/tcp)
> HOP RTT     ADDRESS
> 1   2.00 ms 192.168.1.3
> 2   1.00 ms par10s10-in-f20.1e100.net (173.194.40.148)
>
> Nmap done: 1 IP address (1 host up) scanned in 0.30 seconds
> ------------------------------------------
>
> This one is the output from a computer with 5.51 installed (using the same
> network connection):
>
> ------------------------------------------
> Starting Nmap 5.51 ( http://nmap.org ) at 2013-07-04 09:02 Hora de verano
> romance
> Nmap scan report for www.google.com (173.194.40.146)
> Host is up (0.038s latency).
> Other addresses for www.google.com (not scanned): 173.194.40.145
> 173.194.40.147 173.194.40.144 173.194.40.148
> rDNS record for 173.194.40.146: par10s10-in-f18.1e100.net
>
> TRACEROUTE (using proto 1/icmp)
> HOP RTT      ADDRESS
> 1   1.00 ms  192.168.1.3
> 2   1.00 ms  10.0.0.1
> 3   9.00 ms  12.212-142-129.static.clientes.euskaltel.es (212.142.129.12)
> 4   11.00 ms 172.19.18.21
> 5   20.00 ms 80.157.128.22
> 6   25.00 ms te0-6-0-0.mpd22.par01.atlas.cogentco.com (154.54.63.94)
> 7   41.00 ms 209.85.240.189
> 8   33.00 ms te0-7-0-31.ccr22.lon01.atlas.cogentco.com (154.54.57.162)
> 9   38.00 ms 209.85.243.47
> 10  39.00 ms 149.14.8.50
> 11  71.00 ms 209.85.255.76
> 12  39.00 ms par10s10-in-f18.1e100.net (173.194.40.146)
>
> Nmap done: 1 IP address (1 host up) scanned in 1.66 seconds
> ------------------------------------------
>
> I've been searching the web, looking for the same problem, but have found
> nothing. Any help would be appreciated.
>
> Best regards:
>
> --
> Jorge García (aka Bardok)
> _______________________________________________
> Sent through the dev mailing list
> http://nmap.org/mailman/listinfo/dev
> Archived at http://seclists.org/nmap-dev/
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/