mattbasc
January 11th, 2009, 07:58 PM
I am using Kismet 2008 05 R1. I tried installing using a package manager and using by compiling from source but I am getting the same error.
My kernel version is 2.6.24-21-generic.
I am using iwl3945 as my capture source type.
I have tried all the other similar ones: ipw3945, ipwlivetap. But they do not work.
The error I get when attempting "sudo kismet" is:
FATAL: channel get ioctl failed 95:Operation not supported
Done.
I have read that this means that I need to change my drivers. But I have up-to-date iwlwifi drivers (which contain the file iwl3945) in the kernel directory.
PROBLEM: Fatal error enabling monitor mode, 'monitor' ioctl not available
Some capture sources use a private ioctl, 'monitor', to enable rfmon.
If Kismet is unable to find this ioctl, it means that the wrong
interface was specified, the wrong capture type is being used, or
most commonly, the drivers you are using have not been patched or the
patched drivers are not being loaded.
Be sure to download any patches needed for the drivers you are using,
and make sure that no other copies of those drivers exist in your
/lib/modules/kern-version/ directory. You may need to restart pcmcia-cs
if your wireless card was already running when you installed the patched
drivers.
FIX: Provide the correct interface and ensure that the patched drivers are
loaded.
My kernel version is 2.6.24-21-generic.
I am using iwl3945 as my capture source type.
I have tried all the other similar ones: ipw3945, ipwlivetap. But they do not work.
The error I get when attempting "sudo kismet" is:
FATAL: channel get ioctl failed 95:Operation not supported
Done.
I have read that this means that I need to change my drivers. But I have up-to-date iwlwifi drivers (which contain the file iwl3945) in the kernel directory.
PROBLEM: Fatal error enabling monitor mode, 'monitor' ioctl not available
Some capture sources use a private ioctl, 'monitor', to enable rfmon.
If Kismet is unable to find this ioctl, it means that the wrong
interface was specified, the wrong capture type is being used, or
most commonly, the drivers you are using have not been patched or the
patched drivers are not being loaded.
Be sure to download any patches needed for the drivers you are using,
and make sure that no other copies of those drivers exist in your
/lib/modules/kern-version/ directory. You may need to restart pcmcia-cs
if your wireless card was already running when you installed the patched
drivers.
FIX: Provide the correct interface and ensure that the patched drivers are
loaded.