MS loopback messing up

[Gisle Vanem <giva () bgnett no>]

After installing the Microsoft loopback adapter, nmap has been confused.
The output of "nmap --iflist" is now:

***WinIP***  trying to initialize winpcap 3.1
Winpcap present, dynamic linked to: WinPcap version 3.1 (packet.dll version 3, 1, 0, 27), based on 
WinPcap 3.1 (current-cvs.tcpdump.org.2006.01.18)

Starting Nmap 4.02Alpha1 ( http://www.insecure.org/nmap ) at 2006-03-15 20:05 GMT
************************INTERFACES************************
DEV  (SHORT) IP/MASK      TYPE     UP MAC
eth0 (eth0)  10.0.0.10/24 ethernet up 02:00:4C:4F:4F:50
eth1 (eth1)  10.0.0.6/24  ethernet up 00:01:80:0C:70:B2
lo0  (lo0)   127.0.0.1/8  loopback up

So far so good; I just made an alias like "nmap = g:\MingW\src\inet\nmap\nmap -e eth1", 
but then I'm getting this fatal error:

Starting Nmap 4.02Alpha1 ( http://www.insecure.org/nmap ) at 2006-03-15 20:05 GMT
The max # of sockets we are using is: 0
NmapArpCache() can only take IPv4 addresses.  SorryQUITTING!

A closer inspection shows "sin->sin_family" to be 0 in tcpip.cc and
NmapArpCache(). Any idea why? 

BTW. all this is with WinPcap 3.1 release (3, 1, 0, 27). 

--gv


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