I've correctly created a Bluetooth Low Energy advertising packet using the GAP Service Data type (0x16). Unfortunately, Wireshark is showing this as a Malformed Packet. If I switch the data type to some other type of format (say Manufacturing Specific), the dissector works fine. But when I select the Service Data type (BLE Supplement specification V6-2, page 19 - section 1.11 Service Data) it clearly states that the Service Data format (16 bit) contains two octets followed by additional service data. From Additional debugging the problem of malformed packets seems to be that the dissector is requiring data to be in even octets - which is not a requirement of the specification. If I adjust the data enclosed within this field - wireshark does not produce a failure. asked 01 Mar '16, 11:16 DanielLSS |
One Answer:
It seems to be fixed in: https://code.wireshark.org/review/6902 (before you request it :)) Try Wireshark 2.0 or the latest. answered 07 Sep '16, 00:54 Michał Łabędzki |
If you are sure it is a bug, Wireshark bugzilla is the right place to report it, not a Q&A site.