Aircrack-ng Fails All The Time Options

[Capn_Fish]

I've been trying to crack the WEP key on one of my spare routers, but Aircrack-ng fails every time, even with 1 million+ IVs.

What I've been doing is:

CODE

airodump-ng --ivs --write <write prefix> --channel <router's channel> <interface>

Then, once I have a lot (1,000,000+) IVs, I do:

CODE

aircrack-ng -c -a 1 -e <ESSID> -b <BSSID> <*.ivs file>

Is there something wrong with that method? It goes for ~6 hours, then says it failed.

Thanks.

[Capn_Fish]

Nobody sees anything wrong with that? I'm probably doing something wrong.

EDIT: It appears I am using the wrong process. I guss I need patched drivers.

[ogrefish]

if you can get the patched injection drivers working....

You could try using aircrack-ptw. Make sure you dont collect ivs though with airodump, use the cap file instead, so ya dont use the --ivs.. Its quicker by far and you can crack wep with around 20k collected packets.

Ya Airodump command is fine.

When i did use the old aircrack-ng, i used

aircrack-ng -f 2 -a 1 -b APmac -n 64 (filelocationname).ivs Can switch 64 for 128 too.

-f is the fudge factor, can try up to 4. If still no luck try disabling the korek attack by adding -k (from 1-17).

Still, now aircrack-ptw is out now, no need for that really

(Still trying to get injection working on cacko using the 2.418 kernel )

hope that helps

[Capn_Fish]

if you can get the patched injection drivers working....

You could try using aircrack-ptw. Make sure you dont collect ivs though with airodump, use the cap file instead, so ya dont use the --ivs.. Its quicker by far and you can crack wep with around 20k collected packets.

Ya Airodump command is fine.

When i did use the old aircrack-ng, i used

aircrack-ng -f 2 -a 1 -b APmac -n 64 (filelocationname).ivs    Can switch 64 for 128 too.

-f is the fudge factor, can try up to 4. If still no luck try disabling the korek attack by adding -k (from 1-17).

Still, now aircrack-ptw is out now, no need for that really

(Still trying to get injection working on cacko using the 2.418 kernel   )

hope that helps

I'll look into that.

I'm about an inch away from being able to compile modules, though, so I'll be able to use that too.

Thanks.