Page 3 of 3

PostPosted: Wed Aug 09, 2006 3:18 pm
by King_Ice_Flash
warnockm wrote:Got it patched. Thanks for the hex editor instructions! still no monitor mode on 8.10...

Any 8.x firmware version has been blacklisted from the .15 Orinoco drivers. You need to use a version 6.X or 7.X. 7.52 would probably be my first choice.

PostPosted: Wed Aug 09, 2006 5:57 pm
by warnockm
Ah, luck is not on my side. for some reason, the 8.xx and 6.xx drivers work when edited, but the 7.xx ones do not. since i couldn't use 8.xx, i had to go down to 6.xx. however, monitor mode now works! thanks king!

PostPosted: Thu Aug 10, 2006 5:57 pm
by warnockm
ok ok... so question... now when i run "iwconfig ethx mode monitor", the command is sucessful, however, "iwpriv ethx" does not list "monitor". Kismet, however, runs, but dies after 30 seconds. I'm thinking there's still a problem w/ my firmware or drivers. Any suggestions you can give me? Each step gets me a little closer...

PostPosted: Thu Aug 10, 2006 6:00 pm
by King_Ice_Flash
Are you putting the card into monitor mode before starting Kismet? I usually just let kismet put the card into monitor mode. Usually kismet says something when it quits. Any idea what that was?

Also, type 'dmesg' before kismet starts and after it crashes, see if it says anything.

PostPosted: Thu Aug 10, 2006 6:53 pm
by warnockm
dmesg after insert:

pccard: PCMCIA card inserted into slot 0
pcmcia: registering new device pcmcia0.0
eth2: Hardware identity 0001:0001:0004:0000
eth2: Station identity 001f:0001:0006:0010
eth2: Firmware determined as Lucent/Agere 6.16
eth2: Ad-hoc demo mode supported
eth2: IEEE standard IBSS ad-hoc mode supported
eth2: WEP supported, 104-bit key
eth2: Station name "HERMES I"
eth2: ready
eth2: index 0x01: , irq 3, io 0x4100-0x413f
ADDRCONF(NETDEV_UP): eth2: link is not ready
eth2: New link status: Connected (0001)
ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
eth2: no IPv6 routers present

dmesg after kismet dies:

ADDRCONF(NETDEV_UP): eth2: link is not ready
device eth2 entered promiscuous mode
audit(1155275209.263:5): dev=eth2 prom=256 old_prom=0 auid=4294967295
hermes @ 00014100: Timeout waiting for command 0x0002 completion.
eth2: Unable to disable port while reconfiguring card
eth2: Resetting instead...
eth2: New link status: Disconnected (0002)
eth2: New link status: Connected (0001)
ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready

kismet dies with this message:

FATAL: Failed to set channel 7 16: Device or resource busy
Terminating.
Didn't detect any Cisco Discovery Packets, unlinking cisco dump
Didn't see any weak encryption packets, unlinking weak file
Sending termination request to channel control child 3110...
Waiting for channel control child 3110 to exit...
Kismet exiting.

I'm running Fedora FC5 w/ the original orinoco drivers (0.15).

PostPosted: Thu Aug 10, 2006 7:22 pm
by G8tK33per
Nice MAC address.

PostPosted: Thu Aug 10, 2006 7:42 pm
by warnockm
G8tK33per wrote:Nice MAC address.


better than a wep key ;)

PostPosted: Thu Aug 10, 2006 9:01 pm
by King_Ice_Flash
Which kernel are you using?

PostPosted: Thu Aug 10, 2006 9:09 pm
by warnockm
King_Ice_Flash wrote:Which kernel are you using?


2.6.17

PostPosted: Thu Aug 10, 2006 10:10 pm
by Barry
[quote="warnockm"]better than a wep key ]


That all depends on how we, ahhh, somebody uses it. ;)

PostPosted: Thu Aug 10, 2006 10:15 pm
by King_Ice_Flash
Ill give it a try with the latest 2.6.17 tomorrow with the 6.x firmware. It's honestly been a while since I have touched a FC5 system. If I don't have the same issue, I don't really know how to help.

PostPosted: Fri Aug 11, 2006 6:10 pm
by warnockm
I tried it on another computer running 2.6.17 and FC5. I had compiled 0.13 drivers before using kernel 2.6.17, and installed them. Using those same modules, Kismet does not lock up. It appears that the FC5 kernel cannot compile the dragorn drivers. Looks like this is the prob, not the firmware.

this is the error on the make of orinoco-0.13-dragorn-2.6.17 drivers:

make -C /usr/src/kernels/2.6.17-1.2157_FC5-i686 M=/root/orinoco-0.13-dragorn-2.6.17 modules
make[1]: Entering directory `/usr/src/kernels/2.6.17-1.2157_FC5-i686'
CC [M] /root/orinoco-0.13-dragorn-2.6.17/orinoco_cs.o
In file included from /root/orinoco-0.13-dragorn-2.6.17/orinoco_cs.c:27:
/root/orinoco-0.13-dragorn-2.6.17/orinoco.h:63: warning: ‘packed’ attribute ignored for field of type ‘uint8_t[16]’
/root/orinoco-0.13-dragorn-2.6.17/orinoco.h:194: warning: ‘packed’ attribute ignored for field of type ‘char[16]’
/root/orinoco-0.13-dragorn-2.6.17/orinoco_cs.c: In function ‘orinoco_cs_detach’:
/root/orinoco-0.13-dragorn-2.6.17/orinoco_cs.c:158: error: implicit declaration of function ‘free_orinocodev’
make[2]: *** [/root/orinoco-0.13-dragorn-2.6.17/orinoco_cs.o] Error 1
make[1]: *** [_module_/root/orinoco-0.13-dragorn-2.6.17] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.17-1.2157_FC5-i686'
make: *** [modules] Error 2

PostPosted: Fri Aug 11, 2006 9:59 pm
by King_Ice_Flash
With FC5, you don't have to compile any drivers. The ones that came with the kernel. As much as I don't like the .15 Orinoco drivers that come with the kernel, the still do work somewhat reliably.

Trying to install your .13e drivers may be causing the issues you are having. The installer/modules are very outdated.

I have had very poor luck getting the 0.13 drivers working with FC5, and the time when I did get it to work, I had already screwed around with the system so much (Installing the stock kernel without any RH patches and then recompiling it for my particular system) that the system wasn't entirely stable for anything but Kismet. Even when I tried it again, I couldn't make it work for my self, let alone write instructions for the average user.

I just tried mine with the 6.16 firmware, and it ran just fine, detecting the 5 WAPs in the neighborhood from my room.

PostPosted: Sat Aug 12, 2006 4:13 pm
by warnockm
I did not try anything but to compile them. I'm still running the drivers that came w/ FC5. Not sure why it's crashing on me. Thanks for your help.

PostPosted: Mon Oct 23, 2006 10:17 pm
by King_Ice_Flash
FC6 has been (un)officially released and installed, so the new Kismet howto has begun (There is a Kismet RPM, so this should be the easy part :) Now onto that perpetually pesky Orinoco issue.