[Winpcap-users] SharpPcap as wrapper

Gianluca Varenni gianluca.varenni at cacetech.com
Thu Dec 21 16:37:59 GMT 2006


I think the problem is that SharpPcap does not have any knowledge of the 
radiotap link layer, and reverts to the default ethernet header when it 
doesn't know the link layer.

In particular, I think you should have a look at the SharpPcap sources, and 
modify the file LinkLayer.cs (at least).

Have a nice day
GV

----- Original Message ----- 
From: <GefRaitaSep at uboot.com>
To: <winpcap-users at winpcap.org>
Sent: Monday, December 18, 2006 2:25 PM
Subject: [Winpcap-users] SharpPcap as wrapper


> Hello!
>
> I know it´s not the best position to post here a question about SharpPcap 
> the .NET-Wrapper of winpcap, but for SharpPcap doesn´t exist no forum nor 
> mailing list and I thought some .NET experts using winpcap and sharppcap 
> could hopefully answer my question.
>
> As mentioned I´m using SharpPcap in my C# app. Since I´m trying to use 
> AirpCap I found out that pcapDataLink and dataLinkLength and 
> protocolOffset seems to be wrong for 802.11 packets from AirPcap. But the 
> real problem is I´m receiving packets with 38 byte length from SharpPcap 
> altough radiotap and 802.11 header should both have 24 byte (and Airpcap 
> is should receive them because of my settings). In contrary to this, 
> wireshark shows correct packets.
>
> Does anybody know something about this problem?
>
> Best regards, Bernhard
> -----
> www.uboot.com - community mit gratis blog, video, foto, gallery,
> chat, adressbuch, sms, mail, nickpage, web space
>
> _______________________________________________
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
> https://www.winpcap.org/mailman/listinfo/winpcap-users 



More information about the Winpcap-users mailing list