data and arp's got stucked!

[smartyx99]

Hi to all the experts...
This is my first post in backtrack forums.
First of all i want to thank all you guys for providing excellent tutorials.
So to gain some extra knowledge i bought an ASUS 167-G V2. (i did a lot of forums reading for that)
Successfully installed the drivers aftr a lot of trials.
Now at the final step for cracking the passwrd unfortunately i didnt get keys at 10000 IVs.
Now the problem arises--
Suddenly It seems the arps got stucked at 10190 and similarly the data also seems like stucked at 11226. After waiting for a lot of time 15-20 min i saw that the data moved only up 20-30 ivs in 20 minutes, so is the case with arp's. Now I have been waiting for 90 minutes and still it seems like mot going up.
What should be done in that case.
The PWR is almost 100.

[dromar421]

You might try injecting some more packets.But I have also had what seemed to be the stop and go problem and I opened a second shell window and switched to it and back over and found that the packets was really moving faster then what I though give those two things a try and maybe even a reboot to go at it fresh start up just a thought hope it helps. If you still have trouble get back to us with maybe a few screen shots or even the commands you are using.

[kill_box001]

Hi to all the experts...
This is my first post in backtrack forums.
First of all i want to thank all you guys for providing excellent tutorials.
So to gain some extra knowledge i bought an ASUS 167-G V2. (i did a lot of forums reading for that)
Successfully installed the drivers aftr a lot of trials.
Now at the final step for cracking the passwrd unfortunately i didnt get keys at 10000 IVs.
Now the problem arises--
Suddenly It seems the arps got stucked at 10190 and similarly the data also seems like stucked at 11226. After waiting for a lot of time 15-20 min i saw that the data moved only up 20-30 ivs in 20 minutes, so is the case with arp's. Now I have been waiting for 90 minutes and still it seems like mot going up.
What should be done in that case.
The PWR is almost 100.

can i have some more info about what you're actually trying to do here im assuming the following

-your using the most recent version of BT4
-your trying to break WEP
-you are using the aircrack-ng suite
-you are able to put your card into monitor mode [airmon-ng start wlan0] and inject packets [aireplay-ng -9 mon0]
-you have permission to pen test against this network

what i need to know is

-does the AP your pen testing against have client associated with it


you don't necessarily need 10000 IVS, its more like the minimum..the more you capture the more accurate and quickly you will be able to break the password with aircrack-ng

try finding some videos and tutorials on pentesting with wifi networks theres plenty out there even on youtube..

[halfdone]

Try using Gerix wifi cracker.Its quite easy.

[gunrunr]

and if by chance you set your WEP for 128 bit it may take 3 times as many packets or more. If you go ahead and use gerix wifi cracker try the packet forging attack that tends to make the iv count climb rather quickly. If you are successful first thing you should do is configure wpa/wpa2 with a strong non dictionary passkey. WEP is a lie.

[smartyx99]

This is my own network testing.
Plz watch the following link further for more new problems associated with it after giving it a new try.
http://www.backtrack-linux.org/forum...tml#post167897
The following commands i used--
airmon-ng start rausb0
airodumo-ng rausb0
airodump-ng -c 11 -w wep --bssid 12:01:33:10a:00 rausb0
aireplay-ng -1 0 -a (bssid) -h (fake mac) rausb0
aireplay-ng -3 -b (bssid) -h (fake mac) rausb0
aircrack-ng -b (bssid) (filename-02.cap)