aboutsummaryrefslogtreecommitdiffstats
path: root/epan/dissectors/packet-bluetooth.c
AgeCommit message (Collapse)AuthorFilesLines
2017-08-31bluetooth: Update bluetooth_uuid_valsStig Bjørlykke1-0/+61
Change-Id: Idd3767f0b7fbd8cec606f7e3be138f310c6113eb Reviewed-on: https://code.wireshark.org/review/23328 Petri-Dish: Stig Bjørlykke <stig@bjorlykke.org> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Stig Bjørlykke <stig@bjorlykke.org>
2017-08-31bluetooth: Update bluetooth_company_id_valsStig Bjørlykke1-0/+191
Change-Id: I5c9761eacdfd3a668d5deb8aad46b0d3bee70051 Reviewed-on: https://code.wireshark.org/review/23327 Petri-Dish: Stig Bjørlykke <stig@bjorlykke.org> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Stig Bjørlykke <stig@bjorlykke.org>
2017-02-17Bluetooth: AD: Add dissector for Apple iBeaconMichal Labedzki1-0/+74
iBeacon is manufacturer specific (Apple) data in advertising packets. Based on: https://developer.apple.com/ibeacon/Getting-Started-with-iBeacon.pdf Use DecodeAs on advertise packet using field "BT EIR/AD Manufacturer Company ID" then select this dissector "Apple iBeacon". Change-Id: Ie3e50a391914054f33144d99734cf59fbda9683e Reviewed-on: https://code.wireshark.org/review/19970 Petri-Dish: Michal Labedzki <michal.tomasz.labedzki@gmail.com> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Anders Broman <a.broman58@gmail.com>
2017-02-07Bluetooth: AD: Add support for AltBeaconMichal Labedzki1-0/+83
Another format of beacon in advertising packet. Based on: https://github.com/AltBeacon/spec User needs to use DecodeAs to use this dissector - any manufacturer's company id may be valid. Change-Id: I5656d9dbb70b648b2fadba7f3b525d38a2fe8e57 Reviewed-on: https://code.wireshark.org/review/19971 Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com> Reviewed-by: Anders Broman <a.broman58@gmail.com>
2017-02-06Bluetooth: Update Assign NumbersMichal Labedzki1-65/+205
Updated on 5th February 2017: - UUIDs - Company Ids Change-Id: I9868891ee2bdcdaa687bd45c76429f2b476889cc Reviewed-on: https://code.wireshark.org/review/19973 Petri-Dish: Michal Labedzki <michal.tomasz.labedzki@gmail.com> Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com>
2016-12-05Bluetooth: Assigned Numbers: Update Member UUIDsMichal Labedzki1-1/+26
Update manually from time to time based on: https://www.bluetooth.com/specifications/assigned-numbers Change-Id: I506e58c16322862c9fe517b71ab12806818331b5 Reviewed-on: https://code.wireshark.org/review/19086 Petri-Dish: Michal Labedzki <michal.labedzki@tieto.com> Reviewed-by: Michael Mann <mmann78@netscape.net>
2016-11-04Bluetooth: Update Assigned Numbers: CompanyIDsMichal Labedzki1-5/+164
It comes from: https://www.bluetooth.com/specifications/assigned-numbers/Company-Identifiers To meet Wireshark requirements make them ASCII in case of some vendors. Change-Id: I66b8ce5a1bc6af03fae6efa18e594d83b586be38 Reviewed-on: https://code.wireshark.org/review/18664 Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
2016-08-31Don't do any Decode As stuff for dissector tables not used with Decode As.Guy Harris1-3/+3
Have all dissector tables have a "supports Decode As" flag, which defaults to FALSE, and which is set to TRUE if a register_decode_as() refers to it. When adding a dissector to a dissector table with a given key, only add it for Decode As if the dissector table supports it. For non-FT_STRING dissector tables, always check for multiple entries for the same protocol with different dissectors, and report an error if we found them. This means there's no need for the creator of a dissector table to specify whether duplicates of that sort should be allowed - we always do the check when registering something for "Decode As" (in a non-FT_STRING dissector table), and just don't bother registering anything for "Decode As" if the dissector table doesn't support "Decode As", so there's no check done for those dissector tables. Change-Id: I4a1fdea3bddc2af27a65cfbca23edc99b26c0eed Reviewed-on: https://code.wireshark.org/review/17402 Petri-Dish: Guy Harris <guy@alum.mit.edu> Reviewed-by: Guy Harris <guy@alum.mit.edu>
2016-05-22Bluetooth: Update Member UUIDs and CompanyIDsMichal Labedzki1-10/+200
Update member UUIDs and CompanyIDs from Bluetooth Assign Numbers. Change-Id: I5deb5b8e930d2df0296f17a3fe3b46989a28a86d Reviewed-on: https://code.wireshark.org/review/15453 Petri-Dish: Michal Labedzki <michal.labedzki@tieto.com> Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com> Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com>
2016-05-20Bluetooth: GATT: Add support for PLXS/PLXPMichal Labedzki1-0/+3
PLXS is Pulse Oximeter Service used by some pulse oximetry sensor for consumer and professional healthcare applications. Change-Id: Iab5b7dd3e4bfb58cef0cc2c76df1e3aab69f35c7 Reviewed-on: https://code.wireshark.org/review/15452 Petri-Dish: Michal Labedzki <michal.labedzki@tieto.com> Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com> Tested-by: Michal Labedzki <michal.labedzki@tieto.com>
2016-04-02Bluetooth: Fix conflicting address fieldsMichal Labedzki1-23/+39
For Broadcast address use FT_ETHER with FF:FF:FF:FF:FF:FF address instead of string address "Broadcast". Change-Id: I638d3d6a1baa9c965dd0a9f548cedbd81af3ec5b Reviewed-on: https://code.wireshark.org/review/14767 Petri-Dish: Michal Labedzki <michal.labedzki@tieto.com> Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com> Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com> Tested-by: Michal Labedzki <michal.labedzki@tieto.com>
2016-03-28Fix more -Wused-but-marked-unused warnings/errors.Joerg Mayer1-2/+2
Change-Id: Ieb3e70a23c1a55b7ba60b1b32f159341adfe65b7 Reviewed-on: https://code.wireshark.org/review/14682 Reviewed-by: Jörg Mayer <jmayer@loplof.de>
2016-03-20Create call_data_dissector() to call data dissector.Michael Mann1-5/+3
This saves many dissectors the need to find the data dissector and store a handle to it. There were also some that were finding it, but not using it. For others this was the only reason for their handoff function, so it could be eliminated. Change-Id: I5d3f951ee1daa3d30c060d21bd12bbc881a8027b Reviewed-on: https://code.wireshark.org/review/14530 Petri-Dish: Michael Mann <mmann78@netscape.net> Reviewed-by: Michael Mann <mmann78@netscape.net>
2016-03-20Manually add protocol dependencies derived from find_dissector.Michael Mann1-2/+2
Started by grepping call_dissector_with_data, call_dissector_only and call_dissector and traced the handles passed into them to a find_dissector within the dissector. Then replaced find_dissector with find_dissector_add_dependency and added the protocol id from the dissector. "data" dissector was not considered to be a dependency. Change-Id: I15d0d77301306587ef8e7af5876e74231816890d Reviewed-on: https://code.wireshark.org/review/14509 Petri-Dish: Michael Mann <mmann78@netscape.net> Reviewed-by: Michael Mann <mmann78@netscape.net>
2016-03-17Associate dissector tables and heuristic subdissector lists with a protocol.Michael Mann1-3/+51
This will make it easier to determine protocol dependencies. Some LLC OUI dissector tables didn't have an associated protocol, so they were left without one (-1 used) Change-Id: I6339f16476510ef3f393d6fb5d8946419bfb4b7d Reviewed-on: https://code.wireshark.org/review/14446 Reviewed-by: Michael Mann <mmann78@netscape.net>
2016-03-09Bluetooth: GATT: Add a lot of attributes usage expert infosMichal Labedzki1-6/+6
Bluetooth Specifications specify properties of every characteristics (read, write, indicate, notify, write without response, signed write etc.) Check it and add expert info about invalid usage if detected use of wrong opcode with the characteristic. Change-Id: I98ad8280b9ee65b4015a021e732ea748cc9e7a83 Reviewed-on: https://code.wireshark.org/review/14313 Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
2016-02-19Don't call the hci_usb dissector through a dissector table.Guy Harris1-5/+20
It works the same regardless of what flavor of USB metadata there is, and there's no good reason for any Bluetooth code to know, or care, about particular flavors of USB metadata. Add some comments while we're at it. Change-Id: I6ea2063a015e424fc84a407231e80ef3e2a79c98 Reviewed-on: https://code.wireshark.org/review/14001 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2016-01-25Move the proto data stuff out of frame_data.[ch].Guy Harris1-0/+1
It's not tied to the frame_data structure any more, so it belongs by itself. Clean up some #includes while we're at it; in particular, frame_data.h doesn't use anything related to tvbuffs, so don't have it gratuitiously include tvbuff.h. Change-Id: Ic32922d4a3840bac47007c5d4c546b8842245e0c Reviewed-on: https://code.wireshark.org/review/13518 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2016-01-24Add the packet number to the packet_info structure, and use it.Guy Harris1-3/+3
That removes most of the uses of the frame number field in the frame_data structure. Change-Id: Ie22e4533e87f8360d7c0a61ca6ffb796cc233f22 Reviewed-on: https://code.wireshark.org/review/13509 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2016-01-23Add more fields to packet_info structure and use them.Guy Harris1-1/+1
Add fields for the absolute time stamp (and another field for a presence flag for the absolute time stamp) and the packet encapsulation for the packet. This lets us remove the field for the packet encapsulation in the frame_data structure; do so. Change-Id: Ifb910a9a192414e2a53086f3f7b97f39ed36aa39 Reviewed-on: https://code.wireshark.org/review/13499 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2016-01-18Bluetooth: Update Assign numbers (5th December 2015)Michal Labedzki1-0/+66
Add TDS and OTS/OTP UUID, OTS PSM (I cannot find it, but it seems to be linear), update CompanyIds and add three EIR/AD codes: URI, Indoor Positioning and Transport Discovery Data. Implementation of new "numbers" will be done later. Change-Id: I8ad4d9c1d55c1824d87e88303c28e67dd445ec98 Reviewed-on: https://code.wireshark.org/review/13386 Petri-Dish: Anders Broman <a.broman58@gmail.com> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Anders Broman <a.broman58@gmail.com>
2015-12-12Remove -Wwrite-strings compiler flagJoão Valverde1-2/+2
The "-Wwrite-strings" flag produces nuisance warnings. These warnings are not useful, they're impossible to fix in a sane way and therefore are being handled with casts of static strings to (char *). This just moves the warning to [-Wcast-qual] and a compiler pragma is in turn required (and used) to squelch that warning. Remove the Wwrite-strings warning. Let that responsibility fall on the programmer (as is done by casting). Change-Id: I5a44dfd9decd6d80797a521a3373593074962fb5 Reviewed-on: https://code.wireshark.org/review/12162 Petri-Dish: Alexis La Goutte <alexis.lagoutte@gmail.com> Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com> Reviewed-by: Michael Mann <mmann78@netscape.net>
2015-12-09new_register_dissector -> register_dissector for dissector directory.Michael Mann1-1/+1
Change-Id: Ie39ef054a4a942687bd079f3a4d8c2cc55d5f22c Reviewed-on: https://code.wireshark.org/review/12485 Petri-Dish: Michael Mann <mmann78@netscape.net> Reviewed-by: Michael Mann <mmann78@netscape.net>
2015-12-09new_create_dissector_handle -> create_dissector_handle for dissector directory.Michael Mann1-4/+4
Some of the ASN.1 dissectors still generate a new_create_dissector_handle from the tool itself, so leave those for now. Change-Id: Ic6e5803b1444d7ac24070949f5fd557909a5641f Reviewed-on: https://code.wireshark.org/review/12484 Petri-Dish: Anders Broman <a.broman58@gmail.com> Reviewed-by: Michael Mann <mmann78@netscape.net>
2015-11-25Use try_val_to_str_ext() in print_uuid().Guy Harris1-10/+21
That's a much cleaner way of determining whether you found no matchin bluetooth_uuid_vals_ext than checking whether val_to_str_ext_const() returned the "use this if unknown" value. It also lets us avoid a wmem_strdup(). Make print_numeric_uuid() and print_uuid() return const gchar *; there's no reason for them *not* to be const, and that means we don't have to throw away constness. Change-Id: I62fb0b81c64c107dfea6c16ca8c5b9593f8f2a9d Reviewed-on: https://code.wireshark.org/review/12126 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2015-11-20Bluetooth: Update company IDs and Member/SDO UUIDsMichal Labedzki1-77/+368
Update company IDs and Member/SDO UUIDs to latest Assign Number. Change-Id: Ia543ab1bcf43cf5283658cbe0971c8bc9877426d Reviewed-on: https://code.wireshark.org/review/11979 Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
2015-11-20Bluetooth: GATT: Add HTTP Proxy Service attributesMichal Labedzki1-0/+7
Add HTTP Proxy Service attributes and UUID. Change-Id: If0ab490f2df0930d2b80687ac4c9a1d7e4d463e4 Reviewed-on: https://code.wireshark.org/review/11978 Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
2015-11-20Bluetooth: Add ability to add custom UUID descriptionMichal Labedzki1-33/+19
Some vendors use UUID128 as own services/attributes. Sometimes they use UUID16 for it too. Support both cases. Change-Id: I001692b94fcc2f86eafa81012790e9134b0f2a36 Reviewed-on: https://code.wireshark.org/review/11976 Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
2015-11-04Don't allow multiple registrations of a protocol in dissector tables.Michael Mann1-3/+3
The target here is the Decode As dialog where protocols have multiple registrations into a dissector table and that shows up as multiple entries in the Decode As dialog list with the same name so users are unsure which "dissector" they are choosing. The "default" behavior (done in this commit) is to not allow duplicates for a dissector table, whether its part of Decode As or not. It's just ENFORCED for Decode As. Bug: 3949 Change-Id: Ibe14fa61aaeca0881f9cc39b78799e314b5e8127 Reviewed-on: https://code.wireshark.org/review/11405 Petri-Dish: Michael Mann <mmann78@netscape.net> Reviewed-by: Michael Mann <mmann78@netscape.net>
2015-11-01bluetooth: Fix uninitialized value warningJoão Valverde1-3/+2
Change-Id: Iee1d1cf3e24dacca3c1a353001a8af71e074a96b Reviewed-on: https://code.wireshark.org/review/11454 Reviewed-by: Martin Kaiser <wireshark@kaiser.cx> Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com> Petri-Dish: Michal Labedzki <michal.labedzki@tieto.com> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Michael Mann <mmann78@netscape.net>
2015-10-17Bluetooth: ATT: Print names assigned to handles in info columnMichal Labedzki1-2/+8
This increase readability. Change-Id: I033ae557316f40b292da2c9b3f99692bbe21cf4d Reviewed-on: https://code.wireshark.org/review/11020 Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
2015-10-17Bluetooth: Fix displaying and handling UUID128Michal Labedzki1-13/+52
Use a standard way of displaying 128 UUIDs (like GUID). This also change a way that UUID are handled by dissector tables. Change-Id: Ie0f880f58480c34b40dd23c426202349e0620b12 Reviewed-on: https://code.wireshark.org/review/11018 Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
2015-10-16Bluetooth: GATT: Add support for Nordic's vendor UUIDsMichal Labedzki1-2/+9
Add DFU and UART services support. Change-Id: I028fab3aa826c1d944ccfa0624cf33ce566a5099 Reviewed-on: https://code.wireshark.org/review/11015 Petri-Dish: Michal Labedzki <michal.labedzki@tieto.com> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Anders Broman <a.broman58@gmail.com>
2015-09-14Bluetooth: Add "PAN" prefix to three UUIDsMichal Labedzki1-3/+3
"GN" does not seems to be really useful, but "PAN GN" is reasonable. Change-Id: Ia04aa20e4b95743c7db46e87606e3843a124d7e4 Reviewed-on: https://code.wireshark.org/review/10524 Reviewed-by: Michael Mann <mmann78@netscape.net>
2015-08-18Bluetooth: Update Assign NumbersMichal Labedzki1-7/+25
+18 ATT attributes to be implemented (IPS 1.0 - 19 May 2015, etc.) Change-Id: Ib30ea20fe9b32a4be842f01ad5b8e8ee081a14ff Reviewed-on: https://code.wireshark.org/review/10095 Reviewed-by: Anders Broman <a.broman58@gmail.com>
2015-07-17Qt/Bluetooth: Add HCI Summary dialogueMichal Labedzki1-0/+2
HCI Summary dialogue collect HCI Opcodes, HCI Events, Hardware Errors, Statuses and Reasons. Also show occurrence of them. The top level item is group of items (by OGF or types), the second level item is in real command, event, hardware error, status or reason. The third level items are direct link to packet that contains second level item type. Change-Id: I6b6bd02533c4605a2dd2c1f5dfee46f72a0f3fdc Reviewed-on: https://code.wireshark.org/review/9676 Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com> Tested-by: Alexis La Goutte <alexis.lagoutte@gmail.com> Petri-Dish: Michal Labedzki <michal.labedzki@tieto.com> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
2015-07-17Bluetooth: Add generic UUID table for DecodeByMichal Labedzki1-0/+35
Replace L2CAP Service, RFCOMM Service and AVCTP PID dissector table by shared Bluetooth Service UUID table. It also supports UUID16, UUID32 and UUID128 by hex-string, like for AVRCP: "110e". Change-Id: I473bc73d10939e8ed6dd55a6a92387c7a1ec125a Reviewed-on: https://code.wireshark.org/review/9678 Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
2015-06-16Pass the pseudo-header to wtap_encap dissectors via the "data" argument.Guy Harris1-4/+4
Have the "data" argument to dissectors registered in thw wtap_encap dissector table point to the pseudo-header for the packet. Use that argument in the Bluetooth dissector. Change-Id: I022bbfb796ef51d95df09fb952a149960170d631 Reviewed-on: https://code.wireshark.org/review/8951 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2015-06-16Clean up handling of metadata in Bluetooth dissectors.Guy Harris1-24/+131
Make the "previous protocol data" union in bluetooth_data_t a discriminated union, and use the discriminator to decide whether to use a given member of the union or not (or to check whether the member you plan to use is valid). Have separate top-level dissectors depending on what the data type pointed to by the "data" argument is. Use that member to point to pseudo-header metadata, and, for now, set it to point to the appropriate pinfo->pseudo_header value; eventually, we plan to pass the pseudo-header pointer in as the "data" argument from the "frame" dissector. Don't overwrite the pseudo-header in the packetlogger dissector - construct a new one and pass it in. Change-Id: Ia1ef71e7082a964c5d92d47221f8c00e32f3f087 Reviewed-on: https://code.wireshark.org/review/8943 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2015-06-15Qt/Bluetooth: Add Devices dialogueMichal Labedzki1-1/+18
Please found it under Bluetooth menu. It shows all devices found in logs, not only connected, all that its address can be found in logs. Show if device is local (in most cases: capturing on it side) and manufacturer and LMP version what should answer the question what version of Bluetooth is used by Bluetooth device chip. Also firmware version. Change-Id: I32e3b7100cdebcaa850b6541de0ab89dff41c0e1 Reviewed-on: https://code.wireshark.org/review/8901 Petri-Dish: Michal Labedzki <michal.labedzki@tieto.com> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Tested-by: Michal Labedzki <michal.labedzki@tieto.com> Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
2015-04-01Bluetooth: fix Uninitialized scalar variable (CID 1268203)Alexis La Goutte1-1/+1
Change-Id: Ic9e47a32dc935e3e121cd49d4b378021c122aecd Reviewed-on: https://code.wireshark.org/review/7866 Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com> Petri-Dish: Alexis La Goutte <alexis.lagoutte@gmail.com> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
2015-02-07Don't call the Bluetooth code's UUID type "uuid_t".Guy Harris1-4/+4
uuid_t is a data type provided by a number of environments, thanks to the Open Software Fuundation; calling the Bluetooth code's data type, which includes an actual OSF-style UUID as a member, "uuid_t" can lead to confusion and *does* lead to compile errors on platforms where, for better or worse, system headers such as <unistd.h> define uuid_t (and are included by, for example, Qt headers). Just rename it "bluetooth_uuid_t". Change-Id: Ic742723913ba4105cd3269dd24fc821147285176 Reviewed-on: https://code.wireshark.org/review/7017 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2015-02-07Bluetooth: ATT: Use proto_tree_add_new_bytes for UUID128Michal Labedzki1-1/+2
Change-Id: I018b3e125bcbb6908276dd2b3b9f66def9aa745b Reviewed-on: https://code.wireshark.org/review/6907 Petri-Dish: Michal Labedzki <michal.labedzki@tieto.com> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Tested-by: Michal Labedzki <michal.labedzki@tieto.com> Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
2015-02-07Bluetooth/GUI: ATT: Add Server Attribute TableMichal Labedzki1-5/+5
It is a GUI+QT feature that introduce Bluetooth menu and "ATT Server Attributes" that present all handle+UUID pairs as table. User may copy cell value, row, selected rows or whole table within header. On activate user will go to packet that introduce UUID for specified handle. Change-Id: If17e53aff5feb89ededc740a595ba5882b90be5e Reviewed-on: https://code.wireshark.org/review/6911 Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
2015-02-03Bluetooth: ATT: Dissect almost all attributesMichal Labedzki1-1/+10
Change-Id: Ia388c07150d9664327daf2d1990b4465b5f4ae28 Reviewed-on: https://code.wireshark.org/review/6910 Petri-Dish: Michal Labedzki <michal.labedzki@tieto.com> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
2015-02-03Bluetooth: ATT: Dissect GATT levelMichal Labedzki1-0/+62
ATT dissector is now able to decode GATT level fields. This is results of added request-response tracking/share information. Change-Id: I41ac622a38916a7a20f625fa30ac72d7812446c6 Reviewed-on: https://code.wireshark.org/review/6904 Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
2015-02-02Bluetooth: Simplify to "UnknownDirection" in Info column when direction is ↵Michal Labedzki1-5/+1
unknown Change-Id: Ibad679c0b6c95d65389ce087f65b8f31cf3acd68 Reviewed-on: https://code.wireshark.org/review/6903 Petri-Dish: Michal Labedzki <michal.labedzki@tieto.com> Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
2015-01-10Bluetooth: HCI: Detect Vendor by "Read Local Version Information"Michal Labedzki1-0/+6
There is information about manufacturer of Bluetooth chip. Also try to detect if that "permament" info is not changed, if so informs user about this rare event (probably there is an issue) Change-Id: I1fa748a67ad7943e61d4445d240f0578b94560fc Reviewed-on: https://code.wireshark.org/review/6408 Petri-Dish: Michal Labedzki <michal.labedzki@tieto.com> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com> Tested-by: Michal Labedzki <michal.labedzki@tieto.com>
2015-01-10Bluetooth: SMP: Add missing opcode for "Identity Address Information"Michal Labedzki1-2/+8
Also fix tvb_length, tvb_length_remaining warnings. Bug: 10299 Change-Id: Ib8b55ea9f2220394a5896d13e5cc4e2cefff1e13 Reviewed-on: https://code.wireshark.org/review/6407 Petri-Dish: Alexis La Goutte <alexis.lagoutte@gmail.com> Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com> Tested-by: Michal Labedzki <michal.labedzki@tieto.com>
2015-01-10Bluetooth: Add HCI Vendor Broadcom dissectorMichal Labedzki1-0/+52
Since those command/events are vendor specific and proprietary not all commands/events are implemented. All implemented commands can be found in Open Source implementations for Broadcom chip. If you found more, please let me know. Change-Id: Ie68d3737c88a8cef39260a9d93192cfc81871d6c Reviewed-on: https://code.wireshark.org/review/6406 Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com> Tested-by: Michal Labedzki <michal.labedzki@tieto.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-01 06:37:08 +0000