--- Begin Message ---
Hello all,
DLT_BLUETOOTH_LE_LL_WITH_PHDR was created close to a decade ago mainly to
support Bluetooth LE sniffers. It includes parameters describing sniffer RF
capture settings in addition to the BLE link layer packet. It was created
in the days of Bluetooth 4.0, when BLE wa
--- Begin Message ---
A couple more editorial comments:
In the description of the bits in the Flags field, I'd describe the 0x3000 bits
as "PDU type dependent", and, after they're listed indicate that:
For PDU types other than type 1 (auxiliary advertising), the PDU type
dependent field
--- Begin Message ---
Thanks for the feedback, your suggestions do make the specification
clearer. I edited the specification based on your suggestions, and I also
clarified the usage of integer bit fields within the Flags field.
Link to the updated version of the spec with the latest changes:
htt
--- Begin Message ---
For an advertising physical channel PDU, it appears that the PDU type is in the
least-significant 4 bits of the PDU header.
Is that not present in an auxiliary advertising packet?--- End Message ---
___
tcpdump-workers mailing list
--- Begin Message ---
The reason the extra auxiliary PDU type field is needed is that the
four-bit auxiliary PDU type is ambiguous and context-dependent for
auxiliary PDUs. See Volume 6, Part B, Section 2.3, Table 2.3. The four
least significant bits of the advertising PDU header will be 0b0111 for
