I'd like to suggest that "struct _pcap_bluetooth_monitor_header" is too generic a name when this header only applies to the internal workings of an operating system's HCI and adapter-lifetime traffic.
There are other forms of bluetooth monitoring that are not OS-specific nor even cover HCI. For example open-source sniffers like ubertooth and gr-bluetooth capture at the RF level. It's likely that a DLT allocation request will be forthcoming for capturing bluetooth over-the-air [1]. [1] https://github.com/greatscottgadgets/ubertooth/wiki/Bluetooth-Captures-in-PCAP Chris Kilgour _______________________________________________ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
