TH3GR3AT3STT3AM / reaver-wps

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

wash does not detect AP #392

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Answer the following questions for every issue submitted:

0. What version of Reaver are you using?  

1.4

1. What operating system are you using (Linux is the only supported OS)?

Ubuntu 10

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?

-58

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

motorola wr850g

5. What is the entire command line string you are supplying to reaver?

wash -i mon0 -C
wash -c 1 -i mon0
wash -c 1 -s -i mon0

reaver -i mon0 -c 1 -b 00:26:41:xx:xx:xx -vv -x 360

6. Please describe what you think the issue is.

Dunno. Even if the AP isnt vuln to WPS flaw, I would still think it would be 
detected by wash.

7. Paste the output from Reaver below.

wash lists other APs as normal, just nothing for this particular one.

reaver output:

[+] Switching mon0 to channel 1
[+] Waiting for beacon from 00:26:41:xx:xx:xx
[+] Associated with 00:26:41:xx:xx:xx (ESSID: Name)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
^C
[+] Nothing done, nothing to save.

I have successfully tested reaver and wash on 2 different APs (verizon & 
netgear), however, this old motorola does not get detected by wash. wash picks 
up my other APs and others in the area. airodump has no problem seeing the 
motorola AP.

Original issue reported on code.google.com by kdela...@gmail.com on 6 Sep 2012 at 2:33