search

omegakw / reaver-wps

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

Reaver 1.3 on a specific AP has a problem while other APs works fine. #459

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
1. What operating system are you using (Linux is the only supported OS)?
backtrack 5 R 1

2. Is your wireless card in monitor mode (yes/no)?
yes

3. What is the signal strength of the Access Point you are trying to crack?
-60 to -70

4. What is the manufacturer and model # of the device you are trying to
crack?
Interface    Chipset        Driver

wlan0        Atheros AR9287    ath9k - [phy0]
                (monitor mode enabled on mon0)

5. What is the entire command line string you are supplying to reaver?
 reaver -i mon0 -b 00:22:3F:C4:24:96 -c 12 -vv

6. Please describe what you think the issue is.
it blocks me at 1.12% 

7. Paste the output from Reaver below.

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

Trying pin 62281560
[!] WARNING: Receive timeout occurred
[+] Trying pin 62281560
Trying pin 62281560
[!] WARNING: Receive timeout occurred
[+] Trying pin 62281560
Trying pin 62281560
[!] WARNING: Receive timeout occurred
[+] Trying pin 62281560
Trying pin 62281560
[!] WARNING: Receive timeout occurred
[+] Trying pin 62281560

8. RX Quality 

The RX Quality is between 96 - 100%

Hi cheffner,

I have tried backtrack5R3, backtrack5R2,backtrack5R1 on several APs and was 
successful in getting WPS pins along with correct password. 

But there was one particular unknown AP that i couldn't do it at all. So i 
lately found one article issue of reaver no.175. I followed those steps 

and surpringly it worked but partially.   

Summarize Software on my PC was BT5R1, Compact Wireless 3.3 with Patches as in 
mentioned in reaver issue 175, and Reaver 1.3 version used.

Now i am very excited to know why the WPS Pins tested by reaver version 1.3 
stop at 1.12%. Although 1.12% took almost a day but PINS 

followed one after another with some "WARNING: Receive timeout occurred".

Now it's not moving and keeps repeating on pin 62281560.

At this point of time,  i have taken a tcpdump trace which i believe you might 
provide a better insight. 

My apologies as i haven't done tcpdump before 1.12% for the working PINS.

Thanks,
Johny Blair

Other Info: The software on my PC with compact wireless 3.3 works fine with 
other APs.

Original issue reported on code.google.com by JohnyBla...@gmail.com on 16 Jan 2013 at 1:20