Dutch

The gear used for the site survey was :
Dell C600 laptop with an Atheros based 802.11b/g PCCard WiFi nic.
No external antenna.
A Holux GM210 USB GPS puck.
Kismet running under Debian Linux.
Laptop placed in a Targus PC Backpack, with the PC card pointing up. GPS Puck placed under one shoulderstrap.

Kismet had been configured to only scan channels 1, 6, 11, 13, with a 4 channels Page Ranking second scan time. (kismet.conf, channelvelocity and sourcechannels statements)
Kismet had been configured to only detect and track the MAC adresses in use at the school, or actually only detect and track the OUI of the equipment that the school uses. In this case Zyxel gear, filtered in kismet.conf with the filtertracker statement - filter_tracker=BSSID(00:A0:0C:C5:8F:00:00/FF:FF:FF:FF:00:00).
These parameters had been checked out in advance, i.e. which channels and which MAC's that the schools WiFi network utilized.

Kismet had also been configured to speak out detected network SSID's as well as sounding off everytime kismet detected a packet. (kismet_ui.conf file, sound, sound_new, sound_traffic, and speech parameters).



After following the route mapped out on the Google Earth picture, I took the resulting kismet.xml, kismet.gps, and kismet.csv files, to post process into a Google Earth kml file.
The first step is to run the php script. In the example below the php engine is installed in \program files\php\, the kismetfiles are in \kismetdata\ and the php script is also in \kismetdata\

Open a command prompt on your windows box.
Enter the following commandlines :

cd \kismetdata<enter>
"\program files\php\php.exe" -f kismet-to-kml.php kismet kmz<enter>

The first command changes to the folder containing the kismet.gps, kismet.xml, kismet.csv and the php script files
The second command executes the PHP5 engine, telling it to compile and run the kismet-to-kml script file, with the filename (without any suffix) of the kismet.gps and kismet.xml files, and to output both a kml and and zipped kmz file.

Please note that if the .gps file contains errors, such as missing the closing </gps-run> tag or having malformed <gps-point=........> lines, there will be warnings and errors.
Remember that kismet .csv, and .xml files are written afresh at every data cycle, but .gps files are appended to. If you didn't exit kismet properly, then chances are high, that the .gps file will contain a malformed <gps-point=....> line and missing the </gps-run>.
Just open the .gps file in any texteditor that can handle large files, move to the bottom of the file, delete the erroneous <gps-point=...> line and add a closing </gps-run> tag on the last line.

After it has churned away for a bit (1½ min for the 24 networks and 5 Mb data in this example), there will be a kismet.kml and a kismet.kmz file in the \kismetdata\ folder.

Doubleclick the kismet.kmz file to open it in Google Earth. Google Earth will zoom to the location of the first AP, and show the icons for the detected AP's.
They will be way off, as the .xml file only contains the locations coordinates from when Kismet first detected the AP and when it last detected the AP.
Untill I get the the time to change the php script, we need to do some hand editing, in order to get the program to show the location where Kismet had the best signal of the AP, which is as close to the actual location we can get, without doing triangulation.
Enter the kismet.csv file. The last coordinate pair in each record here, is the location where Kismet detected the highest signal level.

Go through each displayed accesspoint in the My Places window in Google Earth, rightclicking the Access point, select Edit, and then click the Advanced checkmark, and then the Location tab, put in the corresponding Lat/Lon coodinates for each AP, then click apply.

Now the icons for the detected AP's will be more correctly placed.

Attached Images

newuvt-wl2.jpg (48.3 KB, 823 views)