Reaver "Failed to associate......." , "Waiting for beacon..."

[satana77]

CAn someone say what is my trouble with reaver and my MK4?

i have latest firmware 2.8.0,only reaver installed and it's on usb.

Other tools like sslstrip,DNSspoofing,MITM are working perfectly,but i need reaver leaved in dark corner.

Tried to do brute forcing from command line via ssh and from web-UI on 3 different APs(and on mine too).Nothing works, reaver just waiting for beacon for sometime and then gives warning "Failed to associate".

Tried to disable wlan0 - no effect.

Tried airodump-ng :it's hopping channels and catching beacons as well.

Tried wash: it finds all wps-enabled APs.

I read on the Reaver project page(googlecode) that the problem might be in the Big-Endian.I understand what it mean,but can't solve this problem alone.any suggestions?

PS i'll pray if it will be solved.

Edited April 13, 2013 by satana77

[digip]

Try a different target known to be vulnerable? Reaver us hit or miss, noisy, and in many instances, can just completely fail or even DoS the router you are targeting. Its also possible the targets aren't WPS enabled? I've never gotten it to work for me personally, but could be my NIC, or my setup.

[khaotic57]

Why are you posting in two forums about the same question/topic?