README
1Kismet-Dot15d4
2
30. NOT COMPLETE
4
51. What is Kismet-Dot15d4
62. Caveats
73. Compiling
84. Installing
95. Using
10
110. NOT COMPLETE
12
13*** THIS CODE IS CURRENTLY NOT COMPLETE ***
14
15Unless you're in contact with me and are helping develop it, it's not likely
16to do what you want. What it CAN do, currently:
17
18* Drive the AVR RAVEN
19* Drive a Linux-Serialdev device via userspace (should work on any platform)
20* Read pcap files
21* Print debug info about packets
22* Log to PCAP file
23* Do VERY basic 802.15.4 decoding
24
251. What is Kismet-Dot15d4
26
27 Kismet-Dot15d4 is a Kismet plugin which provides 802.15.4 support in
28 Kismet. 802.15.4 is a low-power network protocol for sensors, control,
29 and other "mote" applications, and is the underpinning of Zigbee, 6pan,
30 etc.
31
32 (Some) Driver support is included for the AVR USB RAVEN board,
33 available here:
34 http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=ATAVRRZUSBSTICK-ND
35
36 This driver works only under Linux.
37
38 Much more complete (and multiplatform) support is included for devices
39 based on the Linux-Serialdev firmware. This is a firmware which allows
40 an 802.15.4 device to be connected via a serial port.
41
42 Notable devices which support this firmware include the Redbee devices
43 (available from http://redwirellc.com/), and devices based on them,
44 such as the Quahogcon 2010 conference badge and likely the Ninja
45 Networks 2010 Defcon badge. These devices MUST BE FLASHED to use the
46 Linux-Serialdev firmware, firmware and information available at:
47 http://mc1322x.devl.org/
48
49 It CAN NOT BE USED with 802.11 wi-fi cards, it is a completely different
50 protocol.
51
52 Kismet-Dot15d4 defines the decoders, loggers, and UI controls for
53 802.15.4 networks in a common fashion, and supports reading and writing
54 IEEE802.15.4 pcap files.
55
562. Caveats
57
58 This code is currently only partially developed and may not provide full
59 functionality.
60
61 The Raven code implements a user-space driver using Libusb. Sometimes
62 things go stupid and the card or the server fall down during a sync
63 problem.
64
653. Compiling
66
67 Compiling the Kismet-Dot15d4 plugin requires the Kismet source be installed
68 and configured.
69
70 By default, Kismet-Dot15d4 expects the Kismet source to be in
71 /usr/src/kismet; this can be overridden by setting the
72 KIS_SRC_DIR environment variable:
73
74 cd plugin-dot15d4/
75 KIS_SRC_DIR=/home/foo/src/kismet make
76
77 For Raven support, the LibUSB library (and development headers, most
78 likely called libusb-devel by your distribution) is required.
79
804. Installing
81
82 Kismet plugins may be installed system-wide in the plugins directory (by
83 default, /usr/local/lib/kismet/) or in the users home directory
84 (~/.kismet/plugins)
85
86 The default installation path can be overridden with the KIS_DEST_DIR
87 variable if you have not installed Kismet in the default location and
88 wish to install the plugin in the system-wide plugins directory:
89 cd plugin-ptw
90 KIS_DEST_DIR=/usr make install
91
92 Plugins can be installed in the current users home directory with:
93 cd plugin-ptw
94 make userinstall
95
965. Using
97
98 Once the plugin is loaded, Kismet will automatically understand and
99 decode pcap files with the IEEE802.15.4 link data.
100
101 To capture from an AVR RAVEN, plug in the USB device, and define a
102 capture source in Kismet using the interface 'raven'. The device will
103 be automatically detected:
104 ncsource=raven
105
106 To monitor with multiple Raven devices at once, each raven must have a
107 USB device ID specified with the 'usbdev' source option. The definition
108 of the usb device ID depends on the operating system, in Linux it is a
109 number incremented for each device and shown in 'lsusb' and 'dmesg'
110 ncsource=raven:usbdev=...
111
112 To capture with a Linux-Serialdev device, plug in the usb device, and
113 define a capture source for d15d4serial with a device= option pointing
114 to the USB serial interface. For redbee-based devices, this will be the
115 SECOND serial device registered:
116 ncsource=d15d4serial:device=/dev/ttyUSB1
117
118 To enable pcap logging, the logfile must be turned on by adding
119 'pcap15d4' to the logtypes= line of the kismet.conf.
120
121