Yes, but it’s rooted pretty deep in some of the libpcap sources. That code was actually working at some point on linux and there was some idea to include it
in libpcap vs. being a patch for WinPcap. I don’t know what happened to that plan. AFAIK, there were also some security concerns about the protocol used for transferring the packets (I don’t know the details), and that might be one of the reasons why it was
never pushed back to upstream.
From: Yang Luo [mailto:hsluoyb@xxxxxxxxx]
Sent: Wednesday, April 13, 2016 5:14 PM
To: Developer support list for Wireshark; Gianluca Varenni
Subject: Re: [Wireshark-dev] Get "Malformed Packet" for 802.11 Beacon frames on Windows
Hi Gianluca,
On Thu, Apr 14, 2016 at 2:06 AM, Gianluca Varenni <Gianluca.Varenni@xxxxxxxxxxxx> wrote:
The underlying problem is integrating remote capture support, I don’t know what the latest is there.
I didn't touch that part of code before. It seems to be a Windows-only feature.
From:
wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx]
On Behalf Of Graham Bloice
Sent: Wednesday, April 13, 2016 9:55 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Get "Malformed Packet" for 802.11 Beacon frames on Windows
On 13 April 2016 at 17:23, Gianluca Varenni <Gianluca.Varenni@xxxxxxxxxxxx> wrote:
Graham/Yang,
Please unicast me and I can give you some hints on how wpcap.dll is compiled on Windows. Shortly,
we take the libpcap sources and apply a pretty substantial patch on it to compile on Windows.
Thanks! I want to know how to compile/integrate the latest libpcap code into wpcap.dll. I don't know the steps.
We haven't changed what happens at all with wpcap.dll. I guess we'll have to just make a big jump to current libpcap and create another patch to fix what hurts, although I know
Guy was keen to make libpcap compile correctly on Windows.
--
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:
https://www.wireshark.org/lists/wireshark-dev
Unsubscribe:
https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
|
