Wireshark friends,
I’d like to announce sysdig, the latest open source project I’ve been
working on together with the team at my new startup, Draios.
http://www.sysdig.org/
https://github.com/draios/sysdig
Sysdig tries to bring the network analysis workflow to Linux system
troubleshooting, an
Guy Harris wrote:
> Luis EG Ontanon wrote:
>> Windows does not implement it as does not even have selectable fds or
>> at least the one select() in winsock does not work on FDs so for
>> WinPcap another approach should be taken (Gianluca?)
>
> I *should* be possible to get the handles for the
Guy Harris wrote:
> Davide Schiera wrote:
>
>> The structures are used to wrap the header of a 802.11 packet.
>> The base format of these structures are
>> UCHAR fc[2];
>> UCHAR dur[2];
>> UCHAR addr1[AIRPDCAP_MAC_LEN];// addr1[6]
>> UCHAR addr2[AIRPDCAP_MAC_LE
Joerg Mayer wrote:
> Gerald,
>
> On Wed, Dec 06, 2006 at 02:53:31PM -0800, Gerald Combs wrote:
>> The WPA code (specifically the modules in the airpdcap directory) is
>> Windows-specific because we might use same code base for WPA decryption
>> in Wireshark and in the Airpcap driver. We're worki
No, it's just not implemented in Wireshark yet. We'll work on adding it
in future versions.
Loris
Douglas F. Calvert wrote:
> Is there a technical reason why you cannot channel hop with the airpcap
> device?
> ___
> Wireshark-dev mailing list
> Wiresh
Ulf Lamping wrote:
> [EMAIL PROTECTED] wrote:
>> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=19747
>>
>> User: gerald
>> Date: 2006/10/31 01:44 AM
>>
>> Log:
>> From Giorgio Tino: Add a "Don't show this message again" option to an
>> AirPcap warning dialog. Fix a callback
