|
|
|||||||
| Register | Search | Today's Posts | Mark Forums Read |
 |
|
|
LinkBack | Thread Tools | Display Modes |
08-10-2006
|
#31 (permalink) |
|
Registered Member
Join Date: Sep 2003
Posts: 16
|
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...
|
|
|
|
08-10-2006
|
#32 (permalink) |
|
Alien Paranoid Stumbler
Join Date: May 2003
Location: WI
Posts: 2,625
|
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.
__________________
"Yeah," said a voice from under the table, "you go to pieces so fast people get hit by the shrapnel." |
|
|
|
|
08-10-2006
|
#33 (permalink) |
|
Registered Member
Join Date: Sep 2003
Posts: 16
|
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). Last edited by warnockm : 08-10-2006 at 08:41 PM. |
|
|
|
|
08-10-2006
|
#34 (permalink) |
|
Asshole Emeritus
Join Date: May 2003
Location: S.E. VA.
Posts: 5,913
|
Nice MAC address.
__________________
"Benjamin is nobody's friend. If Benjamin were an ice cream flavor, he'd be pralines and dick." Sons of Confederate Veterans |
|
|
|
|
08-10-2006
|
#39 (permalink) |
|
Alien Paranoid Stumbler
Join Date: May 2003
Location: WI
Posts: 2,625
|
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.
__________________
"Yeah," said a voice from under the table, "you go to pieces so fast people get hit by the shrapnel." |
|
|
|
|
08-11-2006
|
#40 (permalink) |
|
Registered Member
Join Date: Sep 2003
Posts: 16
|
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 Last edited by warnockm : 08-11-2006 at 07:58 PM. |
|
|
|
|
08-11-2006
|
#41 (permalink) |
|
Alien Paranoid Stumbler
Join Date: May 2003
Location: WI
Posts: 2,625
|
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.
__________________
"Yeah," said a voice from under the table, "you go to pieces so fast people get hit by the shrapnel." Last edited by King_Ice_Flash : 08-11-2006 at 11:01 PM. |
|
|
|
|
10-23-2006
|
#43 (permalink) |
|
Alien Paranoid Stumbler
Join Date: May 2003
Location: WI
Posts: 2,625
|
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.
__________________
"Yeah," said a voice from under the table, "you go to pieces so fast people get hit by the shrapnel." |
|
|
|
Linear Mode
