Re: '--packet_trace' option under Windows

[Fyodor <fyodor () insecure org>]

On Tue, Apr 01, 2003 at 12:51:08PM +0200, Roberto Travagliante wrote:
> I'm sending to you the patch (modified files) as .ZIP hoping it can be
> interesting. Into these files there are notes about added code. The nmap
> version is 3.20 (I downloaded it two days ago).

Thanks!  Nmap 3.25 (and 3.26) now include this functionality.  I ended up
doing it in a slightly different way though.

> I'm also sending to you code for a new option '--ttl_trace <ttl>' that
> increments automatically TTL for every packet sent (for TTL-tracerouting),
> and I added a simple message (showed if this option is used) about

I agree that this functionality can be very useful.  But I'm not sure
whether it belongs in Nmap or lower-level tools like hping2.   Here is
an example:

# hping2 -t 1 --traceroute -p 80 -S www.microsoft.com
eth0 default routing interface selected (according to /proc)
HPING www.microsoft.com (eth0 207.46.249.27): S set, 40 headers + 0 data bytes
1->TTL 0 during transit from 64.71.128.193  (gige-g0-0-19.gsr12008.fmt.he.net)
2->TTL 0 during transit from 216.218.130.1  (gsr12012.sjc.he.net)
3->TTL 0 during transit from 198.32.176.77  (paix.hotmail.net)
4->TTL 0 during transit from 207.46.34.65  (unknown host name)
5->TTL 0 during transit from 207.46.33.29  (pos15-0.core1.sea1.us.msn.net)
6->TTL 0 during transit from 207.46.36.210  (unknown host name)
7->TTL 0 during transit from 207.46.155.10  (unknown host name)
8->TTL 0 during transit from 207.46.224.146  (unknown host name)
46 bytes from 207.46.249.27: flags=SA seq=8 ttl=56 id=33585 win=16384 rtt=22.4 ms

Cheers,
-F

---------------------------------------------------------------------
For help using this (nmap-dev) mailing list, send a blank email to 
nmap-dev-help () insecure org . List run by ezmlm-idx (www.ezmlm.org).