Hi,
I am writing my first dissector for an internal protocol. Part of the
protocol is based on a spec that must be obtained via a web service based on
its ID. So in order to obtain the information needed to dissect the data I
need to make a web request to the service. What I'd like to do is just
On Tue, 9 Nov 2010 13:32:09 +0100, Stig Bjørlykke s...@bjorlykke.org
wrote:
On Sat, Nov 6, 2010 at 4:25 PM, etx...@wireshark.org wrote:
Log:
From Alexander Koeppe:
Patch that fixes overflowing highlighting of data.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5374
This patch
Holy crap - what spec is that??
-hadriel
On Nov 9, 2010, at 9:51 AM, Billy Prin wrote:
Hi,
I am writing my first dissector for an internal protocol. Part of the
protocol is based on a spec that must be obtained via a web service based on
its ID. So in order to obtain the information
Not sure why I don't see this message posted on gmane?
Anyway, I see you received a few responses already elsewhere:
- http://lkml.org/lkml/2010/11/9/243
- http://www.spinics.net/lists/linux-usb/msg38480.html
But I don't think those responses are technically correct. With the C
standard, there
Hi Devs,
I was advised via the wiki to send my request here.
Anyhow, here goes:
Wireshark's current stable release (1.4.1 at this time) does not have
the ability to decrypt broadcast/multicast 802.11 frames encrypted with
the Group Transient Key (GTK). I'd love to see this feature added. The
On Tue, Nov 09, 2010 at 01:32:09PM +0100, Stig Bj?rlykke wrote:
On Sat, Nov 6, 2010 at 4:25 PM, etx...@wireshark.org wrote:
Log:
From Alexander Koeppe:
Patch that fixes overflowing highlighting of data.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5374
Btw. should
On Nov 9, 2010, at 8:25 AM, Maynard, Chris wrote:
Not sure why I don't see this message posted on gmane?
Anyway, I see you received a few responses already elsewhere:
- http://lkml.org/lkml/2010/11/9/243
...in which Pete Zaitcev says:
Do be careful here, because the struct you're talking
Pete Zaitcev wrote:
On Tue, 09 Nov 2010 07:40:36 +0100
Németh Márton nm...@freemail.hu wrote:
I'm looking at the struct mon_bin_hdr and struct mon_bin_isodesc in file
f=drivers/usb/mon/mon_bin.c
Actually you're supposed to be looking at Documentation/usb/usbmon.txt.
If there is a
On Nov 9, 2010, at 12:05 PM, Németh Márton wrote:
OK, that's clear, the byte order of the API structure fields are in host
endian
order. The API structures are already saved by Wireshark into file for quite
some
time.
...and tcpdump. Support for capturing on USB on Linux has been in
