| Bug ID |
8396
|
| Summary |
Bluetooth: Add HCRP dissector
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
SVN
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Enhancement
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
michal.labedzki@tieto.com
|
Created attachment 10118 [details]
Example HCRP logs (fake)
Build Information:
TShark 1.9.1 (SVN Rev Unknown from unknown)
Copyright 1998-2013 Gerald Combs <gerald@wireshark.org> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GLib 2.32.3, with libpcap, with libz 1.2.3.4, with POSIX
capabilities (Linux), with libnl 2, with SMI 0.4.8, with c-ares 1.7.5, with Lua
5.2, without Python, with GnuTLS 2.12.14, with Gcrypt 1.5.0, with MIT Kerberos,
with GeoIP.
Running on Linux 3.6.9, with locale en_IE.UTF-8, with libpcap version 1.1.1,
with libz 1.2.3.4.
Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Built using gcc 4.4.7.
--
Bluetooth: Add HCRP dissector
Add support for Bluetooth HCRP Profile version 1.2.
Based on specification from:
https://www.bluetooth.org/Technical/Specifications/adopted.htm
Please check example logs: Go to frame 23 and try to DecodeBy for L2CAP PSM
0x1003, 0x1005 and 0x1007 as HCRP. Now you can see HCRP Control channel,
data channel and notification channel. Unfortunately user must manually specify
other required data for correctly recognize payload. Go to HCRP preferences
ensure "Is that Client?" is checked and set "L2CAP PSM for Control" to 4099,
"L2CAP PSM for Data" to 4101 and "L2CAP PSM for Notification" to 4103. Later,
you can uncheck "Is that Client" and check payload again (of course there
should be malformed frames, but some other cases are supported
[see notification channel]).
PS. Well, we are close to implement full Bluetooth stack in Wireshark.
There is still (minor) unimplemented or partially implemented: DI (will be:
HCI/SDP part), HDP (license to buy, so this can be ignored), GNSS (like HDP,
but there
are many free unofficial specifications) and Bluetooth Low Energy Profiles
(GATT-based, will be part of btatt?), HFP (work ongoing).
All specification are available on:
https://www.bluetooth.org/Technical/Specifications/adopted.htm
You are receiving this mail because:
- You are watching all bug changes.
