Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 1751] New: Direction info missing for Bluetooth H4 captures in pcap-format

[bugzilla-daemon@xxxxxxxxxxxxx]

http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1751

           Summary: Direction info missing for Bluetooth H4 captures in
                    pcap-format
           Product: Wireshark
           Version: SVN
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: allan.m@xxxxxxxxxxxxxx


Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
There is no information about the packet direction in Bluetooth HCI captures in
pcap format (WTAP_ENCAP_BLUETOOTH_H4). The result is that dissectors for higher
Bluetooth layers (e.g. L2CAP) do not work properly because the ingoing and
outgoing packets can not be distinguised.

A solution could be to use the upper most bit of the H4 packet type field (1
byte) that follows the pcap packet header. The H4 packet type can only take
values from 1 to 4, i.e. the highest bit would never be used for the packet
type but could instead be used for the direction (0: sent/host->controller, 1:
received/controller->host). I.e. my proposal is to shrink the packet type field
from 8 to 7 bits and use the last bit for direction info.

Old capture files that does not follow this format would still be
compatible/readable with wireshark (with same dissecting problems as today of
course).


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.