Please help with long standing nmap issue

[Jerry Pape <jpape () espt com>]

Hello list,


Issue involves both the --iflist and the subsequent reporting of 
"Warning: Unable to open" also -O -v scan fails to recognize the devices 
revealed by the -sP scan. Perhaps I am just doing something wrong, but I 
have previously reported this and related issues.

I like to use nmap to inventory remote networks that I connect to via 
VPN Tracker VPN software v 5.4.1

Please advise...

JP

BTW did we ever meet in of the popular spots in Paly--I lived out there 
a long time also Mtn View and Sunnyvale (we used to lease The Edge back 
in the late 80's).

-------------------------------------------------------

M:~ jp$ nmap -iflist

Starting Nmap 4.85BETA4 ( http://nmap.org ) at 2009-03-29 16:31 MDT
Warning: Unable to open interface en1 -- skipping it.
Warning: Unable to open interface vmnet8 -- skipping it.
Warning: Unable to open interface vmnet1 -- skipping it.
Warning: Unable to open interface en5 -- skipping it.
Warning: Unable to open interface en6 -- skipping it.
************************INTERFACES************************
DEV  (SHORT) IP/MASK            TYPE        UP MAC
lo0  (lo0)   127.0.0.1/8        loopback    up
gif0 (gif0)  192.168.253.229/32 point2point up

WARNING: Unable to find appropriate interface for system route to 
192.168.253.1
WARNING: Unable to find appropriate interface for system route to 
192.168.253.1
WARNING: Unable to find appropriate interface for system route to 
192.168.253.1
**************************ROUTES**************************
DST/MASK           DEV  GATEWAY
10.37.129.2/32     lo0  127.0.0.1
10.211.55.2/32     lo0  127.0.0.1
127.0.0.1/32       lo0  127.0.0.1
192.168.226.0/32   gif0 192.168.253.229
192.168.253.229/32 lo0  127.0.0.1
127.0.0.0/0        lo0  127.0.0.1

M:~ jp$ sudo nmap --iflist

Starting Nmap 4.85BETA4 ( http://nmap.org ) at 2009-03-29 16:33 MDT
Warning: Unable to open interface vmnet8 -- skipping it.
Warning: Unable to open interface vmnet1 -- skipping it.
************************INTERFACES************************
DEV  (SHORT) IP/MASK            TYPE        UP MAC
lo0  (lo0)   127.0.0.1/8        loopback    up
gif0 (gif0)  192.168.253.229/32 point2point up
en1  (en1)   192.168.253.229/24 ethernet    up 00:1E:C2:C3:08:C2
en5  (en5)   10.211.55.2/24     ethernet    up 00:1C:42:00:00:08
en6  (en6)   10.37.129.2/24     ethernet    up 00:1C:42:00:00:09

**************************ROUTES**************************
DST/MASK           DEV  GATEWAY
224.0.0.251/32     en1  192.168.253.1
10.37.129.2/32     lo0  127.0.0.1
10.211.55.2/32     lo0  127.0.0.1
17.151.16.20/32    en1  192.168.253.1
64.13.134.49/32    en1  192.168.253.1
64.13.134.50/32    en1  192.168.253.1
69.93.193.204/32   en1  192.168.253.1
74.125.127.99/32   en1  192.168.253.1
74.125.127.102/32  en1  192.168.253.1
74.125.127.166/32  en1  192.168.253.1
74.125.155.155/32  en1  192.168.253.1
204.132.96.226/32  en1  192.168.253.1
224.0.0.1/32       en1  192.168.253.1
127.0.0.1/32       lo0  127.0.0.1
192.168.226.0/32   gif0 192.168.253.229
192.168.253.229/32 lo0  127.0.0.1
127.0.0.0/0        lo0  127.0.0.1
0.0.0.0/0          en1  192.168.253.1

M:~ jp$ sudo nmap -O -v 192.168.226.1-254

Starting Nmap 4.85BETA4 ( http://nmap.org ) at 2009-03-29 16:33 MDT
Warning: Unable to open interface vmnet8 -- skipping it.
Warning: Unable to open interface vmnet1 -- skipping it.
Initiating Ping Scan at 16:33
Scanning 254 hosts [2 ports/host]
Ping Scan Timing: About 31.50% done; ETC: 16:35 (0:01:07 remaining)
Ping Scan Timing: About 60.04% done; ETC: 16:35 (0:00:41 remaining)
Completed Ping Scan at 16:35, 103.72s elapsed (254 total hosts)
Read data files from: /usr/local/share/nmap
Nmap done: 254 IP addresses (0 hosts up) scanned in 104.06 seconds
         Raw packets sent: 1016 (34.544KB) | Rcvd: 885 (72.047KB)

M:~ jp$ nmap -sP 192.168.226.1-254

Starting Nmap 4.85BETA4 ( http://nmap.org ) at 2009-03-29 16:38 MDT
Host 192.168.226.1 appears to be up.
Host 192.168.226.2 appears to be up.
Host 192.168.226.10 appears to be up.
Host 192.168.226.12 appears to be up.
Host 192.168.226.14 appears to be up.
Host 192.168.226.15 appears to be up.
Host 192.168.226.16 appears to be up.
Host 192.168.226.17 appears to be up.
Host 192.168.226.18 appears to be up.
Host 192.168.226.19 appears to be up.
Host 192.168.226.41 appears to be up.
Host 192.168.226.42 appears to be up.
Host 192.168.226.43 appears to be up.
Host 192.168.226.44 appears to be up.
Host 192.168.226.46 appears to be up.
Host 192.168.226.47 appears to be up.
Host 192.168.226.48 appears to be up.
Host 192.168.226.49 appears to be up.
Host 192.168.226.210 appears to be up.
Host 192.168.226.211 appears to be up.
Host 192.168.226.230 appears to be up.
Host 192.168.226.232 appears to be up.
Host 192.168.226.233 appears to be up.
Host 192.168.226.235 appears to be up.
Host 192.168.226.236 appears to be up.
Host 192.168.226.238 appears to be up.
Host 192.168.226.239 appears to be up.
Host 192.168.226.240 appears to be up.
Host 192.168.226.241 appears to be up.
Host 192.168.226.243 appears to be up.
Host 192.168.226.245 appears to be up.
Nmap done: 254 IP addresses (31 hosts up) scanned in 2.55 seconds
M:~ jp$




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