Re: Questions: interface names on win32

[David Fifield <david () bamsoftware com>]

On Wed, Nov 28, 2007 at 09:15:26PM +0000, jah wrote:
> I've just bought a new box with XP on it (no way am I going with Vista!) 
> and I notice that the interface device name is not exactly identified 
> with --iflist:
>
> C:\Documents and Settings\jah>ipconfig
>
> Windows IP Configuration
> Ethernet adapter *Local Area Connection*:
>
>         Connection-specific DNS Suffix  . :
>         IP Address. . . . . . . . . . . . : 192.168.1.15
>         Subnet Mask . . . . . . . . . . . : 255.255.255.0
>         Default Gateway . . . . . . . . . : 192.168.1.1
>
> C:\Documents and Settings\jah>nmap --iflist
>
>
> Starting Nmap 4.23RC3 ( http://insecure.org ) at 2007-11-28 20:56 GMT 
> Standard Time
> ************************INTERFACES************************
> DEV  (SHORT) IP/MASK         TYPE     UP MAC
> *eth0* (eth0)  192.168.1.15/24 ethernet up 00:19:21:3D:3F:CE
> lo0  (lo0)   127.0.0.1/8     loopback up
>
> DEV  WINDEVICE
> eth0 \Device\NPF_{3F5D3A0C-7937-48BD-B9FD-B8B36D8884DD}
> lo0  \Device\NPF_GenericDialupAdapter
>
> **************************ROUTES**************************
> DST/MASK           DEV  GATEWAY
> 192.168.1.255/32   eth0 192.168.1.15
> 192.168.1.15/32    lo0  127.0.0.1
> 255.255.255.255/32 eth0 192.168.1.15
> 192.168.1.0/0      eth0 192.168.1.15
> 127.0.0.0/0        lo0  127.0.0.1
> 224.0.0.0/0        eth0 192.168.1.15
> 0.0.0.0/0          eth0 192.168.1.1
>
> is this by design or not?  Having googled, I can't see that anyone's 
> ever mentioned this before and the manpage says only that --iflist 
> "Prints the interface list and system routes as detected by Nmap."

I'm not sure, but I found this comment in libdnet-stripped/src/intf-win32.c:

/* Next we must find the pcap device name corresponding to the device.
   The device description used to be compared with those from
   PacketGetAdapterNames(), but that was unrelaible because dnet and
   pcap sometimes give different descriptions.  For example, dnet gave
   me "AMD PCNET Family PCI Ethernet Adapter - Packet Scheduler
   Miniport" for one of my adapters (in vmware), while pcap described it
   as "VMware Accelerated AMD PCNet Adapter (Microsoft's Packet
   Scheduler)". Plus, Packet* functions aren't really supported for
   external use by the WinPcap folks.  So I have rewritten this to
   compare interface addresses (which has its own problems -- what if
   you want to listen an an interface with no IP address set?) --Fyodor */

> Starting Nmap 4.23RC3 ( http://insecure.org ) at 2007-11-28 21:06 GMT 
> Standard Time
> ************************INTERFACES************************
> DEV  (SHORT) IP/MASK         TYPE     UP MAC
> eth0 (eth0)  192.168.1.13/24 ethernet up 00:13:CE:8A:74:3C
> eth1 (eth1)  192.168.1.14/24 ethernet up 00:16:36:06:7D:16
> lo0  (lo0)   127.0.0.1/8     loopback up
>
> DEV  WINDEVICE
> eth1 \Device\NPF_{9E407963-4C68-4336-9008-3236DF509606}
> lo0  \Device\NPF_{08CFDE0B-16EF-4DBB-B93C-386AB69B65FF}
>
> Also, I observe that the wireless adapter doesn't have an entry under 
> WINDEVICE....why's that?

I don't know what that is. I saw that phenomenon in some of the Vista
users' reports too.

David Fifield

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