search

nyck92 / reaver-wps

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

reaver timeouts on any APs regardless of signal strength #119

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
been trying several accesspoints, also ones with strong signal and for some 
reason after trying pin.... its just timing out on 5 different APs. I ran 
airodump to see if the signal could be problem i associate with it and stays 
connected, but reaver however tells me timeout timeout and sometimes 
association failed. Now I read that this could be a driver problem? My device 
not being able to perform the reaver pin attack. Ive been able to crack wep 
with packet injection, but this is of course different attack. I'm using 
backtrack 5 and had to manually install the zydas1211rw driver for my hawking 
usb dish (hwu8dd) I read the page of supported drivers it wasn't listed there 
initially but in the comments said someone that it worked with zydas1211rw. I 
really don't know what else could cause these timeouts. What are the odds of 
all 5 Aps locking me out and just give me timeout response without any other 
notice after just trying 1 pin. please help!

Original issue reported on code.google.com by marcodem...@gmail.com on 10 Jan 2012 at 12:32

GoogleCodeExporter commented 8 years ago 
Assuming all 5 APs support WPS, the odds of that are very low. I've tested 
Reaver with one Harking card before (forget the model number now), and it 
didn't play well, so it could be a driver issue.

Can you provide the Reaver options you are supplying as well as the output from 
Reaver and a pcap of the attack?

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

GoogleCodeExporter commented 8 years ago

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

GoogleCodeExporter commented 8 years ago

Original comment by cheff...@tacnetsol.com on 11 Jan 2012 at 4:59

GoogleCodeExporter commented 8 years ago 
I am not sure this belongs here, in another issue or nowhere at all. Sorry if 
it's the latter.

But regarding what you said about signal strength being an issue even at 
-60dbm, I was doubtful. So I got closer to my AP, less than 2 meters away with 
a PWR of -35/-40 and an RXQ of 100, and here's Reaver's output.

(It contains some timeouts and some out of order packets and benefits from 
r86's more detailed output. Sorry for no pcap I haven't figured out how to 
sanitize it. TCPDump is available if needed.)

Original comment by b1957...@nwldx.com on 11 Jan 2012 at 6:45

Attachments:

GoogleCodeExporter commented 8 years ago 
I noticed you're using the -A option, so I assume you're using aireplay-ng to 
perform the association. Was Reaver unable to associate to the AP on its own? 
If so, this sounds like the same problem as reported in issue 117.

Original comment by cheff...@tacnetsol.com on 11 Jan 2012 at 6:54

GoogleCodeExporter commented 8 years ago 
Before going to issue 117 I have to precise that I've always had problems with 
association, even before r56. We thought it was an issue with my driver iwlagn 
(card Intel Wireless Link 5100).

Do you think it's still a driver issue? In which case I could be better for you 
that I stop testing until Reaver is integrated to Aircrack.

Original comment by b1957...@nwldx.com on 11 Jan 2012 at 7:15