Kismet Wireless

Kismet Forums

 

Posted by:sideburns
Subject:Identifying the chipset
Date:06:33:03 05/01/2010

> > I'm trying to get kismet running on a Toshiba laptop with a built in WiFi card. One of my two problems is finding out just what chipset I have. I know it's Intel but kismet isn't happy with just that.
>
> Install a modern kismet version and it figures out the driver for you.

I'm using kismet-0.0.2009.06.R1-1.fc12.i686, installed from the Fedora repository by yum. Is that modern enough for you?

> Otherwise, dmesg, hw specs for your device, etc.

After turning on the card, dmesg | grep wlan0 reports this:

ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: authenticate with AP 00:11:50:26:33:3b
wlan0: authenticated
wlan0: associate with AP 00:11:50:26:33:3b
wlan0: RX AssocResp from 00:11:50:26:33:3b (capab=0x601 status=0 aid=10)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

>
> > The other is SELinux related, and there's already a bug report on it.
>
> There is? I know nothing of this. Kismet doesn't really have any interaction with selinux.
>

Searching bugzilla.redhat.com for kismet reports three open kismet bugs:
https://bugzilla.redhat.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=Fedora&content=kismet

Two of them reference SELInux. Granted, they're both of the form "Why is SELinux blocking kismet?" and the responses tend toward, "Damned if I know!"

Testing, SELinux is still complaining about consolehelper-g and kismetserver is stopping unexpectedly.


Reply to this message