search

inzision123 / reaver-wps

Automatically exported from code.google.com/p/reaver-wps
0 stars 0 forks source link

Not trying pins #57

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 

Hi, i'm using an alfa usb wifi adapter, in monitor mode using airmon-ng.
I used "reaver -i mon0 -b XX:XX:XX:XX:XX:XX -vv"
It associates with the AP, but doesn't start to try pins, with any of the 
networks I had available

Thanks

Original issue reported on code.google.com by byk...@gmail.com on 2 Jan 2012 at 10:07

GoogleCodeExporter commented 8 years ago 
Can you provide the output that reaver gives you?

Original comment by cheff...@tacnetsol.com on 2 Jan 2012 at 10:10

GoogleCodeExporter commented 8 years ago 
I use the Alfa AWUS036H and it works well with the rtl8187 driver in Ubuntu.

I compiled the bleeding edge compat-wireless
http://linuxwireless.org/en/users/Download and installed them.

In Ubuntu 11.04 and it all works.

Original comment by g...@watchingyou.info on 2 Jan 2012 at 10:43

GoogleCodeExporter commented 8 years ago 
How long are you waiting to see if reaver is going to start trying pins? 
Sometimes (with my experience) after associating with the AP it takes a couple 
of minutes before actually trying the 1st pin. Try to input reaver -i mon(what 
every number airmon-ng says) -b (whatever that bssid is for your target) -vv 
(if you want to display all messages) and walk away for a couple of minutes. 
See if you have any luck by waiting.

Original comment by GatorG...@gmail.com on 3 Jan 2012 at 6:01

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Hi. I've the same adapter. I tried all version of this software, but it does 
not try to find the pin. I waited about 24hour before to stop with the latest 
version.

this is the output:

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

[+] Waiting for beacon from 00:XX:XX:6F:XX:XX
[+] Switching mon0 to channel 1
[+] Associated with 00:XX:XX:6F:XX:XX (ESSID: SOME)

Original comment by zero...@gmail.com on 3 Jan 2012 at 6:27

GoogleCodeExporter commented 8 years ago 
@bykas, zeroc:

Do your APs support WPS? If so, please provide the command line options you are 
supplying to Reaver, along with the Reaver output and a pcap of the attack. 
Without this I can't help you.

Original comment by cheff...@tacnetsol.com on 3 Jan 2012 at 6:52

GoogleCodeExporter commented 8 years ago 
Ok.i Will retry the attack to my AP  using wireshark to get the pcap dump.
Thanks for your answer.

Original comment by zero...@gmail.com on 3 Jan 2012 at 7:20

GoogleCodeExporter commented 8 years ago

Original comment by cheff...@tacnetsol.com on 4 Jan 2012 at 2:43

GoogleCodeExporter commented 8 years ago 
I was too far from the AP when i tried. Now it works.

Original comment by giusyiac...@gmail.com on 5 Jan 2012 at 7:39

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Ok, so I tried again, with full verbose, and it started trying pins.
But when it tried the first one, it took a while to end, and finally it gave a 
"Timeout Error".
This happens with every AP I tried, most of them very close to my antenna.
All APs support WPS as far as I know, and btw, my interface is an Alpha 
AWUS036NH
Thanks again!

Original comment by byk...@gmail.com on 5 Jan 2012 at 8:23

GoogleCodeExporter commented 8 years ago 
Glad it's working for you now. :)

Original comment by cheff...@tacnetsol.com on 5 Jan 2012 at 9:17

GoogleCodeExporter commented 8 years ago 
I have the same problem... I am in monitor mode, type in reaver, it becames 
associated with the network I want, and after 15 mins of waiting it does not 
start to run pins, signal strength is very good... I am running reaver in bt4 
r2 ...

Original comment by franaza...@gmail.com on 16 Jul 2012 at 11:13