[Orinoco-users] Problems with scanning in the latest Orinoco driver version

[Marcelo Terres]

Hi.

I'm using Kubuntu with kernel 2.6.17.13.

I compiled the latest orinoco cvs version, and I change this line in
orinoco.c:

static int force_monitor = 1; /*=0*/ (line 115)

like indicated in https://wiki.ubuntu.com/OrinocoMonitorMode.

But I'm still not able to scanning, like you can see above:

***@homeserver:~/tmp$ sudo iwlist eth1 scan
eth1 Interface doesn't support scanning : Operation not supported

If I try to use kismet (version 2005.08.R1-1.2), I'm getting the following
error:

***@homeserver:/usr/local/src/orinoco_cvs/orinoco/trunk# kismet
Server options: none
Client options: none
Starting server...
Waiting for server to start before starting UI...
Suid priv-dropping disabled. This may not be secure.
No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Enabling channel splitting.
Source 0 (orinoco_cs): Enabling monitor mode for orinoco source interface
eth1 channel 6...
FATAL: Could not find 'monitor' private ioctl or use the newer style 'mode
monitor' command. This typically means that the drivers have not been
patched or the correct drivers are being loaded. See the troubleshooting
section of the README for more information.


Any ideas ?

Thanks,

[Pavel Roskin]

Hello, Marcelo!

Post by Marcelo Terres
I'm using Kubuntu with kernel 2.6.17.13.
I compiled the latest orinoco cvs version, and I change this line in

The driver is no longer maintained in CVS. I think you mean the latest version
from the SourceForge Subversion repository.

Post by Marcelo Terres
static int force_monitor = 1; /*=0*/ (line 115)
like indicated in https://wiki.ubuntu.com/OrinocoMonitorMode.

I looked at that page, and it doesn't seem quite right to me. Forcing monitor
mode on Lucent/Agere 7.xx and 8.xx firmwares makes the firmware unstable. It
may be OK for tcpdump on a single channel, but AirSnort with channel scanning
crashes firmware in less than a minute. The document in Wiki doesn't tell
about the downsides of enabling force_monitor.

Post by Marcelo Terres
eth1 Interface doesn't support scanning : Operation not supported

Scanning is not supported in monitor mode. Please show the output of iwconfig
(which would indicate the mode among other things) and the kernel messages from
the driver (as shown by dmesg), which would show the firmware version and
possible firmware failures due to the buggy monitor mode.

--
Regards,
Pavel Roskin