[Winpcap-users] error while building winpcap
gianluca.varenni at cacetech.com
Thu Nov 20 18:30:24 GMT 2008
----- Original Message -----
From: "Joshua (Shiwei) Zhao" <swzhao at gmail.com>
To: <winpcap-users at winpcap.org>
Sent: Thursday, November 20, 2008 8:37 AM
Subject: Re: [Winpcap-users] error while building winpcap
> On Tue, Nov 18, 2008 at 12:50 PM, Gianluca Varenni
> <gianluca.varenni at cacetech.com> wrote:
>> The sources of WinPcap 4.0.2 do not compile that smoothly with
>> In case you want to compile WinPcap with VS2005/2008, I suggest you to
>> the newest build available here:
>> Modifying the sources of WinPcap 4.0.2 to make it compile under
>> should not be too difficult, mainly a matter of tweaking some #define and
>> #include directives here and there, but using that source package should
>> much more straightforward.
>> Out of curiosity, which kind of modification were you trying to apply on
>> winpcap sources?
> The reason is that I have a WiFi chip that I can config its driver to
> pass packets in promiscuous mode. So I need the WinPcap driver to know
> that and be able to pass that to wireshark. I guess sth similar to
> what AirPcap does.
How do you configure your WiFi driver to go into promiscuous mode? Is it
done through the usual
OID_GEN_CURRENT_PACKET_FILTER, a custom OID code or some other mechanism?
> So my change only needs to rebuild the wpcap.dll. Now when I compile
> wpcap project, I run to an error which cannot find packet.lib or
> packet.dll. Since I don't want to rebuild packet.lib/.dll, can I just
> copy an existing one and use it to build wpcap.dll?
It's definitely possible to copy the version of packet.lib shipped with the
developer's pack into the proper folders.
The x86 packet.lib file should be put into
The x64 one should be put into
> In fact I'm not sure I really understand how WinPcap understand the
> driver's capability and then let Wireshark know it supports
> promiscuous mode. Are there some document describing the mechanism?
There's actually no mechanism to query for the promiscuous mode support.
WinPcap just tries to set the underlying miniport into promiscuous mode
(using OID_GEN_CURRENT_PACKET_FILTER) and returns failure in case the OID
Hope it helps
> Many thanks,
>> Have a nice day
>> ----- Original Message ----- From: "Joshua (Shiwei) Zhao"
>> <swzhao at gmail.com>
>> To: <winpcap-users at winpcap.org>
>> Sent: Monday, November 17, 2008 3:08 PM
>> Subject: [Winpcap-users] error while building winpcap
>>> Hi there,
>>> I'm thinking to make a small change in winpcap so that I can test my
>>> idea with wireshark. So I downloaded winpcap-4.0.2 source code and
>>> tried to build it at first.
>>> With both VS2008ee and VS2005ee, I met the following error message and
>>> I'm confused. Here studio.h is given by VS itself. How come it shows
>>> this error? Is there some configuration problem or what else?
>>> 1>C:\Program Files\Microsoft Visual Studio 9.0\VC\include\stdio.h(358)
>>> : error C3163: '_vsnprintf': attributes inconsistent with previous
>>> 1> C:\Program Files\Microsoft Visual Studio
>>> 9.0\VC\include\stdio.h(350) : see declaration of '_vsnprintf'
>>> I really appreciate your help.
>>> Winpcap-users mailing list
>>> Winpcap-users at winpcap.org
>> Winpcap-users mailing list
>> Winpcap-users at winpcap.org
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
More information about the Winpcap-users