Fix 'u_char' undeclared on musl libc

On musl libc we get build errors with 'u_char' undeclared and

```
expected expression before ')' token
205 | btbb_pcap_dump(h->pcap_file, &pcap_pkt.pc

Fix 'u_char' undeclared on musl libc

On musl libc we get build errors with 'u_char' undeclared and

```
expected expression before ')' token
205 | btbb_pcap_dump(h->pcap_file, &pcap_pkt.pcap_header, (u_char *)&pcap_pkt.bredr_bb_header);
```

This PR fixes both the issues, one of the issue is caused by another.

Signed-off-by: brahmajit das <[email protected]>

show more ...

Use `DLT_BLUETOOTH_LE_LL` for PPI rather than `DLT_USER0`.

`DLT_USER*` is intended for private use. It requires extra configuration in
tools like Wireshark to make it actually work, and causes prob

Use `DLT_BLUETOOTH_LE_LL` for PPI rather than `DLT_USER0`.

`DLT_USER*` is intended for private use. It requires extra configuration in
tools like Wireshark to make it actually work, and causes problems for
Ubertooth users in other tools (eg: secdev/scapy#1673)

I don't have the hardware for this, so I cannot test this change.

show more ...

le: handle BT 5.0 long packets

As of Bluetooth 5, LE packets can be up to 255 octets long. Do not
truncate when capturing such long packets. Note that there is still an
assert lying around in the Pc

le: handle BT 5.0 long packets

As of Bluetooth 5, LE packets can be up to 255 octets long. Do not
truncate when capturing such long packets. Note that there is still an
assert lying around in the PcapNG code, waiting to be tripped.

show more ...

Update version string setting proceedure

Package maintainers can override the git repo detection by providing
their own release version string using cmake -DRELEASE_STRING="you_version"
For all othe

Update version string setting proceedure

Package maintainers can override the git repo detection by providing
their own release version string using cmake -DRELEASE_STRING="you_version"
For all other users we check for a git repo and default to the last release
version string if none is found

show more ...

Update release string logic to check for git dir by default

log version string in cmake output

Increment SO version

Merge pull request #47 from tsvehagen/fix-pcap-magic

Fix pcap magic number for nanoseconds

Bump SO version and fix some const values

Merge pull request #49 from elli89/fix_decode

correct and simplify the btbb_decode() procedure

Tidy cmake for OS X and static/shared lib builds

Fix a couple of warnings about uint8_t bitshifting

Correct NAP extraction from 8 bits to 16 bits
- Thanks to Nemanja Savić

le: decode flags

le: parse manufacturer-specific data

le: parse remaining LE advertising types

Hat tip to @ZeroChaos- for reporting this issue.

move btbb_decode() to bluetooth_packet.c since it has no relation to btbb_piconet any more

simplify btbb_decode()

It makes no sense to iterate over CLK6 here. If CLK6 is not correct here, we are in trouble anyway.

The part which was commented checks if the channel of the packet matches t

simplify btbb_decode()

It makes no sense to iterate over CLK6 here. If CLK6 is not correct here, we are in trouble anyway.

The part which was commented checks if the channel of the packet matches the hopping pattern. This brings no benefit since when following the Ubertooth stick is only able to receive packets that match the hopping pattern.

show more ...

store clkn in the correct variable

pkt->clock is never set but used for decoding packets
remove it and use pkt->clkn instead

trim whitespaces at the end of a line

Fix pcap magic number for nanoseconds

The magic number in the pcap header should be 0xa1b23c4d for
nanosecond resolution pcap files. The previous value 0xa1b2c3d4
made wireshark show the wrong times

Fix pcap magic number for nanoseconds

The magic number in the pcap header should be 0xa1b23c4d for
nanosecond resolution pcap files. The previous value 0xa1b2c3d4
made wireshark show the wrong timestamp.

show more ...

Fixed the pcapng file with all the pcap fixes

Or bits not and

Fixed Payload present

Fixed the packet length?