Backtrack5 r3 reaver stuck after it is associated with 00:1F:C6:46:C4:65

[Vinnie]

Hello guys! I just want to say that this thing is awesome i just wish that i could make it work because i really wanna make it work.
So as you might know I am trying to test to get my wireless router WPA password by using backtracker 5 r3 reaver. I have followed many guides and i almost got it to work except its not actually trying to pin the router. Here is an example

root@bt:~# reaver -i mon0 -b 00:1F:C6:46:C4:65 -vv

Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>

[+] Waiting for beacon from 00:1F:C6:46:C4:65
[+] Switching mon0 to channel 1
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 3
[+] Switching mon0 to channel 4
[+] Switching mon0 to channel 5
[+] Switching mon0 to channel 6
[+] Switching mon0 to channel 7
[+] Switching mon0 to channel 8
[+] Switching mon0 to channel 9
[+] Switching mon0 to channel 11
[+] Associated with 00:1F:C6:46:C4:65 (ESSID: Home-Secure)

Does anyone know what is wrong? please help me guys i need help fast if possible.

All help is appreciated.
Kind Regards
Vinnie

[deviney]

I have tried reaver on BT5r3 Gnome VM image and had no problems.

I have how ever ran into some wireless routers that have appeared on walsh (the program used to find wireless router vulnerable to reaver) and also got to the Associated stage and the hung. I think its because the wireless router does not have WPS.

correct me if am wrong someone?

[Akumu]

I have came across this issue as well. When testing one of my routers, i have about 6 different ones, they are all listed when using wash -i mon(). I have came across using different networking adapters, alfa and others and had noticed it sometimes locks up. Many times if I restart the network card and disconnect it, it simply resumes.