I recently moved all my work involving Bluetooth in wireshark to a windows 10 virtual machine. I fixed an initial error with encapsulation where I added user 10 DLT = 157 with btle as the protocol, which was the same as I did before and it worked fine. However this time, while I get no errors, the layout is different and it is missing a lot of info like source and destination, payload, any handle values. The type of packets displayed are "Empty PDU", "Control Opcode: LL_START_ENC_RSP", and "L2CAP Fragment". Please forgive me if any terminology used here is incorrect, I am still new to wireshark and learning. Any help with getting this back to the normal layout would be greatly appreciated. asked 11 Dec '15, 12:50  nearl002 |
One Answer:
It seems to be a bug, please fill the bug on Bugzilla. DLT_USER are not currently supported by centralised "bluetooth" dissector where all additional/useful operations done or data have been stored. answered 12 Dec '15, 03:11  Michał Łabędzki |
Thank you for looking into it.
I am encountering the same series of messages.
Was a bug report ever created? If so, did you receive an answer? Or an estimate of when it would be addressed?
Thanks in advance.
As I remember there is no bug request yet (and no sample capture file) - please create. To speed up work on this I need capture file, this issue in on my TODO list, but it is not ready right now.