| Bug ID |
9695
|
| Summary |
Add a shared metadata field "connection handle" to bt protocols, or add possibility to add multiple fields in one collumn
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Enhancement
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
wireshark 1.11.3 (SVN Rev Unknown from unknown)
Copyright 1998-2014 Gerald Combs <[email protected]> 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+ 3.4.2, with Cairo 1.10.2, with Pango 1.30.0, with
GLib 2.32.4, with libpcap, with libz 1.2.3.4, with POSIX capabilities (Linux),
with libnl 3, with SMI 0.4.8, with c-ares 1.7.5, with Lua 5.1, without Python,
with GnuTLS 2.12.14, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP, with
PortAudio <= V18, without AirPcap.
Running on Linux 3.2.0-58-generic, with locale en_IE.UTF-8, with libpcap
version
1.1.1, with libz 1.2.3.4, GnuTLS 2.12.14, Gcrypt 1.5.0.
Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Built using gcc 4.6.3.
--
When analyzing bluetooth communication with multiple devices, one of the best
ways to distinguish which two devices are communicating is by connection
handle. These handles are present in HCI_CMD as bthci_cmd.connection_handle,
HCI_EVT as bthci_evt.connection_handle and in acl packets as bthci_acl.chandle.
It would be great to group them as single field for all bt protocols, or
provide a mechanism that enables user to set conditions for showing a field in
a column, or assemble the info shown in a column. The second solution might be
a bit better, as connection handles are not unique across adapters.
You are receiving this mail because:
- You are watching all bug changes.