Nmap Development mailing list archives

Previous By Date Next
Previous By Thread Next

Re: Windows 7

From: Christian Savalas <csavalas () gmail com>
Date: Sun, 13 Feb 2011 02:46:10 -0800
I should have written this in the last e-mail, but I hadn't tried it
out yet. I can't do a normal scan with this revision with or without
having the virtual adapter disabled:

C:\Users\Anonymous\Desktop\nmap-5.51SVN-dnet-pcap1>nmap google.com

Starting Nmap 5.51SVN-dnet-pcap1 ( http://nmap.org ) at 2011-02-13
02:43 Pacific Standard Time
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.63 seconds

C:\Users\Anonymous\Desktop\nmap-5.51SVN-dnet-pcap1>nmap google.com

Starting Nmap 5.51SVN-dnet-pcap1 ( http://nmap.org ) at 2011-02-13
02:44 Pacific Standard Time
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.20 seconds


On Sun, Feb 13, 2011 at 2:43 AM, Christian Savalas <csavalas () gmail com> wrote:

Sure thing David. If you have time in the future, let me know how it's
coming; I'm very curious to see how it gets resolved.

Christian


Virtual Adapter Enabled:
----------------------------------

C:\Users\Anonymous\Desktop\nmap-5.51SVN-dnet-pcap1>nmap --iflist

Starting Nmap 5.51SVN-dnet-pcap1 ( http://nmap.org ) at 2011-02-13
02:39 Pacific Standard Time
************************INTERFACES************************
DEV  (SHORT) IP/MASK         TYPE     UP MTU MAC
eth0 (eth0)  192.168.1.3/24  ethernet up 0   00:26:B9:CF:50:5F
eth1 (eth1)  0.0.0.0/8       ethernet up 0   F0:7B:CB:8F:71:B7
eth2 (eth2)  (null)/0        ethernet up 0   00:50:56:C0:00:08
eth3 (eth3)  192.168.1.40/24 ethernet up 0   F0:7B:CB:8F:71:B7
eth4 (eth4)  (null)/0        ethernet up 0   00:50:56:C0:00:01

DEV  WINDEVICE
eth0 \Device\NPF_{47C778F5-8BAC-4C1C-A7BD-7CB05BBAE58B}
eth1 \Device\NPF_{AEC749F8-57B4-4542-AEF6-30539FC9FC87}
eth2 \Device\NPF_{3992A8D8-5A06-4013-A821-9FA231E4A3C6}
eth3 \Device\NPF_{EED21227-E2CE-4EFF-A995-9C4110FF08D1}
eth4 \Device\NPF_{BEC88542-20C3-4EA2-974F-A6823B0F0C5C}

WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
**************************ROUTES**************************
DST/MASK           DEV  GATEWAY
255.255.255.255/32 eth0 192.168.1.40
192.168.1.255/32   eth0 192.168.1.40
192.168.1.40/32    eth0 192.168.1.40
192.168.1.0/24     eth0 192.168.1.40
224.0.0.0/4        eth0 192.168.1.40
0.0.0.0/0          eth0 192.168.1.1




Virtual Adapter Disabled:
----------------------------------


C:\Users\Anonymous\Desktop\nmap-5.51SVN-dnet-pcap1>nmap --iflist

Starting Nmap 5.51SVN-dnet-pcap1 ( http://nmap.org ) at 2011-02-13
02:39 Pacific Standard Time
************************INTERFACES************************
DEV  (SHORT) IP/MASK         TYPE     UP MTU MAC
eth0 (eth0)  192.168.1.3/24  ethernet up 0   00:26:B9:CF:50:5F
eth1 (eth1)  (null)/0        ethernet up 0   00:50:56:C0:00:08
eth2 (eth2)  192.168.1.40/24 ethernet up 0   F0:7B:CB:8F:71:B7
eth3 (eth3)  (null)/0        ethernet up 0   00:50:56:C0:00:01

DEV  WINDEVICE
eth0 \Device\NPF_{47C778F5-8BAC-4C1C-A7BD-7CB05BBAE58B}
eth1 \Device\NPF_{3992A8D8-5A06-4013-A821-9FA231E4A3C6}
eth2 \Device\NPF_{EED21227-E2CE-4EFF-A995-9C4110FF08D1}
eth3 \Device\NPF_{BEC88542-20C3-4EA2-974F-A6823B0F0C5C}

WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
WARNING: Unable to find appropriate interface for system route to 127.0.0.1
WARNING: Unable to find appropriate interface for system route to 169.254.176.88
WARNING: Unable to find appropriate interface for system route to 169.254.89.175
**************************ROUTES**************************
DST/MASK           DEV  GATEWAY
255.255.255.255/32 eth0 192.168.1.40
192.168.1.255/32   eth0 192.168.1.40
192.168.1.40/32    eth0 192.168.1.40
192.168.1.0/24     eth0 192.168.1.40
224.0.0.0/4        eth0 192.168.1.40
0.0.0.0/0          eth0 192.168.1.1


On Sat, Feb 12, 2011 at 2:50 PM, David Fifield <david () bamsoftware com> wrote:

On Thu, Feb 10, 2011 at 09:34:46PM -0800, David Fifield wrote:

I don't know offhand what to do about this. One potential solution is to
rewrite libdnet's code so that it gets its list of interfaces from
WinPcap instead of through the MIB and GetIfTable. That's a pretty
significant change though, with a lot of potential ramifications. In
your case, we've seen that libdnet finds like 19 Ethernet devices
(mostly tunnels or variations on a few physical devices), while WinPcap
finds only five total. I think it's worth trying, though it might break
things for other people.


Christian, please try --iflist with this test version, with the virtual
adapter enabled and disabled.

http://nmap.org/dist/nmap-5.51SVN-dnet-pcap1-win32.zip

This has libdnet get its interface list directly from pcap_findalldevs,
instead of using GetIfTable, so there's no need to match up the two
different interface lists. This is just a proof of concept and we'd need
to do some more research to see if this can be a fully functional
replacement.

David Fifield





--
Christian Savalas
Marina Pointe Tech Support
13600 Marina Pointe Drive
Marina Del Rey, CA 90292
+1 (310) 343-2000 (cell)





-- 
Christian Savalas
Marina Pointe Tech Support
13600 Marina Pointe Drive
Marina Del Rey, CA 90292
+1 (310) 343-2000 (cell)
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/
Previous By Date Next
Previous By Thread Next

Current thread: