RE: Nmap bug - nmap -sT and --packet-trace error

["Rob Nicholls" <robert () robnicholls co uk>]

I suspect the confusion comes from seeing things like "TCP
192.168.1.16:53357" when performing a SYN scan, rather than "TCP localhost".
I'm assuming there's no (elegant) way of identifying the source IP address
that Windows will use during a Connect scan? I highly doubt that there's a
way of identifying the source port for each request. I can live with just
seeing "localhost" though.

Rob

-----Original Message-----
From: nmap-dev-bounces () insecure org [mailto:nmap-dev-bounces () insecure org]
On Behalf Of David Fifield
Sent: 13 January 2010 19:29
To: Ninel Piroi
Cc: nmap-dev () insecure org
Subject: Re: Nmap bug - nmap -sT and --packet-trace error
<snip>
The output is kind of confusing but there is no bug here. The packets
are supposed to come from localhost--where else could they come from?
<snip>


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