WASH not detecting any AP's [SOLVED]

[niftyspark]

WASH v1.4 is not detecting any AP's, nor is it throwing any errors.

Running Backbox 3.05 32-bit with 3.8 kernel - updates have been run. Reaver v1.4 works without issue as does airmon-ng airodump-ng etc.
Recently migrated from BT5r3 on the same hardware which ran WASH v1.4 without a problem.

sudo wash -i mon0

When running WASH it creates a 'reaver.db' file in '/usr/local/etc/reaver' which doesn't increase in size above 14KB.

Have compiled and installed WASH from source, but this has the same problem.

Any idea's where to go next?

[niftyspark]

After further investigation it appears REAVER isn't working correctly either. No errors are produced, but neither are the PIN numbers moving on, there are no M1, M2 etc messages. No file 'reaver.db' is created in '/etc/reaver/'?

Have tried with previous version of the Kernel 3.2, this produces the same results.

Any thoughts?

[niftyspark]

Further information that might be helpful, using Backbox 2.05 Live CD on the same machine, both wash and reaver work without issue. Does this point to the Kernel being the issue?

[ZEROF]

Hi,

I was playing this days to find few solution for my wifi card. Problem is that we have so many solution online, that is hard to say which one will work for us. My idea is that you have more then one problem.

1. It's two side problem, because of way some tools were coded, all system settings must be perfect before they will work (this is where we come to basic and pro linux users)
2. Kernel 3.8 is not that good for all ralink cards, some support was removed from this kernel version but i can't say what was removed
3. People don't try to install backports (old compact drivers) and to add aircrack patch.

What i have done to resolve all issues is 3.10 kernel, backports last version, install patch provided by aircrack team. Writing "how to" is possible but not that easy to do. Why? Every system have own settings and it's hard that my solution will work with other systems and because of that i prefer to give basic information and see people resolving this issue like a pro.

And, in the end, if we want to hack we need hardware for it and we need to know how that hardware actually works.

[niftyspark]

For me the solution, was in the end easy, the official Kernel 3.5 at http://wiki.backbox.org/index.php/Kernel_3_with_BackBox works without issue, fantastic.

I did try the suggestions, there is some great information available at http://wiki.backbox.org/index.php/Compat-drivers_aircrack_patched and http://www.mathyvanhoef.com/2012/09/compat-wireless-injection-patch-for.html Though I still couldn't get it to work on the 3.2 or 3.8 Kernels, this is probably more due to my failings than the process  :P

For now I'll stick with Kernel 3.5 ;D