Gerald Combs wrote:
As far as the Airpcap code being Windows-specific: we've tried to
generalize it so that it can be adapted to other platforms. There's no
reason the code that calls airpcap_if_set_device_channel() under Windows
can't (and shouldn't) use the SIOCSIWFREQ ioctl under Linux.
I originally posted this to the user list, but it was suggested
this is a better forum.
I am having problems with a CORBA protocol plugin. I have generated
the .c file using :-
omniidl -p c:\wireshark-0.99.3a\tools -b wireshark_be q_quentinv3.idl
packet-quentinv3.c
and built and installed the
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 working on
de-Windows-izing the
Hi,
Perhaps a fault in the GIOP dissector. Can you send the text output of
the failed decoding?
BR
Anders
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: den 7 december 2006 10:53
To: wireshark-dev@wireshark.org
Subject:
[EMAIL PROTECTED] wrote on 07/12/2006 12:52:43:
Hi,
Perhaps a fault in the GIOP dissector. Can you send the text output of
the failed decoding?
BR
Anders
I'm not 100% sure which bit you are after, but the packet
bytes look like :-
Frame 199 (130 bytes on wire, 130 bytes captured)
Hi.
The newly added eap_handle in packet-isakmp (revision 20054) breaks
building on OSX.
The attached patch will fix this for packet-isakmp and packet-radius,
which had the same variable name eap_handle.
I find alot of dissectors using global dissector_handle_t. Should
this be fixed for
On Wed, Dec 06, 2006 at 02:20:52PM +0100, Francesco Fondelli wrote:
Could you write up some documentation changes to doc/README.developer
so others will know how to use this feature. You can send a diff of
only README.developer since we already have the other patches. We
will then review
Loris Degioanni wrote:
Yes, this would be the optimal option, but it would require adding to
libpcap features that are not strictly capture oriented, like setting
a channel or configuring a set of decryption keys.
I'd consideer setting a channel capture-oriented, as a capture
application
