Nmap Development: RE: Latest NMAP & the cisco VPN client...

From: Wagner, Chris \(GE Infra, Non-GE, US\) <chris.wagner_at_ge.com>
Date: Mon, 12 Feb 2007 14:15:13 -0500

IIRC I was able to get some functionality by forcing nmap to send the traffic through my local ethernet interface and it forwarded the traffic through the VPN. It's been a while since I did that so ur mileage may vary.

-----Original Message-----
From: nmap-dev-bounces_at_insecure.org on behalf of kx
Sent: Fri 2/9/07 8:50 PM
To: Hines,Colin Mack; Craig Humphrey; Saro Hayan
Cc: nmap-dev_at_insecure.org; Padgett,Phil
Subject: Re: Latest NMAP & the cisco VPN client...

Colin,
WinPcap can't transmit over a VPN. See:
http://seclists.org/nmap-dev/2006/q3/0438.html

You might try --unprivileged which should allow things like Connect
scans to work.

Cheers,
kx

On 2/9/07, Hines,Colin Mack <cmhines_at_ufl.edu> wrote:
>
> Running XP sp2 / all latest patches and IE7.
>
> Cisco VPN Client 4.6.02.0011 using ipsec/tcp
> Nmap for windows v4.20 downloaded today from insecure.org
>
> It seems that nmap is not correctly enumerating all the local routes
> provided by the cisco vpn client. Here is my current route print
> output...
>
>

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