Ok - This is a fantastic USB device, the range on it, is amazing. However there are some serious bugs in the drivers I think that let it down.
Here's where I've gotten to:
I'm using the BT2 iso in a vmware machine.
1) I launch flux (or startx) and go into a terminal window.
2) I ensure that I edit airoscript.sh is modified to use /tmp as the dump directory, "wlan0" as the default device, AND I change the fake-mac address in the script to "00:01:02:03:04:05"
3)
I HAVE TO DO THIS FIRST BEFORE RUNNING THE SCRIPT:
Code:
ifconfig wlan0 hw ether 00:01:02:03:04:05
If I run the airoscript and try to change the mac from there the USB device will NOT work for association.
4) Now I run airoscript. Here's the next bug.....after I scan for networks, and select a particular AP, I only get ONE chance to crack it. When I select the attack option (3) and say use fake-association, 9 out of 10 times I will associate with the AP and all will be well.
5) If the association fails, or I decide to select and attack another (second) AP, the USB device is useless! It fails to work! The only way around it is to quit airoscript, and do the following
Code:
ifconfig wlan0 down
(remove the usb cable from computer for 2 secs and replace)
(Wait 20secs for device to be recognised)
ifconfig wlan0 hw ether 00:01:02:03:04:05
airoscript.sh
and start again.
I have to do a very hard reset after every association attempt by the USB device - even if it was successful or not, it always requires a reset to try again.
Also, when I get injecting with the Alfa, I get a statistic of around 250-320 ivs/sec on the screen, however it feels a LOT slower than that. Ie. At that speed I should get 1000 ivs in around 4 secs. If I use my watch it takes closer to 12secs. Why?
Also! On my laptop I have exactly the same setup. When I am injecting (the same AP as before) it can show as low as 10 ivs/sec. As soon as I run the crack command (4) from airoscript and leave that window running in the background my ivs/sec shoot up to 300 again!!!
It's almost as if the extra cycle taken by the computer in processing the aircrack-window, allows the other windows (inject/capture/associate) more time to get their things done and work more efficiently!
Can anyone either shed some light or know a better software driver to use etc?
Can anyone else recreate these problems too?