Nmap Development mailing list archives
Re: nmap and routing problems
From: David Fifield <david () bamsoftware com>
Date: Mon, 20 Apr 2009 12:15:50 -0600
On Thu, Feb 19, 2009 at 12:13:17PM -0700, David Fifield wrote:
On Thu, Feb 19, 2009 at 08:38:42PM +0200, Peter Gordon wrote:Progress has been made ! I ran the latest version of nmap -4.85BETA3: ./nmap -e eth0 --unprivileged 10.10.10.71 and received the message "Host seems down". The problem is with the socket connection. The -e flag doesn't seem to be doing anything. What it should be doing is a bind to the IP of the requested port. Without -e option connect(3, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("10.10.10.71")}, 16) = -1 ENETUNREACH (Network is unreachable) With -e option connect(3, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("10.10.10.71")}, 16) = -1 ENETUNREACH (Network is unreachable)
I don't think the -e option is supposed to bind to a source address. Try using -S 10.19.1.30 instead. That should work even as a non-root user. David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Re: nmap and routing problems David Fifield (Apr 20)