Re: [Wireshark-dev] Bluetooth coloring rules

Hi, > On Tue, Apr 30, 2013 at 7:54 PM, Gerald Combs wrote: >> About half of our coloring rules are for various Bluetooth protocols. >> Would anyone object to moving them to a Bluetooth-specific global >> configuration profile? I don't think they belong in the default profile >> but I'd rather not

Re: [Wireshark-dev] GSOC ideas: protocol buffers dissector andFileshark

Hi, > Dnia 18 kwietnia 2013 17:56 Guy Harris napisał(a): >> ...except in those places where the UI *should* be different. For example, >> when showing a JPEG, Wireshark doesn't have multiple items in the "packet >> list" pane, because the JPEG is in, for example, a single HTTP message. >> Ho

Re: [Wireshark-dev] Wireshark 1.9.2 is now available

Hi, > New and Updated Features > > The following features are new (or have been significantly > updated) since version 1.8: > * USB type and product name support has been improved. Ok, I propose to add information about: * Support all Bluetooth profiles/protocols There is nothing more

Re: [Wireshark-dev] Bluetooth SBC codec in RTP Player

Hi, > Sent: 26 March 2013 22:06 > To: Developer support list for Wireshark > Subject: Re: [Wireshark-dev] Bluetooth SBC codec in RTP Player > > Hi, > > Two questions: > 1) Why move codec infrastructure into epan? I don't understand the rationale. Is there other way to handle that? Please feel f

[Wireshark-dev] Bluetooth SBC codec in RTP Player

Hi All, I want to ask about how to add SBC codec support to RTP Player. SBC is codec used by Bluetooth. There is GPL library for that (libsbc developed by BlueZ developers). I decided to move codecs to "epan" directory and small extend existing fine API - my idea can be simply described in word

[Wireshark-dev] Automatic update USB Vendor ID / Product ID

Hi All, Is that possible to add automatic update dor USB VendorID/ProductID like this one: "[Automatic manuf, services and enterprise-numbers update for 2013-03-10]" http://code.wireshark.org/git/?p=wireshark;a=commit;h=8b215accd052336054004cd6f33a1623d4dedec0 Update can be done by run: "python

Re: [Wireshark-dev] new dissector - dynamic value string table?

Hi Max, > On the first question of detecting the camera type, it looks like the > information I need is captured by packet-usb.c (emem_tree_t > *device_to_product_table) -- however it's not exported. I will need to > add a way of getting access to this tree from the new dissector. I guess you d