shunz1 / reaver-wps

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

Unable to associate #328

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

0. What version of Reaver are you using?  (Only defects against the latest
version will be considered.)
1.4
1. What operating system are you using (Linux is the only supported OS)?
Xubuntu 12.04
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?
DIfferent
4. What is the manufacturer and model # of the device you are trying to
crack?
Netgear wgr614
5. What is the entire command line string you are supplying to reaver?
default one, nothing changed
6. Please describe what you think the issue is.
Not supported driver
7. Paste the output from Reaver below.
[+] Waiting for beacon from {BSSID}
[+] Switching mon0 to channel 6
[!] WARNING: Failed to associate with {BSSID}
[!] WARNING: Failed to associate with {BSSID}
[!] WARNING: Failed to associate with {BSSID}

---Or switches between channel a lot and again spams
[!] WARNING: Failed to associate with {BSSID}
[!] WARNING: Failed to associate with {BSSID}
[!] WARNING: Failed to associate with {BSSID}

Original issue reported on code.google.com by hdbus...@gmail.com on 9 Jun 2012 at 4:40

GoogleCodeExporter commented 8 years ago
what is the entire command line string you are supplying to reaver?

eg reaver -i wlan0 -b "your bssid here" -vv

make sure you enter the right bssid or you get failed to associate.
you can get your bssid with airodump-ng

Original comment by dennis_n...@hotmail.com on 10 Jun 2012 at 7:12

GoogleCodeExporter commented 8 years ago
The command is correct, the BSSID is correct as well. I suspect that it might 
be the driver or it needs 100% signal strength...

Original comment by hdbus...@gmail.com on 13 Jun 2012 at 10:48