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

[bugzilla-daemon@xxxxxxxxxxxxx]

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


guy@xxxxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |paolo.abeni@xxxxxxxx
           Platform|PC                          |All




------- Comment #2 from guy@xxxxxxxxxxxx  2007-08-18 20:59 GMT -------
This will only work if the pcap-format files *have* a direction indicator in
them.  Currently, it doesn't appear that the top-of-tree version of libpcap
puts a direction indicator into the file; if Wireshark is going to expect one
to be there, then libpcap needs to be changed to put one there.

>From looking at bt_read_linux() in libpcap's pcap-bt-linux.c, it appears that
it does get a direction indication:

        /* get direction and timestamp*/
        cmsg = CMSG_FIRSTHDR(&msg);
        while (cmsg) {
                int in;
                switch (cmsg->cmsg_type) {
                        case HCI_CMSG_DIR:
                                in = *((int *) CMSG_DATA(cmsg));
                                break;
                        case HCI_CMSG_TSTAMP:
                                pkth.ts = *((struct timeval *)
CMSG_DATA(cmsg));
                                break;
                }
                cmsg = CMSG_NXTHDR(&msg, cmsg);
        }

Can the value of "in" be used to set a flag in the header?

And should the direction be put in the H4 header, or put into a separate field
added before the header?


-- 
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.