Stuck at "checking for mac filtering"

[GoogleCodeExporter]

I had successfully had the script run all the way through the point that it
cracked a WEP key.  Not sure what has changed, but at this point, it simply
sits for hours and hours checking for MAC filtering.  

I can see where it's simply continuously looping through the while
<PREAUTH_IPC>) loop but I'm unsure why.

Any suggestions for something to try/add. 
The particular AP(s) that it gets stuck trying are in my control and
running standard OPEN/WEP configs with no MAC filtering.

While freshly rebooted and making sure the drivers are loaded properly and
no aircrack-ng or wepbuster perl process is running (e.g, pkill -9 air &&
pkill -9 perl)

1. What did you see when you ran wepbuster?

2. What do you see when you run "ifconfig"?

3. What do you see when you run "iwconfig"?

4. What do you see when you run "airmon-ng"?

5. Which Linux are you using?

6. Which wireless card/s are you using?
1. Chipset
2. Driver (built-in or no?)

7. Which interfaces are you supposed to be using or expecting wepbuster to
find?
1. as an injection interface
2. as monitor interface

8.  Which revision of wepbuster in SVN are you using? (normally, the
tarball is updated
everytime a change is commited, to be safe, always checkout the latest
revision
via svn)

9. Did you change and recompile the aircrack-ng sources?

10. What do you see when you do a "ps ax |grep perl && ps ax |grep air"
while
running the program?

11. Did you try setting these three manually?
1. $inject_iface
2. $monitor_iface
3. $mac_address

12. Did you read the "Troubleshooting" in the wiki???

13. Did you read it carefully?

14. Did you understand it? =)

15. Did you try running "airodump-ng -t WEP -n..." using $monitor_iface and
you are certain that you are seeing WEP-enabled access points and not some
odd shaped object that looks like a nuclear silo?

16. Did you run into some hot chick lately?

Original issue reported on code.google.com by hoopyfro...@gmail.com on 9 Jun 2009 at 3:33

[GoogleCodeExporter]

the latest revision of README.TXT contains the actual aircrack-ng commands that 
wepbuster is running. Try if 
you can run those command manually. Also, after running wepbuster, and I want 
to run it again, sometimes I 
have to reload the drivers for some reasons. you can try that as well..

Original comment by markjays...@gmail.com on 9 Jun 2009 at 4:00

[GoogleCodeExporter]

Build 47 with the removal of the -D seems to have taken care of this.  :)

Original comment by hoopyfro...@gmail.com on 10 Jun 2009 at 1:21

[GoogleCodeExporter]

nice. =)

Original comment by markjays...@gmail.com on 10 Jun 2009 at 1:53

[GoogleCodeExporter]

This probably isn't the best place to request this, but I don't see a 'request 
line'
anywhere :)

Could you add some code to show 'minutes/seconds to crack:' after a successful 
WEP crack?

Original comment by hoopyfro...@gmail.com on 10 Jun 2009 at 2:32

[GoogleCodeExporter]

Original comment by markjays...@gmail.com on 12 Jun 2009 at 5:04

• Changed state: Fixed