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?
Can't locate Expect.pm in @INC (@INC contains: /etc/perl
/usr/local/lib/perl/5.1.0.0 /usr/local/share/perl/5.10.0 /usr/lib/perl5
/usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10
/usr/local/lib/site_perl .) at wepbuster line 5.
BEGIN failed--compilation aboarted at wepbuster line 5.
root@btbt:~/wepbuster-1.0_beta#
2. What do you see when you run "ifconfig"?
I am using backtrack4 live cd and networking is up (both wireless and wired).
3. What do you see when you run "iwconfig"?
I am using backtrack4 live cd and networking is up (both wireless and wired).
4. What do you see when you run "airmon-ng"?
airmong-ng is working fine at wlan0.
5. Which Linux are you using?
backtrack 4 live cd
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 attah...@gmail.com on 22 Jul 2009 at 3:49
Original issue reported on code.google.com by
attah...@gmail.com
on 22 Jul 2009 at 3:49