Kismet Ruby Scripts for MySQL - Updated

I was trying to find an easier way to track clients back to users. The skism script works, but I felt I needed something more (plus I wanted to get back to Ruby programming). I noticed that dragorn included some Ruby scripts with the kismet source. His examples were for SQLite, but I wanted to use MySQL, so...here's what I have so far:

Create MySQL Tables
Grab and Insert Client Information
Grab and Insert BSSID Information
Grab and Insert SSID Information

Here's one file to do all the inserts:
Grab and Insert CLIENT,BSSID,SSID Information

Feel free to use these and update as you see fit for your environment. I'm hoping to do more in the coming weeks.

Kismet + SCCM = skism

Here's a python script that will connect to your Kismet server, grab client MAC addresses and send them off to Microsoft's SCCM to try to match them to usernames.

skism

The coding is probably pretty rough, but I'm not really a coder, so...

If anyone finds this useful, let me know.

Looks Like I was Wrong...

...Thanks to Jeremy.

No, really, thanks Jeremy. I was pulling my hair out until he posted this:

One thing you might need to check is your wireless config file on the router located at:
/etc/config/wireless

The following settings for that work for me:
config wifi-device wlan0
option type mac80211
option channel 5
option macaddr xx:xx:xx:xx:xx:xx (this is yours, not mine)

config wifi-iface
option device wlan0
option network lan
option mode monitor

That did the trick! So, it looks like the build does still work with the above modifications to the wireless config file. 

Broadcom issues with newer OpenWrt trunk

I've been trying to compile the new svn of OpenWrt and wireless seems to be a no-go for the WRT54GL. Then I ran across the following on the OpenWrt site:

Note: The brcm47xx still won't work for those of you needing broadcom wifi, stick to brcm-2.4. We will tell you when it does work.

After much testing and corresponding failures, I'm thinking this is not going to work in the near future, especially for using Kismet. So, I kept an older version of the svn in a separate directory and have backed that up for use with building Kismet. The total structure is around 2Gb, so it is rather large. Not sure where I can host that data yet, but if anyone wants an older version that will build for use with Kismet (this is the same directory that was used to build the images on this site), let me know and I'll try to find a place to put them.

Kismet-Newcore OpenWRT Cross-Compile (UPDATED Makefile)

The new version of kismet moves some lines out of the Makefile and into the Makefile.inc which causes the original instructions to fail. Here's the updated step:

#Edit Kismet Makefile.inc

cd ~/trunk/build_dir/target-mipsel_uClibc-0.9.30.1/kismet-2010-01-R1
vi Makefile.inc


-Change the following flags:

CFLAGS = -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/usr/include -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/include -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/target-mipsel_uClibc-0.9.30.1/usr/include -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/target-mipsel_uClibc-0.9.30.1/usr/include/uClibc++ -I/include -I/usr/include/ncurses

CXXFLAGS = -Wall -Os -pipe -mips32 -mtune=mips32 -funit-at-a-time -fhonour-copts -msoft-float -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/target-mipsel_uClibc-0.9.30.1/usr/include/uClibc++ -fno-builtin -fno-rtti -nostdinc++

CPPFLAGS = -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/usr/include -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/include -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/target-mipsel_uClibc-0.9.30.1/usr/include -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/target-mipsel_uClibc-0.9.30.1/usr/include/uClibc++ -I/include -I/usr/include/ncurses


-To: (You are adding the "+" before the "=")

CFLAGS += -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/usr/include -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/include -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/target-mipsel_uClibc-0.9.30.1/usr/include -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/target-mipsel_uClibc-0.9.30.1/usr/include/uClibc++ -I/include -I/usr/include/ncurses

CXXFLAGS += -Wall -Os -pipe -mips32 -mtune=mips32 -funit-at-a-time -fhonour-copts -msoft-float -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/target-mipsel_uClibc-0.9.30.1/usr/include/uClibc++ -fno-builtin -fno-rtti -nostdinc++

CPPFLAGS += -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/usr/include -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/include -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/target-mipsel_uClibc-0.9.30.1/usr/include -I/home/mike/openwrt/trunk/staging_dir/target-mipsel_uClibc-0.9.30.1/target-mipsel_uClibc-0.9.30.1/usr/include/uClibc++ -I/include -I/usr/include/ncurses


Kismet init

Here's a script to add to /etc/init.d that will start kismet_drone on router startup. Put this code in a file called "kismet_drone" (or whatever you want to call it):

#!/bin/sh /etc/rc.common
# Copyright (C) 2008 OpenWrt.org

START=65
PROG=/usr/bin/kismet_drone
start() {
        $PROG
}

stop() {
        killall kismet_drone
}

 Once this is done do the following:

cd /etc/rc.d
ln -s ../init.d/kismet_drone S65kismet_drone

Now kismet_drone will start whenever the router is restarted. The "stop" command doesn't work very well, I'm still working on fixing that issue.

Flashing the Flashed

If your router is already flashed with DD-WRT, the easiest way to get the drone working is to use SCP and MTD. Here's the quick 'n' dirty:

#SCP .trx file to router
scp filename.trx root@routerip:/tmp/

#SSH into router
ssh -lroot routerip

#Start the flash
cd /tmp
mtd -r write filename.trx linux

At this point the router will begin the flash process. Be patient, don't jump the gun and pull the plug on the router (potential brickage might follow). This usually takes 3-5 minutes, just wait for the router to reboot, then you will have to telnet back in and do the configure thing all over again.