Kismet Wireless

Kismet Forums


Posted by:jmiller
Subject:Intel iwl4965 Adapter with iwlwifi drivers
Date:18:37:24 24/08/2007

> > I've got an Intel 4965 wifi adapter with iwlwifi based drivers. It works fine with the ipw3945 sourcetype if I put it into monitor mode manually first:
> >
> > ifconfig wlan0 down
> > iwconfig wlan0 mode monitor
> > ifconfig wlan0 up
> >
> > I noticed in another post that some needed to do this and others didn't for the iwlwifi based 3945 drivers. Is there something else that needs to be done to allow Kismet to handle this itself? Not a big deal but something that should probably get addressed at some point.
> This shouldn't be needed. Kismet has, for a while, attempted to configure the device up, then bring it down, and attempt to configure it while down before declaring failure.

I get this if I don't put the interface in monitor mode first:

Source 0 (Kismet): Enabling monitor mode for ipw3945 source interface wlan0 channel 6...
FATAL: Failed to set monitor mode: Device or resource busy. This usually means your drivers either do not support monitor mode, or use a different mechanism for getting to it. Make sure you have a version of your drivers that support monitor mode, and consult the troubleshooting section of the README.

> Do you have any 11n equipment which you can test? I'd be very very interested in a pcap of both a beaconing 11n AP, and in the data of an 11n network, assuming this card can detect it. It'd be best to get these as a `tcpdump -i foo -s 0 -w log.pcap', instead of Kismet output.

I don't have a 802.11n AP yet. At some point probably but I'm guessing I'll be too late to help :)

> >
> > Edit:
> > I suppose versions would help :)
> >
> > Kismet: 2007.01.1b
> I'll add an iwl4965 alias in the kismet-stable-svn code right now, if you have a chance to test it. It should work w/ no preconfig in the shell, just run Kismet, if that doesn't work, let me know.
> [edit - iwl4965 source committed]

Well, I grabbed the source and made the very bad decision to see what would happen if I tried to just run Kismet before installing. It completely locked the machine up so I'll have to give it another shot tonight when I have physical access to it.

> -m

Reply to this message