search

greatscottgadgets / ubertooth

Software, firmware, and hardware designs for Ubertooth
https://greatscottgadgets.com/ubertoothone/
GNU General Public License v2.0
1.95k stars 433 forks source link

Ubertooth & kismet build errors? #262

Closed dreyes15 closed 3 years ago

dreyes15 commented 7 years ago

I am trying to install the kismet plugin as specified in the third party instructions specifically I have run the following: however after following the steps described in the documentation when I run kismet I get the following

screen shot 2017-05-01 at 10 40 32 am

Version information

Ubuntu 16.04 Ubertooth 2017-03-R2 Kismet-2013-03-R1

dominicgs commented 7 years ago

Most of those look like permissions errors. Is this running as root? Or another user?

Has the ubertooth plugin installed anywhere? What was the output of the make install command for the plugin?

dreyes15 commented 7 years ago

That is the output running as both root and as a regular user, after running: sudo make plugins-install I receive the following output

screen shot 2017-05-02 at 6 28 13 pm

Could these errors have originated from the soft link? when I run ln -s ../ubertooth-2017-03-R2/host/kismet/plugin-ubertooth . I get the error that says it failed to create the symbolic link '/plugin-ubertooth': file exists

dreyes15 commented 7 years ago

I have kismet seeing the ubertooth one as a plugin now, I had to change the path of where the source code to kismet was it

screen shot 2017-05-02 at 6 51 15 pm

This is what I get when clicking on the plugin, which I think is the correct output?

dominicgs commented 7 years ago

That looks better. Try starting some Bluetooth devices nearby to see if you get any output?

dreyes15 commented 7 years ago

There we go I am getting some packets now, thanks!

screen shot 2017-05-02 at 8 08 10 pm
dreyes15 commented 7 years ago

Hmm there seems to be another issue It seems after exiting the program the terminal says I have some packets, but upon opening the pcap file it says no packets collected, perhaps now it's a kismet issue?

dreyes15 commented 7 years ago
screen shot 2017-05-02 at 8 20 42 pm

Here is a photo of what I output

dominicgs commented 7 years ago

Bluetooth has a packet scrambler (known as data whitening in the BT spec) that we can't decode when we first receive packets, we need more information about them. Even when we can decode it, we can't always be sure of the size/modulation of the data section of the packet, so that can often be invalid or left out of the pcap.

It looks like in this case we were never able to unwhiten packet data.

dreyes15 commented 7 years ago

Ok, so in this case it isn't necessarily a Kismet or Ubertooth problem. Hmmm should kismet be generating a pcapbtbb file in addition to a pcap file? It seems mine is not doing that

dominicgs commented 7 years ago

I believe it should only produce one output file for Ubertooth captures.

dreyes15 commented 7 years ago

Hmm ok well apart from the packets never being unwhiten it seems like all the issues I was having is fixed.

Bella721 commented 6 years ago

When we use kismet to capture package, why it can't create pacpbtbb files?

mikeryan commented 3 years ago

Legacy Kismet is no longer supported by this project.