kismet
kismet copied to clipboard
kismetwireless
Bluetooth datasource not working
Using a Sena UD100 the hci comes up and appears to start correctly with no errors. However no data is actually seen by kismet.
I’ve verified the adapter is working by using the same adapter with bluelog and that utility is working fine. I’ve tried with Kismet 2019-R2 and 2020-R4, same results.
Try the latest nightly builds, other than that unfortunately I have no suggestions unless you're able to find any particular steps that cause it to fail; I have several here running on multiple platforms with no issues so I can't recreate a failure to debug it.
On Mon, Oct 19, 2020 at 10:33 AM Kyle [email protected] wrote:
Using a Sena UD100 the hci comes up and appears to start correctly with no errors. However no data is actually seen by kismet.
I’ve verified the adapter is working by using the same adapter with bluelog and that utility is working fine. I’ve tried with Kismet 2019-R2 and 2020-R4, same results.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kismetwireless/kismet/issues/313, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFKJYYZHJYYXBUSSMMY7WW3SLRE4VANCNFSM4SWHN7AQ .
No luck on nightly. I’ve also tried on 2 separate machines one in a VM the other on bare metal, same issue. The hci device is there and works with other utilities. Kismet starts the capture but no data is seen, what info can I grab that would help?
This seems related to #178.
Looks like the issue is related to how Kismet tells the bluetooth controller to start discovery. For whatever reason my UD100 is not actually going into discovery mode when entering adding a data source, this can be verified by using bluetoothctl and checking the controller state.
The fix for me
With already Kismet running (and attempting capture on hci0), enter bluetoothctl and manually start discovery, then data will start showing up in Kismet.
Tried bluez 5.50 and 5.53, same issue on both.
Ahhh, interesting! That absolutely gives me something to go on, I'll try to automate that; i've been trying to get various system to exhibit the problem without luck, that sounds like something that hopefully can be automated.
On Fri, Oct 23, 2020 at 3:29 PM Kyle [email protected] wrote:
Looks like the issue is related to how Kismet tells the bluetooth controller to start discovery. For whatever reason my UD100 is not actually going into discovery mode when entering adding a data source, this can be verified by using bluetoothctl and checking the controller state.
The fix for me With already Kismet running (and attempting capture on hci0), enter bluetoothctl and manually start discovery, then data will start showing up in Kismet.
Tried bluez 5.50 and 5.53, same issue on both.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kismetwireless/kismet/issues/313#issuecomment-715538551, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZAOCFVQL3UFV55MXT3FN3SMHKSNANCNFSM4SWHN7AQ .
