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-Captur
w DLTs and pseudoheaders? Or do the pcap devs update pcap/bpf.h
independently?
Any other advice to help get this request approved and the results into libpcap
would be appreciated.
[1] http://www.tcpdump.org/linktypes.html
[2]
https://github.com/greatscottgadgets/ubertooth/wiki/Bluetooth-Captures-in-P
On 02/14/2014 04:46 PM, Guy Harris wrote:
>
> What is the "nanosecond offset to pcap timestamp"? pcap-ng lets you specify
> the resolution of time stamps, and even pcap lets you, at least with newer
> versions of libpcap and Wireshark, specify nanosecond resolution with a
> different magic num
On 02/14/2014 04:50 PM, Guy Harris wrote:
>
> On Feb 14, 2014, at 4:46 PM, Guy Harris wrote:
>
>> Translating them into the style in the pages under
>> http://www.tcpdump.org/linktypes would be helpful. It avoids worrying about
>> C/C-derived-language data structure names - or anything *else*
ull requests on the GitHub repository for the Web site.
>
Sure, I will keep hosting these pages.
Chris Kilgour
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
endian definition,
given your earlier statement. Since BT itself is little-endian oriented, and
the majority of BT-sniffer users are likely Intel-based, little-endian seems
the way to go.
And by the way, thanks for the quick turnaround on the DLT allocations.
Chris Kilgour
___
