Ask Your Question

Revision history [back]

Custom bluetooth transport implementation


I work with device that implements HCI interface over vendor specific USB protocol. I would be able to create dissector plugin if function:

static bluetooth_data_t *
dissect_bluetooth_common(tvbuff_t *tvb, packet_info *pinfo, proto_tree *tree)

...was not private to packet-bluetooth.c.

Currently supported transports are coupled with bluetooth protocol inside function proto_reg_handoff_bluetooth() (and some static functions called inside) and use disset_bluetooth_common() that I would also like to use.

I wander if exporting function dissect_bluetooth_common() would be a problem or there is other recommended way to create data of type bluetooth_data_t needed later for actual HCI command/event dissectors?

Or maybe I need to integrate some strange protocol into packet-bluetooth.c?

Thanks for advise.