-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inedible LAP values #35
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I recently came cross your ice9-bluetooth-sniffer git repository, and I am very interested in the project you have been working on. However, I have encountered some difficulties in fully understanding the workflow and the underlying code.
I am using HackRF One and mainly I want to receive Classic Bluetooth packets and parse the LAP value. As I can see there is a dedicated function for this, where you even parse the LAP value. However I think these LAP values are wrong, or at least don't match with the actual LAP values I receive with bluetoothctl scan on command.
If I run the example command with verbose on:
./ice9-bluetooth -l -c 2427 -C 20 -w ble.pcap
I get LAPs like these:
burst 2424-0008 cfo -0,036948 deviation 0,099469 lap 5ea6b1
burst 2422-0084 cfo -0,048748 deviation 0,092935 lap 11d4fc
burst 2420-0075 cfo -0,046715 deviation 0,168837 lap 77d176
But if I run a scan on command with bluetoothctl on my machine it doesn't scan devices with MAC addresses like those.
Am I doing something wrong?
Also if two devices are connected and created a piconet (so they are in undiscoverable mode), can this device receive their Classic BT packets and parse the LAP values or only Ubertooth can do this?
Thanks!
The text was updated successfully, but these errors were encountered: