Thanks for the tip off, but (sadly) 4.0.2 doesn't appear to make any
difference to the wireless problem that I'm seeing:
>nmap 192.168.1.11 -d3
***WinIP*** trying to initialize winpcap 3.1
Winpcap present, dynamic linked to: WinPcap version 4.0.2 (packet.dll
version 4.
0.0.1040), based on libpcap version 0.9.5
Starting Nmap 4.22SOC8 ( http://insecure.org ) at 2007-11-09 20:07 GMT
Standard
Time
Fetchfile found C:\tools\win32\nmap-services
The max # of sockets we are using is: 0
--------------- Timing report ---------------
hostgroups: min 1, max 100000
rtt-timeouts: init 1000, min 100, max 10000
max-scan-delay: TCP 1000, UDP 1000
parallelism: min 0, max 0
max-retries: 10, host-timeout: 0
---------------------------------------------
doing 0.0.0.0 = 192.168.1.11
Initiating Ping Scan at 20:07
Scanning 192.168.1.11 [2 ports]
pcap_open_live(net0, 100, 0, 2) FAILED. Reported error: Error opening
adapter: T
he system cannot find the device specified. (20). Will wait 5 seconds then
retr
y.
NB: The reference to "winpcap 3.1" must be hardcoded in nmap, as you can see
on the line immediately below it that I'm using 4.0.2.
Rob
-----Original Message-----
From: DePriest, Jason R. [mailto:jrdepriest_at_gmail.com]
Sent: 09 November 2007 19:11
To: Nmap Dev
Subject: Fwd: [Wireshark-dev] [ANNOUNCE] WinPcap 4.0.2 has been released
Folks might want to see if this helps with any of the strange Vista issues.
-Jason
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org
Received on Nov 09 2007
Intro
