Wireshark-bugs: [Wireshark-bugs] [Bug 10524] New: Bluetooth Smart: Add GATTdissector
| Bug ID |
10524
|
| Summary |
Bluetooth Smart: Add GATTdissector
|
| Product |
Wireshark
|
| Version |
1.12.1
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Enhancement
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
aravind.parvathala@csr.com
|
Build Information:
Version 1.12.1 (v1.12.1-0-g01b65bf from master-1.12)
Copyright 1998-2014 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 GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.1.22, with Gcrypt 1.6.0,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Sep 16 2014),
with
AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 3.1.22, Gcrypt 1.6.0, without AirPcap.
Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz, with 8148MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
The Wireshark dissection seems to stop at the depth of ATT protocol. To add
support for any further dissectors, the basic GATT dissection support needs to
be added.
The advantage of this would be that any further profile dissections (e.g. Heart
rate sensor, HID over GATT etc) require information gathered by dissecting
GATT. Also information from service discovery (which is carried out over GATT
protocol) is the basis for further dissection of any higher layer protocols.
To give a more specific example a capture shows the ATT Protocol "Read by Type
Response" correctly, but the Attribute value reported was not decoded. In order
to decode it properly the "Read by Type Request" for which this response
corresponds to need to be remembered as that request contains the GATT UUID of
the handle, which defines the encoding of the response received.
You are receiving this mail because:
- You are watching all bug changes.
