Ticket #342 (assigned defect)
Kismac crashes when starting to reinject
| Reported by: | CyrilH | Owned by: | pr0gg3d |
|---|---|---|---|
| Priority: | major | Milestone: | 0.4 |
| Component: | cracking engine | Version: | 0.2.99 |
| Keywords: | rt73 inject crash | Cc: | erhankpln@… |
Description
Hi, I have a Powerbook PPC 1.5 GHz 1.25 MB and a D-Link DWA-110 ver A1 (rt73) wifi dongle. Everything seems to work fine with Kismac 0.2.99 until I try to reinject packets and it crashes. Crash.log attached. Please help.
Attachments
-
KisMAC.crash.log
(187.1 KB) -
added by CyrilH 3 years ago.
- Kismac crash log
-
err.log
(16.5 KB) -
added by CyrilH 3 years ago.
Change History
Changed 3 years ago by CyrilH
-
attachment
KisMAC.crash.log
added
comment:1 Changed 3 years ago by CyrilH
- Owner changed from nobody to CyrilH
- Status changed from new to assigned
comment:4 Changed 3 years ago by fish
- Keywords rt73 inject crash added
- Owner changed from CyrilH to pr0gg3d
- Status changed from accepted to assigned
- Component changed from build to cracking engine
Please attach the console log from KisMAC startup through the crash. We do request rather clearly....
Did you have any injectable packets, and was the attempt against a WEP network? Were you channel hopping or were you locked on the the AP's channel?
comment:5 Changed 3 years ago by CyrilH
I attached the console crash log in the first place. Do you need anything else? There are several problems: First, sometimes (not always) when I click "start scanning", Kismac goes crazy: 90% of CPU and not responding. I then have to kill the process, delete the Kismac preference file and restart the computer. Sometimes I have to repeat this operation many times before it works (ie starts scanning and networks appear). Then, when I try to reinject packets on the WEP network I want to crack (and before this of course I have to disable the channel hopping), a window with the injected packets appears a few seconds and then it crashes. NO packets are reinjected. Last problem: when I try "Authentication flood" on the same WEP network, it also crashes but only after a few minutes. Before each crash the Kismac process takes 90% of the CPU time. Thanks for your help!
comment:6 Changed 3 years ago by pr0gg3d
We need also the "console log" as fish said.
It's what you obtain if you run KM into a terminal with:
/Application/KisMAC.app/Contents/MacOS/KisMAC
ot what do you have at /var/log/system.log.
Thanks, pr0gg3d
comment:7 Changed 3 years ago by CyrilH
Here's the crash log (Kismac started from terminal with standard output redirected towards err.log file attached) Cheers, CH.
comment:8 Changed 3 years ago by fish
Have you reset the USB device before restarting KisMAC? I have only ever seen the app attempt to set transmit power levels for unsupported channels (anything above 14) when the device is not functioning properly, usually after a crash.
To reset the device, simply quit KisMAC and unplug the stick for five seconds. Reconnect the stick and start KisMAC back up. See if it works then.
For the record, the Console Log can also be obtained from /Applications/Utilities/Console?.app (this is covered in the Required Information post).
comment:9 Changed 3 years ago by CyrilH
Yes, I did. Actually after each crash the light on the stick stays on (power is supplied). So I unplug it and reconnect it each time, and also delete the kismac preference file. The only thing I did wrong from the start was to install the constructor's driver. But then I read that I shouldn't and uninstalled it with the uninstall program on the CD provided with the dongle.
comment:10 Changed 2 years ago by gkruse
- Milestone changed from 0.2.99 to 0.4
Milestone 0.2.99 deleted
Kismac crash log