| Bug ID |
8536
|
| Summary |
Bluetooth: Fix unrecognised CID session payload
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
SVN
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 10491 [details]
Example AVRCP logs
Build Information:
TShark 1.9.2 (SVN Rev Unknown from unknown)
Copyright 1998-2013 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 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.4.0-PRE-GIT_2013_03_25, with libz 1.2.3.4.
Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Built using gcc 4.6.3.
--
When there are two L2CAP session using the same DCID,
second session can override data from first session, then in the
first session DCID payload may be unrecognised.
Patch uses disconnect information to avoid unexpected override.
Example:
1. See frames: 34 (CID=0x5B) and 36 (CID=0x40)
2. See frames: 76 (CID=0x5C) and 78 (CID=0x40)
3. Make frame 66 "Ignored"
4. Frames 76, 78 are unrecognised - this is ok :)
5. See frame 34 - unexpected unrecognised - bug.
You are receiving this mail because:
- You are watching all bug changes.