You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We noticed while working with kismet that at some point location tracking during Bluetooth and BTLE packet capture was removed. We have narrowed down the breaking commit to 9193c08, which appears to take away location from generic packets.
I see device_tracker::update_common_device when passed the UCD_UPDATE_LOCATION flag appears to fetch location information, and phy_btle.cc and phy_bluetooth.cc both call this function with the appropriate flags, however that information is somehow not making it to the kismetdb logs.
Thanks,
Chris
The text was updated successfully, but these errors were encountered:
Uncommenting the two lines that were commented out in gpstracker.cc in the commit you noted ( 9193c08) restores location data for Bluetooth when exported to KML. I've minimally tested using the master branch and the latest release tag; not sure if if breaks other stuff that I haven't noticed yet.
@neil-m-a thanks for figuring that out! I've confirmed this works for me as well. I will consider opening a pull request, to me it seems like kismet would want to provide the functionality before deprecating the old method of bluetooth location. With releases being few and far between, building master has become the standard way to deploy this software.
Hi,
We noticed while working with kismet that at some point location tracking during Bluetooth and BTLE packet capture was removed. We have narrowed down the breaking commit to 9193c08, which appears to take away location from generic packets.
I see device_tracker::update_common_device when passed the UCD_UPDATE_LOCATION flag appears to fetch location information, and phy_btle.cc and phy_bluetooth.cc both call this function with the appropriate flags, however that information is somehow not making it to the kismetdb logs.
Thanks,
Chris
The text was updated successfully, but these errors were encountered: