> Could you please switch to a scheme where the state information is a
> pseudo-header that precedes the payload in the packet data? We could
> assign a LINKTYPE_BLUETOOTH_LE_LL_UBERTOOTH value for that.
Certainly. Can you point to any protocols which already implement things
this way? I find it'
> I've attached a screenshot: you can see the old version of the PPI
> header (lacks CrcInit), the USER0 DLT, and the 18 bytes of data captured
> from the air.
>
> 18 = 4 byte AA + 2 byte header + 9 byte data + 3 byte CRC
Attachment scrubbed, see
http://lacklustre.net/bluetooth/btle_breakdown.png
> >> So do LINKTYPE_BLUETOOTH_LE_LL/DLT_BLUETOOTH_LE_LL packets include the
> >> preamble octet and the CRC?
> >
> > They include the 3 octet CRC, they do not include the preamble.
>
> OK, I'll update the description on the "link-layer header types" page to note
> that.
>
> So the packet in the
Hi, I impelemented most of the BTLE support in Ubertooth.
> So do LINKTYPE_BLUETOOTH_LE_LL/DLT_BLUETOOTH_LE_LL packets include the
> preamble octet and the CRC?
They include the 3 octet CRC, they do not include the preamble.
To validate the CRC you must know a per-connection CrcInit. This value
