Nmap Development mailing list archives
RE: Cisco VPN and nmap...
From: "Craig Humphrey" <Craig.Humphrey () chapmantripp com>
Date: Wed, 7 Feb 2007 09:12:36 +1300
Hi Saro, I suspect this is actually a limitation of WinPcap and relates to non-ethernet interfaces. I have similar problems with standard PPP (Microsoft) VPNs and cellular based internet connections. If you do an "nmap -iflist" you'll see your NICs, loopbacks and the VPN and I think if it doesn't say "ethernet" in the TYPE column, WinPcap wont reliably work with it. Hope that helps. Later'ish Craig
-----Original Message----- From: nmap-dev-bounces () insecure org [mailto:nmap-dev-bounces () insecure org] On Behalf Of Saro Hayan Sent: Monday, February 05, 2007 5:41 PM To: nmap-dev () insecure org Subject: Cisco VPN and nmap... Hello, I seem to have this problem with nmap with any version of Cisco VPN client that I have tried with (ranging from 4.6.x to the 4.8x version (I believe). It works fine when I am not VPN'ed, but when VPN'ed and I try to scan addresses on the other end of the tunnel, I get the following. Below is a sample. C:\>nmap -sP 10.4.4.4 Starting Nmap 4.20 ( http://insecure.org ) at 2007-02-04 20:40 US Mountain Standard Time nexthost: Failed to determine dst MAC address for target 10.4.4.4 QUITTING! Is this setup just not supported? I've also tried winpcap from 3.1 to 4. It's on a WinXP SP2 box. Thanks in advance.
_______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Cisco VPN and nmap... Saro Hayan (Feb 04)
- <Possible follow-ups>
- RE: Cisco VPN and nmap... Craig Humphrey (Feb 06)