NetStumbler.org Forums - View Single Post - New tool to crack WEP keys under GNU/Linux

topolb · 06-10-2004

Issue this command and post here the results please.

./weplab -r ./packets.log --debug 1 --debugkey FF:AA:FF:AA:FF: --key 64 --prismheader ./packets.log

I will tell you if all went ok. 400 b/s is too much. I think that maybe your logged packets are not in the right format.
Also you may need to use --fcs (THIS IS IMPORTANT). Some drivers adds a tail called fcs to logged packets in monitor mode. If it is happening to you and you dont tell anything to weplab, weplab will be unable to test candidate keys.

c/s are the number of keys that are tested per second
b/s (branch per second) are the number of bytes that are calculated per second in the FMS attack.

You can press the ENTER key anytime during the crack to get statistics of the work done. You will see what is the current key that is being tested.

06-10-2004	#18 (permalink)
topolb Registered Member Join Date: Jun 2004 Posts: 67	Issue this command and post here the results please. ./weplab -r ./packets.log --debug 1 --debugkey FF:AA:FF:AA:FF: --key 64 --prismheader ./packets.log I will tell you if all went ok. 400 b/s is too much. I think that maybe your logged packets are not in the right format. Also you may need to use --fcs (THIS IS IMPORTANT). Some drivers adds a tail called fcs to logged packets in monitor mode. If it is happening to you and you dont tell anything to weplab, weplab will be unable to test candidate keys. c/s are the number of keys that are tested per second b/s (branch per second) are the number of bytes that are calculated per second in the FMS attack. You can press the ENTER key anytime during the crack to get statistics of the work done. You will see what is the current key that is being tested.