Nmap Development mailing list archives

RE: nmap/vmware osx bug


From: "Sina Bahram" <sbahram () nc rr com>
Date: Sun, 29 Apr 2007 21:56:53 -0400

Ok then

I'm not sure if this is true on osx, but I know for a fact that vmware
installs several network adaptors  on Windows; for example, and so I'm
wondering if this could be part of your problem?

Such an adaptor could possibly act as a pass through/bridge, but have issues
with root permissions?

What happens if you enumerate your adaptors and then use nmap's -e option to
select one manually?

Take care,
Sina

-----Original Message-----
From: nmap-dev-bounces () insecure org [mailto:nmap-dev-bounces () insecure org]
On Behalf Of Garrett Reid
Sent: Sunday, April 29, 2007 9:25 PM
To: nmap-dev () insecure org
Cc: Garrett Reid
Subject: Re: nmap/vmware osx bug

I'm running nmap under OSX (the system that just had VMWare installed on
it).

On Apr 29, 2007, at 7:21 PM, Sina Bahram wrote:

Are you running nmap under vmware?

Or are you speaking of running it on the system that has vmware 
installed on it?

Take care,
Sina

-----Original Message-----
From: nmap-dev-bounces () insecure org [mailto:nmap-dev- 
bounces () insecure org] On Behalf Of Garrett Reid
Sent: Sunday, April 29, 2007 9:19 PM
To: nmap-dev () insecure org
Cc: Garrett Reid
Subject: nmap/vmware osx bug

I'm not sure if this is the right place to report this, so apologies 
in advance if it isn't.

For some reason, after installing VMWare Fusion Beta3 (the current 
beta for mac users), nmap will not run as root:
 garrett$ sudo nmap localhost
Starting Nmap 4.20 ( http://insecure.org ) at 2007-04-29 19:06 MDT
getinterfaces: Failed to open ethernet interface (vmnet8). A possible 
cause on BSD operating systems is running out of BPF devices (see 
http://seclists.org/lists/nmap-dev/2006/Jan-Mar/
0014.html).
QUITTING!

However, if run as a non-root user, it works fine:
garrett$ nmap localhost
Starting Nmap 4.20 ( http://insecure.org ) at 2007-04-29 19:16 MDT 
Interesting ports on localhost (127.0.0.1)

I'm not sure if this is nmap using the wrong interface, or vmware 
breaking raw sockets or just what is going on, so I've posted this bug 
to both parties. However, since this is a mailing-list, I'll hopefully 
be getting some feedback from here =)

-Garrett

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


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


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


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


Current thread: