Hi all,
Some time ago I reported that I had experienced
problems running nmap on my Win XP SP2 laptop that did
not work. I have now installed this new version of
winpcap and I'm pleased to discover that nmap now
works!!
So for all those who may be having problems try
updating winpcap.
Martin
--- Gianluca Varenni <gianluca.varenni_at_gmail.com>
wrote:
> After more than two years of hard work, the final
> version of WinPcap 3.1 is
> available from today in the download section of the
> WinPcap website,
> http://www.winpcap.org/install/.
> This new release represents an important milestone
> for the project: major
> improvements and bug fixes have been carried out
> during this long period of
> time, and the result is the most stable and reliable
> version of WinPcap in
> its history. Thanks to all the users that
> contributed to this result by
> submitting bug reports and thoroughly testing the
> several betas that were
> made available.
>
> Gianluca Varenni
> WinPcap Team
>
>
>
> Changelog from WinPcap 3.1 beta4
> ================================
>
> - New installation script based on the NSIS
> installer. The new installer
> should be able to detect any previous version of
> WinPcap, remove it on
> request and install the new version, decreasing
> the number of situations
> in which a reboot is necessary. Moreover, by
> connecting to the WinPcap
> website, the installer is able to tell the user if
> more recent versions of
> WinPcap are available.
>
> - wpcap.dll has been updated to libpcap 0.9.3 from
> http://www.tcpdump.org.
>
> - General cleanup of the documentation (now aligned
> to libpcap 0.9.3).
>
> - Modified the documentation, so that packet.dll is
> no longer available in
> the standard developer's pack.
>
> - Added to the developer's pack a set of
> libpcap-compatible samples,
> suitable to be compiled against vanilla libpcap
>
> - Exported the following new functions from
> wpcap.dll: pcap_list_datalinks()
> and pcap_dump_ftell().
>
> - Removed pcap_file() from the exports because of
> incompatibilities with the
> Microsoft C runtime (CRT).
>
> - General cleanup of the existing samples.
>
> - Renamed the NdisWanAdapter to
> GenericDialupAdapter, to make the use of
> this adapter more clear for the users.
>
> - Removed some useless files in the source tree and
> in the documentation.
>
> - Bug fixing:
> + Fixed several bugs in the kernel BPF filter
> function when the packet is
> stored into two not contiguous buffers. This bug
> shows up as missing
> packets in the capture while the machine is
> using personal firewalls and
> certain antivirus softwares.
> + Fixed a problem related to the NetMon COM
> component initialization. This
> bug caused random access violation errors while
> listing the adapters.
> + Removed a duplicated initialization of an event
> in the driver.
> + Added a check in packet.dll that prevents
> listing and opening of
> FireWire adapters, since they have a broken
> interface with NDIS and can
> cause blue screens.
> + Fixed a memory leak in PacketGetAdaptersIPH().
> + Fixed a check that could cause
> PacketSendPackets() to crash packet.dll.
> + Minor fixes.
>
> =========
>
>
> Changelog from WinPcap 3.1 beta3 to WinPcap 3.1
> beta4
>
=====================================================
>
> - wpcap.dll has been updated to libpcap 0.8.3 from
> http://www.tcpdump.org.
>
> - Added a note in the documentation that states that
> the kernel dump feature
> is disabled due to incompatibilities with the new
> kernel buffer.
>
> - Minor fixes to the documentation
>
> - Removed some useless files.
>
> - Bug fixing:
> + Fixed a bug related to COM initialization in
> WanPacket, by which
> WanAdapters were not working correctly if the
> calling thread was using
> COM with a different threading model.
> + Fixed a problem in AddAdapterIPH(), by which no
> adapter was actually
> added with this function because of a
> UNICODE/ASCII mismatch. Basically,
> AddAdapterIPH received an ASCII adapter name,
> and tried to open it with
> PacketOpenAdapterNPF, which accepts UNICODE
> strings, only.
> + Fixed a bug in the remote capture code due to
> concurrency issues when
> spawning a new thread
> + Fixed a problem related to the generation of
> grammar files with flex
> in the CygWin makefile.
> + Fixed a couple of memory leaks in
> PacketGetAdapterNames().
> PacketGetAdapterNames() seems to be still leaky,
> but the source of the
> leak seems to be a leaky API in the Microsoft
> IpHelperAPI, at least on
> WinXP SP1.
> + Added some code that frees the global list of
> adapters when packet.dll
> is unloaded (i.e. when DllMain is called with
> DLL_PROCESS_DETACH)
> + Fixed a bug that caused the adapters not to be
> listed on terminal
> services. The bug was caused by the lack of the
> "\\global" prefix in
> front of the adapter names.
> + Fixed a bug related to adapter opening in the
> pcap_filter example. Fixed
> the usage string that was wrong.
> + Fixed a bug in the JIT code of the driver that
> could potentially cause a
> BSOD if two threads try to set a filter (that
> will be jitted) at the
> same time.
> + Fixed a bug by which the driver fails to return
> any packet with a read
> after an IOCTL_SETBUFFER has changed the buffer
> size. The bug is due to
> some missing counter resets.
> + Fixed some debugging messages in the NT driver
> that were not macroed
> with IF_LOUD
>
> =========
>
>
> Changelog from WinPcap 3.1 beta2 to WinPcap 3.1
> beta3
>
=====================================================
>
> - Bug fixing:
> + Fixed a bug related to device listing if TCP/IP
> is not installed: on
> 2000/XP if TCP is not installed, it reported
> "you must install TCP/IP",
> and this was plain wrong.
> + Added PacketSetSnapLen() under Win9x. Without
> this function, wpcap.dll
> fails to load on Win9x.
> + PacketGetAdapterNames() has been rewritten under
> Win9x, in order to
> comply to the correct behavior specified in the
> documentation.
>
> =========
>
>
> Changelog from WinPcap 3.1 beta to WinPcap 3.1 beta2
>
=====================================================
>
> - Added some code to show a fake NdisWan adapter,
> useful to capture LCP/NCP
> packets. This adapter is always listed on
> 2000/XP/2003 (if you have enough
> privileges), even if you don't have any
> PPP/VPN/... connection
> established.
>
> - Added a check in the installer, so that the
> installation fails if you
>
=== message truncated ===
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Received on Aug 05 2005
Intro
