I've checked in a slightly different fix in r20053. Tomas, can you
verify that it works on your system?
Giorgio Tino wrote:
> Hi Tomas,
> HAVE_AIRPDCAP is a define, used to compile Wireshark with the support of WPA
> and WPA2.
> It is defined in 3 makefiles: \Makefile.nmake,
> \epan\dissectors\Makefile.nmake, \gtk\Makefile.nmake (surely we can define
> it only once as we did for HAVE_AIRPCAP, for example).
>
> This define is not (well, it should not be...) correlated to HAVE_AIRPCAP,
> used to support the AirPcap device.
>
> The problem in packet-ieee80211.c is the code at line 77. Before patching
> that code, you can modify packet-ieee80211.c by moving the two includes
> before the #ifdef, thus:
>
> #include <airpcap.h>
> #include <airpcap_loader.h>
> #ifndef HAVE_AIRPCAP
> /* XXX - This is probably a bit much */
> #define MAX_ENCRYPTION_KEYS 64
> #endif
>
> Those two #includes are needed because of some #defines and macros (such
> as maximum number of decryption keys, struct used to describe decryption
> keys
> and so on...) that Wireshark and AirPcap 'share'. Those structs and defines
> are used
> by the WPA/WPA2 decryption stuff, and should be included even if
> HAVE_AIRPCAP
> (AirPcap adapter support) is not defined.
>
> We will try to remove AirPcap dependency from code used with HAVE_AIRPDCAP
> (WPA/WPA2 decryption) as soon as possible.
>
> Giorgio
>
>
> ----- Original Message -----
> From: "Kukosa, Tomas" <tomas.kukosa@xxxxxxxxxxx>
> To: "Developer support list for Wireshark" <wireshark-dev@xxxxxxxxxxxxx>
> Sent: Wednesday, December 06, 2006 8:01 AM
> Subject: [Wireshark-dev] HAVE_AIRPDCAP
>
>
>> Hello,
>>
>> what is the purpose of HAVE_AIRPDCAP macro?
>> It is always defined in all makefile.nmake files regardless AirPcap is
>> available or not.
>> Unfortunately I can not compile packet-ieee80211.c file on Windows
>> without AirPcap.
>>
>> Any suggestions?
>>
>> _______________________________________________
>> Wireshark-dev mailing list
>> Wireshark-dev@xxxxxxxxxxxxx
>> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev