I tried WinPcap 2.1 beta with Ethereal. Yes, making WinPcap a DLL solves my
linking problem, I
can now make wiretap a DLL, too.
And more importantly, it is working well. The interface is Ethernet. My OS
is Win2000.
Thanks for the fine work!
--gilbert
"Fulvio Risso" <risso@xxxxxxxxx> on 11/13/2000 09:50:59 AM
To: ethereal-dev@xxxxxxxxxxxx
cc: WinPcap@xxxxxxxxxxxxxxxxxxxxxxx, "Bruno Quarta"
<brunoq@xxxxxxxxxxxxx>, "Marco Mezzalama" <marco@xxxxxxxxx> (bcc:
Gilbert Ramirez/Tivoli Systems)
Subject: [Ethereal-dev] WinPcap 2.1 beta
Hello everyone.
We've published WinPcap 2.1 beta on our web site.
Executable, sources, developer's pack can be downloaded from the WinPcap
web
site:
http://netgroup-serv.polito.it/WinPcap/
We think it should be stable enough; more important, the installation
process is now dynamic (.inf files are no longer required). This is a
non-negligible improvement... almost 60% of the request on our mailing list
was due to the installation procedure.
This new release of WinPcap could break compatibility because the library
is
no longer a static .lib file and it is a dynamic DLL instead. Even if
packet.dll is more or less the same of previous version, some problem could
appear. Moreover old applications, statically linked with libpcap.lib,
cannot get advantage of the bug fixing done in this release.
Names are changed: now WinPcap creates a file called WPcap.dll (instead of
libpcap.lib). This is because we plan (hopefully) to insert new features
(not available in libpcap) in our library. So, in order not to get
confused,
we prefer call it "WinPcap" instead of "libpcap".
Any comment / suggestion / bugs fixing is appreciated.
Cheers,
fulvio
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
