nmap & AIX

[Pier_Luigi_Rotondo () tivoli com]

I am trying to run nmap on a RS6000/AIX platform and I send you some output
hoping that this could be useful and interesting for future developments of
nmap.


I am currently using nmap 2.53 on a AIX 4.3.3.0 All the configuring,
compiling (with IBM xlC, IBM's C compiler) and installing phases run
without problems, but when I it comes to executing nmap I get this message:

# nmap www.mysite.com

Starting nmap V. 2.53 by fyodor () insecure org ( www.insecure.org/nmap/ )
WARNING!  The following files exist and are readable: /usr/local/share/nmap/nmap
-services and ./nmap-services.  I am choosing /usr/local/share/nmap/nmap-service
s for security reasons.  set NMAPDIR=. to give priority to files in your local d
irectory

pcap_open_live: /dev/en0: No such file or directory

There are several possible reasons for this, depending on your operating system:
LINUX: If you are getting Socket type not supported, try modprobe af_packet or r
ecompile your kernel with SOCK_PACKET enabled.
*BSD:  If you are getting device not configured, you need to recompile your kern
el with Berkeley Packet Filter support.  If you are getting No such file or dire
ctory, try creating the device (eg cd /dev; MAKEDEV <device>; or use mknod).
SOLARIS:  If you are trying to scan localhost and getting '/dev/lo0: No such fil
e or directory', complain to Sun.  I don't think Solaris can support advanced lo
calhost scans.  You can probably use "-P0 -sT localhost" though.

QUITTING!





Actually, en0 is properly defined and up:

# ifconfig -a
lo0: flags=e08084b<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT>
        inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
        inet6 ::1/0
en0: flags=4e080863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,PSEG>
        inet 146.84.187.23 netmask 0xffffff00 broadcast 146.84.187.255

The problem is that AIX does not have a device entry for en0 (therefore no
/dev/en0 !) since all devices are registered in the ODM (Object Data
Manager), and also mkdev defines devices in the ODM rather than /dev
(therefore you can't simply create the entry with mkdev or MAKEDEV).





Is there anything in the plans to fix this issue? Please, let me know if
you need further tests to be performed as well as any information that
could result in something useful.


Thank you very much,
Pier Luigi Rotondo, Rome, Italy


---------------------------------------------------------------------
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).