-
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
BT Classic and BLE Sniffing does not record RSSI of packet. #18
Labels
enhancement
New feature or request
Comments
Hi yes, this is something I plan on adding in the near future. We already collect that info from our automatic gain control (AGC) blocks, so it's really just a matter of stuffing it in the correct place in the packet header. |
Wow thank you! I'll see if I can get it going myself. If I do, I'll be sure to share my findings. Unfortunately, I am pretty new to packet sniffing but I will do my best. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First off, amazing code. Great to use and very easy to get going. Was wondering if this addition could be made.
Using a Bladerf 2.0 device to sniff BLE packets. Successfully able grab packet information such as advertising address, angle of arrival, time of arrival, etc. However, the RSSI recording seems to be missing from the packet information delivered to wireshark. I know that this can be hardware or even protocol dependent, but I believe that Bladerf has the capability to record these values. I am hoping to be able to record the RSSI from packets sent advertising and data channels.
I hope to use this value to approximate the location of a device. Please let me know if this is something that is possible to be added. Thanks!
The text was updated successfully, but these errors were encountered: