Installing kismet for ubertooth

Last time, I got the ubertooth tools installed and made sure that the real-time spectrum analysis was working.  Now, I want to install the kismet plugin and wireshark plugin so that I can sniff bluetooth traffic.
I started by following the kismet guide on the getting started page.  I already had some of the packages installed, but that was ok.  I downloaded the latest kismet manually rather than using wget.  Then I followed the directions.  kistmet.conf was in /etc/kismet on my kali 1.04 machine.

I haven't used kismet much at all, so the next step was to read the readme for the ubertooth plugin.  The readme in in the ubertooth tools source, specifically ./ubertooth-2014-02-R2/host/kismet/plugin-ubertooth.

Kismet-Ubertooth

0.  NOT COMPLETE

1.  What is Kismet-Ubertooth
2.  Caveats
3.  Compiling
4.  Installing
5.  Using

0.  NOT COMPLETE

*** THIS CODE IS CURRENTLY NOT COMPLETE ***

What it does:

* Control one (and only one) Ubertooth Zero or Ubertooth One
* Monitor one Bluetooth channel
* Display the LAP of Bluetooth packets
* Determine and display the UAP of Bluetooth packets
* Log to pcap file

What it should be able to do in the future:

* Determine the clock of a target piconets
* Hop along with a target piconet through all channels
* Control more than one Ubertooth Zero or Ubertooth One
* Read pcap files
* Print debug info about packets

1.  What is Kismet-Ubertooth

    Kismet-Ubertooth is a Kismet plugin which provides Bluetooth support in
    Kismet.  It relies on the Bluetooth baseband library, libbtbb
    (http://libbtbb.sourceforge.net/). Kismet-Ubertooth performs passive
    monitoring of Bluetooth networks using the Ubertooth platform
    (http://ubertooth.sourceforge.net/).

    It CAN NOT BE USED with 802.11 wi-fi cards, it is a completely different
    protocol.  If you do not have an Ubertooth but have a Bluetooth adapter,
    try the btscan plugin instead.  It performs active scanning of discoverable
    Bluetooth devices.  Better yet, build yourself an Ubertooth One.

    Kismet-Ubertooth defines the decoders, loggers, and UI controls for
    Bluetooth networks in a common fashion, and supports reading and writing
    Bluetooth baseband pcap files.

    The Bluetooth baseband protocol is the air interface of Bluetooth.  It
    operates in the 2.4 GHz ISM band.  There is a separate interface known as
    HCI (Host Controller Interface) that operates between a host computer and
    an attached Bluetooth adapter.  Kismet-Ubertooth uses special hardware to
    directly access the baseband layer.  It does not operate at the HCI layer.
    Try hcidump if you want to access HCI.

2.  Caveats

    This code is currently only partially developed and may not provide full
    functionality.

    This code has only been tested on Linux.  This code MAY work on other
    platforms, but currently it is only developed with Linux as a target.

3.  Compiling

    Compiling the Kismet-Ubertooth plugin requires the Kismet source be
    installed and configured.  The libbtbb library (0.5 or higher) and libusb
    (1.0 or higher) must also be installed.

    By default, Kismet-Ubertooth expects the Kismet source to be in
    /usr/src/kismet; this can be overridden by setting the KIS_SRC_DIR
    environment variable:

        cd plugin-ubertooth
        KIS_SRC_DIR=/home/foo/src/kismet make

4.  Installing

    Kismet plugins may be installed system-wide in the plugins directory (by
    default, /usr/local/lib/kismet/) or in the users home directory
    (~/.kismet/plugins).

    To install in the system-wide directory:

        cd plugin-ubertooth
        KIS_SRC_DIR=/home/foo/src/kismet make install

    Plugins can be installed in the current users home directory with:

        cd plugin-ubertooth
        make userinstall

5.  Using

    Once the plugin is loaded, Kismet will automatically understand and
    decode pcap files with the Bluetooth link data.

    To capture from an Ubertooth Zero or Ubertooth One, plug in the USB device,
    and define a capture source in Kismet using the interface 'ubertooth'.  The
    device will be automatically detected.

    If you have multiple Ubertooth devices connected, Kismet-Ubertooth uses the
    first one it finds.  Kismet-Ubertooth currently is not capable of using

The editor is acting pretty crazy now, so this post is done!

    multiple Ubertooth devices simultaneously.
    To enable pcap logging, the logfile must be turned on by adding
    'pcapbtbb' to the logtypes= line of the kismet.conf.





So after that, I started kismet.  That started the server, and eventually it asked for a new interface.  I typed in "ubertooth" and gave it the descriptive name "ubertooth".  After that, kistmet started listening.

Then, I had my table search for devices.  If things work properly, I should see lots of packets with LAP 0x9e8b33.

Kismet captured 9e8b33!