mailing list archives
Re: Nmap's traceroute Vs intrace
From: Henri Doreau <henri.doreau () gmail com>
Date: Fri, 11 Mar 2011 15:14:31 +0100
2011/3/11 Houcem HACHICHA <houcem.hachicha () gmail com>:
Hello *Nmap* world!
*Intrace <http://code.google.com/p/intrace/>* is a tracerouting utility
(similar to *0trace*) that makes use of existing TCP connections to insert
some TTL modified packets. So, when using intrace on tcp 80 for instance;
you'll have to *telnet target 80* or browse to it so that *intrace* performs
the tracerouting. Pretty useful to bypass some firewalls and filtering
Is this functionality available in *Nmap*'s traceroute?
Nmap traceroute is multi-protocol and will try to select the best
protocol/port combination (ie; one for which he previously got replies
from the target). If the port scanning phase reveals an open 80/tcp
port on the target, then the built-in traceroute can use it.
Nevertheless it doesn't work by injecting the probes into an
established TCP connection.
Hope this answers your question.
Sent through the nmap-dev mailing list
Archived at http://seclists.org/nmap-dev/