kismet Almost there Options

[davidspitzer]

followed the faqs using kathrin and a ambicom 1100 card -- works great conecting to the internet. Here is my config in kismet and i get a unkown capture source type Prism 2 -- kismet site says the ambicom is a prism 2 -- anyone get this to work and how?

kismet.conf -----[----] 18 L:[ 7+15 22/329] *(738 /12952b)= 0 48 0x30--v>+version=2004.03.devel.a

# Name of server (Purely for organiational purposes)
servername=Kismet

# User to setid to (should be your normal user)
suiduser=kismetuser

# Sources are defined as:
# source=cardtype,interface,name[,initialchannel]
# Card types and required drivers are listed in the README.
# The initial channel is optional, if hopping is not enabled it can be used
# to set the channel the interface listens on.
# source=cisco,eth0,ciscosource
# Other common source configs:
source=prism2,wlan0,prism2source
# source=hostap,wlan1,hostapsource
# source=prism2_avs,wlan0,newprism2source
# source=orinoco,eth0,orinocosource
# An example source line with an initial channel:
# source=orinoco,eth0,silver,11

# Comma-separated list of sources to enable. This is only needed if you defined
Save 3Mark 4Replac Move 7Search

[rgrep]

now it sees the card but says the resource is busy with an ioctl error

I had this problem too. It never happened when I started Kismet within range of my home AP, but if I was out somewhere it would refuse to start. If I kept trying to run Kismet then eventually it would start. The exact error message was:

CODE

FATAL: channel get ioctl failed 16:Device or resource busy

I assume it only happens when you're outside the range of an AP because the card is busy waiting for something to associate with.

I've fixed the problem now by switching drivers from orinoco to hostap. I have a Linksys WCF12 which is Prism 2 (or Prism 3?) and with the default settings in pdaXrom it uses these modules:

CODE

# lsmod
Module                  Size  Used by    Tainted: P
orinoco_cs              4472   1
orinoco                35028   0  [orinoco_cs]
hermes                  4592   0  [orinoco_cs orinoco]

...

I'm not sure why the pdaXrom developers decided to only enable the orinoco driver (comments guys?) but it appears that's the only one it will ever use. For Prism based cards there's no need to use orinoco, especially since hostap is apparently better (and I'm hoping it will let me set my Zaurus up as an Access Point). The file you need to edit to switch drivers is /etc/pcmcia/hermes.conf. I added these lines near the top of the file:

CODE

device "hostap_cs"
  class "hermes"
  module "hostap", "hostap_cs"

Then find the definition for your card (further down in that file) and change the "orinoco_cs" reference to "hostap_cs". The definition for my card nows looks like this:

CODE

card "Linksys CompactFlash Wireless Card"
  version "Linksys", "Wireless CompactFlash Card"
  bind "hostap_cs"

(If you're not sure which entry is for your card, use 'cardctl ident' and search in /etc/pcmcia/hermes.conf for the "product info" it reports.

After editing /etc/pcmcia/hermes.conf, eject your card and restart the PCMCIA services:

CODE

cardctl eject 0
<remove card>
/etc/rc.d/init.d/pcmcia restart
<insert card>

You can test if it's worked by running lsmod again:

CODE

# lsmod
Module                  Size  Used by    Tainted: P
hostap_cs              45896   1
hostap                 85568   0  [hostap_cs]
...

You'll now have to modify your kismet.conf and change the source line. I use:

CODE

source=hostap,wlan0,hostapsource

(NB: Don't bother trying to use the prism2 source examples in kismet.conf, they aren't valid cardtype entries any more - see http://www.kismetwireless.net/documentation.shtml for the full list)