Closed tranzmatt closed 3 years ago
I build kismet on natively on the host OS and ubertooth is chirping away happily. So the deeper issue seems to be libUSB is somehow mishandling it or perhaps something like udev?
What is the output of lsusb from inside Docker?
Do you still need assistance with this issue? We will close this issue if we don't get a reply within the next month.
I'm going to close this as there hasn't been a response in a while, but please re-open this issue or open a new one if you still need assistance.
Sorry, I missed this. The issue seemed to be related to having udev system visible to the system. You need to pass /run/udev to the container.
Matt
On Thu, Feb 25, 2021 at 3:48 PM Straithe notifications@github.com wrote:
I'm going to close this as there hasn't been a response in a while, but please re-open this issue or open a new one if you still need assistance.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/greatscottgadgets/ubertooth/issues/419#issuecomment-786193272, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGTZCSDOQQI3OIHCK5Y4TTTA2ZR7ANCNFSM4S4ZA3DQ .
Thank you for the update!
Steps to reproduce
Expected behaviour
I want to see BT MACs on Kismet as detected by the Ubertooth
Expect same results from inside docker container
Actual behaviour
Tell us what happens instead
Host: $ ubertooth-util -V ubertooth git-0adf33e (user@owk5) Fri Oct 23 11:48:40 EDT 2020
$ ubertooth-rx systime=1603470444 ch=53 LAP=9e8b33 err=0 clkn=1842 clk_offset=637 s=-63 n=-55 snr=-8 systime=1603470444 ch=53 LAP=9e8b33 err=2 clkn=1874 clk_offset=628 s=-63 n=-55 snr=-8 systime=1603470444 ch= 6 LAP=9e8b33 err=2 clkn=1999 clk_offset=3744 s=-75 n=-55 snr=-20 systime=1603470444 ch=55 LAP=9e8b33 err=0 clkn=2490 clk_offset=615 s=-65 n=-55 snr=-10 systime=1603470444 ch=57 LAP=9e8b33 err=1 clkn=3106 clk_offset=602 s=-65 n=-55 snr=-10
Enter docker: $ docker exec -it kismet_server_1 bash
root@fc0dc4b6107f:/src# ubertooth-rx -V libubertooth 1.1 (git-0adf33e), libbtbb 1.0 (git-9d66440)
root@fc0dc4b6107f:/src# ubertooth-util -V ubertooth git-0adf33e (user@owk5) Fri Oct 23 11:48:40 EDT 2020
After enabling ubertooth-0 on kismet
root@fc0dc4b6107f:/src# ubertooth-rx
libUSB Error: No such device (it may have been disconnected): (-4) could not open Ubertooth device ubertooth-rx - passive Classic Bluetooth discovery/decode
root@fc0dc4b6107f:/usr/local/bin# ubertooth-util -V libUSB Error: No such device (it may have been disconnected): (-4) could not open Ubertooth device ubertooth-util - command line utility for Ubertooth Zero and Ubertooth One
Version information
Operating system: NVidia Jetpack 4.3.1 (Ubuntu Bionic 18.04)
Ubertooth tools version (ubertooth-rx -V): $ ubertooth-rx -V libubertooth 1.1 (git-0adf33e), libbtbb 1.0 (git-9d66440)
libbtbb version: $ git status HEAD detached at 2018-12-R1 nothing to commit, working tree clean
Ubertooth firmware version (ubertooth-util -v): $ ubertooth-util -v Firmware version: git-0adf33e (API:1.06)
If you are reporting a problem that involves third party software (Wireshark/Kismet/etc), please report the version here.
Output