Closed GoogleCodeExporter closed 9 years ago
Please provide more information.
what version of aircrack-ng are you using?
What WEP attacks are you attacking with (chopchop, arp, "all")?
What is being output by the program during the attack?
Does "auto-crack" start after 9,000+ IVs are collected?
How many IVs does it collect?
How long did you let the attack run?
Original comment by der...@gmail.com
on 2 Oct 2010 at 5:42
what version of aircrack-ng are you using?
I believe, it is the newest version, but i am unsure of the exact revision
What WEP attacks are you attacking with (chopchop, arp, "all")?
It is set to use Arp and fragmentation
What is being output by the program during the attack?
Can you please clarify this one?
Does "auto-crack" start after 9,000+ IVs are collected?
Yes, it states that it has begun to auto-crack.
How many IVs does it collect?
The longest ive let it run, was about 10 minutes and it collected about 400,000
IVs.
Original comment by chrisk...@gmail.com
on 3 Oct 2010 at 12:59
to see which version of aircrack you are running, type:
aircrack-ng --version
it's at the top of the output, and will look something like:
aircrack-ng 1.0 r#### etc
I need to know the version and revision (r) numbers; basically the first few
lines of the --version output.
----------------------------------
"What is being output by the program during the attack?"
To rephrase: How do you know wifite is attacking? Is it displaying text of some
kind to you, possibly in a terminal window? If it is, this is the output of the
program. Can you copy/paste this text so that I can see what it is saying?
I have more questions:
Have you ever cracked WEP on your machine without the use of an automated tool
before?
If you test again: after Wifite starts auto-cracking (over 9,000 IVs) in a new
terminal window run the command "top" to see running currently running
processes. Look for "aircrack-ng" in the list of processes. If you do see
aircrack-ng, see if aircrack has "<defunct>" next to it. This would help with
debugging this glitch.
Original comment by der...@gmail.com
on 3 Oct 2010 at 1:27
No response for 10 days; I'm assuming the issue corrected itself or the user
stopped caring.
Original comment by der...@gmail.com
on 12 Oct 2010 at 5:29
Original issue reported on code.google.com by
chrisk...@gmail.com
on 2 Oct 2010 at 8:14