Tested Key don't change about reaver-wps

[GoogleCodeExporter]

Oh I forgot, it's BT5 R1 32 bit ;)

Original comment by [email protected] on 31 Dec 2011 at 1:50

[GoogleCodeExporter]

I have the same issue regardless of the AP vendor.

Info: 
- BT5 R1 32 bit
- Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) 
(rev 01)
- Reaver 1.2 R34
- tested against various APs

Original comment by [email protected] on 31 Dec 2011 at 1:55

[GoogleCodeExporter]

@hurnhan

I have a RT2800usb with Ralink 3070 chip, and what I had to do, to stop the 
repeating key issue was run, "sudo airmon-ng start wlan0", as soon as I booted 
in. It sounds simple, I know, but if I stopped the adapter with the "sudo 
airmon-ng stop wlan0" then started it, right after boot up, I received several 
errors as well as the repeating of the same key, for some odd reason (did it 
again this morning just confirm that I was not crazy since it made no sense to 
me). The only caveat is that I am using MythUbuntu 10.4 and getting the drivers 
to work on this build is/was not easy....

Original comment by [email protected] on 31 Dec 2011 at 2:13

[GoogleCodeExporter]

@juanpedr

thanks for this tip, but it didn´t work for me :(

I also tested it in a VM with the same results.

Original comment by [email protected] on 31 Dec 2011 at 2:28

[GoogleCodeExporter]

@juan/hannes:

airmon-ng start wlan0 
-> enables the monitoring inteface mon0
-> the WLAN adaptor is in promiscuous mode

airmon-ng stop wlan0 
-> disables the monitoring mode
-> the WLAN adaptor is in master mode 

Original comment by [email protected] on 31 Dec 2011 at 2:37

[GoogleCodeExporter]

yes, I know :)

Original comment by [email protected] on 31 Dec 2011 at 2:44

[GoogleCodeExporter]

Okay, just wanted to clear up any confusion. Which wifi driver are you using 
(you should see it when enabling/disabling the monitoring interface)? 
Even though the ath9k driver is on the list of working drivers I get the same 
output as you. 

Original comment by [email protected] on 31 Dec 2011 at 2:54

[GoogleCodeExporter]

I´m using rt2800usb.

Original comment by [email protected] on 31 Dec 2011 at 3:00

[GoogleCodeExporter]

this problem is here on arch linux too

Original comment by [email protected] on 1 Jan 2012 at 1:29

[GoogleCodeExporter]

this problem is here on arch linux too

Original comment by [email protected] on 1 Jan 2012 at 1:29

[GoogleCodeExporter]

Same problem here: Kubuntu 11.10 running on Asus EeePC 1215, 64bit mode, 
wireless chipset AR9285 and driver is ath9k

Original comment by [email protected] on 1 Jan 2012 at 7:58

[GoogleCodeExporter]

For anyone/everyone having this issue, can you confirm that:

1) The AP you are targeting supports WPS and has WPS enabled.
2) You have a good signal strength from the AP and low interference on the AP's 
channel and surrounding channels?

From hurenhannes output, it looks like Reaver is running but it isn't able to 
complete a full WPS transaction (or possibly unable to even start one), so it 
keeps re-trying the same pin.

This type of bug is also going to be nearly impossible for me to diagnose with 
pcaps...

Original comment by [email protected] on 2 Jan 2012 at 12:54

[GoogleCodeExporter]

Issue 39 has been merged into this issue.

Original comment by [email protected] on 2 Jan 2012 at 12:58

[GoogleCodeExporter]

Any more info on this? Pcaps?

Original comment by [email protected] on 4 Jan 2012 at 2:45

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Nope, I think it was a just a driver problem at this point. The rt2800usb 
driver suck so bad in BT5 R1 and no chance to fix that :(

Original comment by [email protected] on 4 Jan 2012 at 4:31

[GoogleCodeExporter]

OK, thanks!

Original comment by [email protected] on 4 Jan 2012 at 4:36

• Changed state: WontFix