1Kismet Win32 Readme
2
31. Requirements
42. Quick Start
52. Configuring Kismet
63. Building Kismet
7
8
91. Requirements
10
11    The Windows version of kismet requires Windows 2000, Windows XP (32/64bit),
12    Windows Server 2003 (32/64bit), or Vista (32bit).
13
14    At this time, only two kinds of sources are supported:
15
16    * Drones
17    * The AirPcap USB capture adapter from CACE Technologies
18      (http://www.cacetech.com/products/airpcap.htm)
19
20    THE AIRPCAP ADAPTER IS THE ONLY WAY FOR KISMET TO CAPTURE LIVE 802.11
21    TRAFFIC UNDER WINDOWS. NO OTHER CARDS ARE SUPPORTED. THIS LIMITATION IS
22    CAUSED BY THE LACK OF SNIFFER-MODE CAPABLE DRIVERS ON WINDOWS; THE
23    AIRPCAP ADAPTER CIRCUMVENTS THIS LIMITATION THROUGH THE USE OF A SPECIALIZED
24    CUSTOM DRIVER.
25
26    If multiple AirPcap adapters are plugged in, Kismet is able to take
27    advantage of them to listen on more than one channel simultaneously.
28
292. Quick Start
30
31    The easiest way to run Kismet on Windows is downloading and running the
32    installer executable available at
33
34        http://www.cacetech.com/support/downloads.htm
35
36    The installer creates an entry under "All Programs" with the following
37    items:
38
39    * Kismet: the program executable.
40    * Kismet Configuration Console: the GUI that can be used to configure the
41      program behavior.
42    * Command Line Prompt: this opens a dos console in the kismet installation
43      folder; advanced users can use this to manually run kismet_server.exe,
44      kismet_client.exe or kismet_drone.exe.
45    * Kismet Logs Folder: this shourtcut allows access to the files that kismet
46      produces when it runs. The folder will be empty until Kismet is run at
47      least once.
48
49    After the installer is done, just click on "Kismet", and the program will
50    start with all the available AirPcap adapters as sources.
51
522. Configuring Kismet
53
54    Run the Kismet Configuration Console (start -> All Programs -> Kismet ->
55    Kismet Configuration Console). You will have the option to configure:
56
57    * the local sources Kismet will use for packet capture.
58    * the list of drones Kismet will try to connect to for remote monitoring.
59    * if kismet will log information about the discovered networks to disk.
60
61    Additionally, you will be able to edit the kismet.conf, kismet_ui.conf and
62    kismet_drone.conf files to tweak the program advanced settings. For a
63    reference on these three configuration files, please refer to the program
64    manual.
65
663. Building Kismet
67
68    Requirements:
69
70    * the Cygwin Unix emulation environment. Install it from
71      http://www.cygwin.com/, and remember to include the development packages
72      (gcc and make at least).
73    * the kismet sources, from http://kismetwireless.net/download.shtml
74    * the AirPcap developer's pack, from
75      http://www.cacetech.com/support/downloads.htm
76
77    IMPORTANT: unpack the AirPcap developer's pack INSIDE the folder with the
78    Kismet sources. You want the AirPcap_Devpack_XXX folder to be in the same
79    folder of the Kismet makefile. The reason is that Cygwin appears to have a
80    bug which prevents proper linking if the devpack is not in the same
81    directory that Kismet is compiled in. If kismet_server.exe instantly exits
82    with no output, it is typically indicative of a linkage path problem.
83
84    Instructions:
85
86    a. run the following configure line:
87       ./configure --enable-airpcap --with-airpcap-devpack=<devpack_location>
88       Where <devpack_location> is the name of the AirPcap Developer's pack
89       folder, containing WinPcap and AirPcap
90    b. Build Kismet by typing 'make'
91
92