Hello,
i also checked if now interface status (up/down) and scaning on specified
interface work correct. Interface status get correct reported for me. If i
only had 1 adapter enable, i didnt get NmapArpCache error. If i had 2
enabled and 1 unplugged, as described by Sina and khana, i also get the
NmapArpCache error again. So i did some further testing.
************************INTERFACES************************
DEV (SHORT) IP/MASK TYPE UP MAC
eth0 (eth0) (null)/0 ethernet down 00:0B:5D:24:7A:F7
eth1 (eth1) 192.168.120.254/24 ethernet up 00:07:77:64:09:32
lo0 (lo0) 127.0.0.1/8 loopback up
**************************ROUTES**************************
DST/MASK DEV GATEWAY
255.255.255.255/32 eth1 192.168.120.254
192.168.120.254/32 lo0 127.0.0.1
192.168.120.255/32 eth1 192.168.120.254
255.255.255.255/32 eth1 192.168.120.254
192.168.120.0/0 eth1 192.168.120.254
127.0.0.0/0 lo0 127.0.0.1
224.0.0.0/0 eth1 192.168.120.254
nmap-3.96BETA1-win32>nmap.exe -e eth1 -sP -n 192.168.120.0/24
work as expected
nmap-3.96BETA1-win32>nmap.exe -e eth1 -sP -n 192.168.121.0/24
give , as described above : NmapArpCache() can only take IPv4 addresses.
Sorry
QUITTING!
nmap-3.96BETA1-win32>route print
===========================================================================
Schnittstellenliste
0x1 ........................... MS TCP Loopback interface
0x40004 ...00 07 77 64 09 32 ...... AVM FRITZ!web PPP over ISDN
0x50002 ...00 0b 5d 24 7a f7 ...... Realtek RTL8139-Familie-PCI-Fast
Ethernet-NIC - SecuRemote Minip
ort
===========================================================================
===========================================================================
Aktive Routen:
Netzwerkziel Netzwerkmaske Gateway Schnittstelle Anzahl
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.120.0 255.255.255.0 192.168.120.254 192.168.120.254 1
192.168.120.254 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.120.255 255.255.255.255 192.168.120.254 192.168.120.254 1
224.0.0.0 240.0.0.0 192.168.120.254 192.168.120.254 1
255.255.255.255 255.255.255.255 192.168.120.254 192.168.120.254 1
255.255.255.255 255.255.255.255 192.168.120.254 50002 1
===========================================================================
Ständige Routen:
Keine
Problem is there is no default route, so arp scan for 192.168.121.0/24 didnt
work. Unlucky it gives the
"NmapArpCache() can only take IPv4 addresses" error.
I added a defaultroute, like
Netzwerkziel Netzwerkmaske Gateway Schnittstelle Anzahl
0.0.0.0 0.0.0.0 192.168.120.254 192.168.120.254 1
nmap-3.96BETA1-win32>nmap.exe -e eth1 -sP -n 192.168.121.0/24
Starting Nmap 3.96BETA1 ( http://www.insecure.org/nmap ) at 2006-01-02 11:14
Westeuropõische Normalz
eit
nexthost: Failed to determine dst MAC address for target 192.168.121.255
QUITTING!
and get a more accurate errormsg. So could u both Sina Bahram and khanta
check if u set a default route on the plugged device ? My second device
(eth1) isn't a real eth adapter, its a "AVM FRITZ!web PPP over ISDN" so im
not 100% sure if this workarround did it for u.
Regards Baumgart
-----Ursprüngliche Nachricht-----
Von: nmap-dev-bounces_at_insecure.org [mailto:nmap-dev-bounces_at_insecure.org] Im
Auftrag von Sina Bahram
Gesendet: Freitag, 30. Dezember 2005 19:34
An: nmap-dev_at_insecure.org
Betreff: RE: Informal Nmap 3.96BETA1 release
I have also noticed this same behavior.
In fact, I was just about to report it :).
Take care,
Sina
-----Original Message-----
From: nmap-dev-bounces_at_insecure.org [mailto:nmap-dev-bounces_at_insecure.org]
On Behalf Of khanta
Sent: Friday, December 30, 2005 12:57 PM
To: nmap-dev_at_insecure.org
Subject: Re: Informal Nmap 3.96BETA1 release
The new 3.96BETA1 still gives the ""NmapArpCache() can only take IPv4
addresses." error is there is another adapter on the Windows Box that is
enabled but unplugged, disabling the adapter causes nmap to work correctly.
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Received on Jan 02 2006
Intro
