Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware 9.x, Knoppix, Damn Small Linux, RedHat.
Posts: 465
Rep:
Kismet FATAL Error
Hi, I would like some help cause Im getting this error when I run kismet as user.:
I have a LinkSys Wireless B 2.4 GHz USB 802.11 B
Server options: none
Client options: none
Starting server...
Waiting for server to start before startuing UI...
Will drop privs to username (1000) gid 100
No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Enabling channel splitting.
NOTICE: Disabling channel hopping, no enabled sources are able to change channel.
Source 0 (ciscosource): Enabling monitor mode for cisco source interface eth0 channel 6...
FATAL: Unable to open cisco control file '/proc/driver/aironet/eth0/Config' 2:No such file or directory
If it's WUSB11 it uses the Atmel driver or if it's WUSB11 ver 2.5 it uses the Linux-wlan-ng driver. It looks like you're using cisco as source which is incorrect.
Chipsets known to NOT WORK:
Intel Centrino - Intel has recently released linux-native drivers for
Centrino, but they don't support rfmon.
Broadcom - No linux drivers, only useable with ndiswrapper or
linuxant wrappers around windows drivers.
Airport Extreme - Really a Broadcom, with no rfmon in the OSX drivers.
Atmel - The USB firmware has no rfmon feature. The pcmcia
firmware -may-, but the drivers don't support it.
Realtek - Cards seem to be primarily software-driven, no
support in the drivers.
HermesII - Proxim successor to the Orinoco/HermesI. No support
The command "cardctl ident " should tell you what type of card you have. Hopefully it will be the WUSB11 v2.5, in order to get kismet going.
The kismet.conf has several examples of different sources. If you can use the wlan-ng driver, you would uncomment the source=prism2 line and comment out the source=cisco line.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.