search

TomSlayer / reaver-wps

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

Failed to associate with bssid #43

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
This is the latest svn ver as of writing!
compiled with all known pre reqs on backtrack 4r2

What steps will reproduce the problem?
1. run reaver with "reaver -i mon0 -b (a "bssid") -vv  
2. did not shutdown possible conflicting programs? 
3. is in monitor mode
4. attempted multiple signal strengths on multiple test routers; ddwrt netgear, 
att, netgear, linksys
5. I'm using a alfa usb card; ralink rt2870/3070 rt2800ush on phy0 / wlan0, 
mon0 and mon1
9i'm not sure of the supported cards atm please post this to wiki
(Rechecked and some report not working I'm reporting it does not)

What is the expected output? What do you see instead?
works?
the program to begin cracking pin.
then successful retreival of pin

What version of the product are you using? On what operating system?
absolute latest!

Please provide any additional information below.

the pids of the programs to shutdown in a list would be a nice addition to the 
script if not already present.

a mac changer.

can we add this to wifite?!?!?!?! That would be awesome!!!!

Original issue reported on code.google.com by TomNever...@gmail.com on 1 Jan 2012 at 5:08

GoogleCodeExporter commented 8 years ago 
What are you trying to tell us? I don't comprehend.

Post a snippet of the cli output please.

Original comment by basti.me...@googlemail.com on 1 Jan 2012 at 6:28

GoogleCodeExporter commented 8 years ago 
I am confirming that the rtl2800 USB Alfa is incompatible, as well as 
requesting features.

Original comment by TomNever...@gmail.com on 1 Jan 2012 at 8:04

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
What about Intel Link 5100 cards? Monitor mode and injection work on these, but 
I do get the failed to associate with BSSID warning.

It works if I attempt to launch Reaver while being connected to the BSSID 
through legit means. The AP locks down after a number of attempts, meaning it 
kind of works except I can't be sure because my AP, although WPS enabled with a 
PIN code I know, sends me NACK packets when Reaver sends the correct key 
(through --pin). Shouldn't happen, but it might be due to the AP rather than 
Intel 5100 card so it doesn't seem to be the same issue as the "failed to 
associate" one.

I am using Backtrack 5 R1 and Reaver 1.2 r35 and the AP is a recent Sagem.

Original comment by b1957...@nwldx.com on 2 Jan 2012 at 12:05

GoogleCodeExporter commented 8 years ago 
Hello all , i have the same issue with backtrack 5 with an alfa card rtl ,8187l 
chipset

I tried with the -vv at the end and its the same thing ....

Hope to try it working soon :D

Original comment by danny_pa...@hotmail.com on 2 Jan 2012 at 12:10

Attachments:

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
By the way, not sure if it's of any importance but my AP is set to WPA2 AES.
Also the UUID is not the same as some Sagem ID that seems to be used inside 
packets, which is UUID + 3 (i.e. XX:XX:XX:XX:XX:(XX+3) ).

And finally, my failed to associate messages are less spammy than Danny's 
screenshot above. I do use -vv. I get timeouts, out of order packets and the 
occasional PIN code attempt (though Reaver always tests the same PIN, meaning 
is probably didn't get through). I get ONE "accociated with BSSID" at the very 
beginning followed instantly by a small bunch of "failed to associate" and all 
the mess described above.

Original comment by b1957...@nwldx.com on 2 Jan 2012 at 12:18

GoogleCodeExporter commented 8 years ago 
@Tom, you mentioned "varying signal strengths", but didn't give the signal 
strengths. Usually you get the failed association warnings when you have low 
signal strength and/or high interference. This could also be caused by MAC 
filtering as well.

@b1957946, WPA,WPA2,TKIP,AES, it's all the same since WPS is separate from WPA. 

Hard for me to trouble shoot these types of bugs without pcaps...

Original comment by cheff...@tacnetsol.com on 2 Jan 2012 at 1:07

GoogleCodeExporter commented 8 years ago 
max "on top of the router?"
medium " somewhere in-between at three points, thus med, then +/- 5 10 and 15 
respectively with and without walls
low " as far away as it can be seen by 1 bar but not all the way"

I have gotten it to "connect"? yet it always fails to connect or I get a 
command line error. (this is probably my fault as I reset it on a live usb 
several times)

Unfortunately for me all three of my wifi cards are rtl 2800 based :(
(at least for my tablet {TC1100} and others don't work as my slot wont work 
with the micro? or mini ones. 

I'll see if I can find another one and see if it is my fault?

Can we have an official build up so I can confirm if it is my card?

Original comment by TomNever...@gmail.com on 2 Jan 2012 at 1:42

GoogleCodeExporter commented 8 years ago 
Well if you're on top of the router then you shouldn't have any issues 
associating unless there's MAC filtering involved. 

I don't have a rtl2800 card, but I have heard mixed results: some people say 
the rtl2800usb drivers work fine, others report issues. Can you provide a pcap 
file of the wireless traffic while Reaver is attempting to associate?

Original comment by cheff...@tacnetsol.com on 2 Jan 2012 at 3:27

GoogleCodeExporter commented 8 years ago 
Issue 47 has been merged into this issue.

Original comment by cheff...@tacnetsol.com on 2 Jan 2012 at 1:28

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I don't have a pcap file, I could get one maybe later but I'd have to sanitize 
it before posting... if someone else could throw the pcap instead, that'd be 
appreciated :)

I described the issue above, but wanted to add that my card Intel Wireless Link 
5100 is using iwlagn driver.

Original comment by b1957...@nwldx.com on 2 Jan 2012 at 9:30

GoogleCodeExporter commented 8 years ago 
I am also using the Intel Wireless Link 5100 with iwlagn driver and am 
experiencing the same problems.

Original comment by xcellera...@gmx.com on 2 Jan 2012 at 10:09

GoogleCodeExporter commented 8 years ago 
I am using the "Intel Corporation PRO/Wireless 4965" with the iwlagn driver, 
same issue.

Original comment by chbj...@googlemail.com on 2 Jan 2012 at 10:36

GoogleCodeExporter commented 8 years ago 
Intel 4965AGN   (iwl4965) confirmed not working (Ubuntu i386)

Original comment by andreas....@gmail.com on 2 Jan 2012 at 10:45

GoogleCodeExporter commented 8 years ago 
Is there anything to do on Reaver dev's part?

Or is it only solvable through either an update to iwlagn/iwl4965 drivers or 
replacing those drivers with other Intel drivers? (which I'm not sure exist)

Original comment by b1957...@nwldx.com on 2 Jan 2012 at 10:58

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I had similar problems on a Intel Centrino 6300  
http://code.google.com/p/reaver-wps/issues/detail?id=30

So in theory if wpa_supplicant can do it. Reaver will be able to do it.

I guess that as soon as dev's get their hands on a iwlagn with problems, and 
can reproduce, they'll fix it.

Original comment by gorilla....@gmail.com on 2 Jan 2012 at 11:58

GoogleCodeExporter commented 8 years ago 
Since everyone having this issue appears to be using iwl/rtl2800 drivers, this 
is probably a driver issue. I have had one report on the wiki that the iwlagn 
drivers worked (Intel Wireless WiFi Link 5300 card), and one report that the 
rt2800usb drivers worked, but all others using these drivers have reported 
problems.

I don't have any of these to test, so if this is a driver issue, like it 
sounds, there is probably not much we can do right now.

Original comment by cheff...@tacnetsol.com on 2 Jan 2012 at 11:59

GoogleCodeExporter commented 8 years ago 
Just confirming, same issue here with an Intel Centrino Advanced-N 6230 (using 
iwlagn) - does not work, cycles over and over failed to assoc and timeouts.

Original comment by rolandd...@gmail.com on 3 Jan 2012 at 6:41

GoogleCodeExporter commented 8 years ago 
Hello there,
i just wanted to report that my emea intel pro wirless 6300 works using iwlagn.
Atleast that was the case for a Dlink dir 615 router. 
Had problems assosiating to a belkin router though. 
Can post a pcap file of the successful attack in the evening when i get home.

Original comment by menges.j...@gmail.com on 3 Jan 2012 at 11:12

GoogleCodeExporter commented 8 years ago 
same problem ubuntu 10.04 64 bit Atheros ath9k

Original comment by Str.Joha...@gmail.com on 3 Jan 2012 at 12:08

GoogleCodeExporter commented 8 years ago 
the same with my netgear WG111v3!Failed to associate with..!is this a wireless 
card problem?shall we expect an update?

Original comment by manthos....@gmail.com on 3 Jan 2012 at 12:48

GoogleCodeExporter commented 8 years ago 
Same problem with a RT3070L chipset.

Original comment by he...@electricman.se on 3 Jan 2012 at 1:31

GoogleCodeExporter commented 8 years ago 
This sounds like a card-specific issue (although Johannes, ath9k should work). 
I'll add these drivers to our unsupported list on the wiki, but we probably 
won't be issuing any updates to support new cards anytime soon.

Original comment by cheff...@tacnetsol.com on 3 Jan 2012 at 2:08

GoogleCodeExporter commented 8 years ago 
Intel 3945 not working (Same results as you guys)

Original comment by kalask...@gmail.com on 4 Jan 2012 at 10:55

GoogleCodeExporter commented 8 years ago 
Same here, using Alfa awus036h with Backtrack 5 r1 and getting failed to 
associate Error while using reaver 1.3

Original comment by ndab...@gmail.com on 4 Jan 2012 at 11:17

GoogleCodeExporter commented 8 years ago 
ndabbot, the Alfa should work with BT5. If you can't associate, you either need 
to get a better signal from the AP, or your card is not in monitor mode (or 
there is MAC filtering on the AP, but this is rare).

Original comment by cheff...@tacnetsol.com on 4 Jan 2012 at 1:03

GoogleCodeExporter commented 8 years ago 
anything new on this issue?i'm using awus036h now and have the same problem?

Original comment by manthos....@gmail.com on 4 Jan 2012 at 4:36

GoogleCodeExporter commented 8 years ago 
which driver do you use?

Original comment by hurenhan...@googlemail.com on 4 Jan 2012 at 4:44

GoogleCodeExporter commented 8 years ago 
i am updating and install them now!i let you know later!is this a driver 
problem?i
thinks is RTL8187L

Original comment by manthos....@gmail.com on 4 Jan 2012 at 4:56

GoogleCodeExporter commented 8 years ago 
I'm using a awus036h and also seeing this problem using both BT4 and 5.

Original comment by bdee...@gmail.com on 5 Jan 2012 at 12:42

GoogleCodeExporter commented 8 years ago 
I can also confirm that this issue is occurring with 2 RTL8187L cards, the Alfa 
awus036h and Netgear WG111 v3.

Simply will not associate, the power to the AP is -36 dB. Also getting a "AP 
Limiting Error", but I assume that is a separate issue  all together. I will 
try the Alfa again tomorrow with a Yagi antenna to ensure the power is not an 
issue, although I should not need it regardless for this range/interference.

Original comment by gethackedbro@gmail.com on 5 Jan 2012 at 8:16

GoogleCodeExporter commented 8 years ago 
Try associating with aireplay and then use reaver with --no-associate

Examples:

aireplay-ng mon0 --fakeauth 600 -e Livebox-XXXX -a XX:XX:XX:XX:XX:XX -h 
YY:YY:YY:YY:YY:YY

I've also used: 

aireplay-ng -1 0 -a 14:XX:XX:XX:XX:XX:XX -h YY:YY:YY:YY:YY:YY mon0

Original comment by bdee...@gmail.com on 5 Jan 2012 at 8:41

GoogleCodeExporter commented 8 years ago 
did you fix it?how you use reaver with --no-associate?i tried 3 different 
wireless adpters and get the same!the last was TL-WNT722N!

Original comment by manthos....@gmail.com on 5 Jan 2012 at 12:56

GoogleCodeExporter commented 8 years ago 
@gethackedbro: If you are getting the rate limiting warning, then you did 
associate. The rate limiting error indicates that the AP has locked WPS (this 
may be temporary or permanent, depends on the AP).

Most of these issues have been found to be either driver, environment or user 
related problems. We're talking to the aircrack-ng team and hopefully reaver 
will become part of their tool suite, which means it will use their 
injection/capture libraries, so any drivers that work with aircrack will be 
supported at that point.

Original comment by cheff...@tacnetsol.com on 5 Jan 2012 at 5:31

GoogleCodeExporter commented 8 years ago 
Make sure no other processes (such as dhclient) are active on the interface.
This caused some problems.

Original comment by Diego.Be...@gmail.com on 7 Jan 2012 at 4:04

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Ok, so I hope I have some new info to clear things a bit.

I've always used iwlagn on a 5100 with BT5 and initially it worked. With newer 
versions I had problems and thought it's AP specific UNTIL I went back to my 
successfully owned cisco AP and couldn't even retrieve with -p specified.

So, r34 works on iwlagn. 1.3 does not, it keeps trying a specified (correct) 
pin forever and skips over it (12345670) in crack mode. Just keeps trying pins.

Should have paid attention, the responsible change is between r34 and r45.

Original comment by efs...@gmail.com on 8 Jan 2012 at 7:21

GoogleCodeExporter commented 8 years ago 
I am using Reaver 1.4 in Backtrack 5 R1. Using my Att 2wire as a target I used 
the following cmd: reaver -i mon0 -b xx:xx:xx:xx:xx:xx -vv

I also keep getting the "Failed to associate" message.

Please help

Original comment by plasma...@gmail.com on 23 Jan 2012 at 5:19

GoogleCodeExporter commented 8 years ago 
Sorry forgot to add I have a Alfa Awus036h on mon0

Original comment by plasma...@gmail.com on 23 Jan 2012 at 5:22

GoogleCodeExporter commented 8 years ago 
@ cheff...@tacnetsol.com.. Thank you so much, your suggestion worked. It was 
the drivers.  

rt2800usb drivers for my Alfa card worked like a charm
http://www.backtrack-linux.org/wiki/index.php/Wireless_Drivers

Original comment by MarmM...@gmail.com on 20 Feb 2012 at 4:09

GoogleCodeExporter commented 8 years ago 
Same problem with ath9k in ubuntu 11.04. Note that it does associate, and then 
it fails to later. Here's an example output:

[+] 7.08% complete @ 2012-02-22 23:06:15 (9 seconds/pin)
[+] 7.09% complete @ 2012-02-22 23:06:33 (9 seconds/pin)
[+] 7.09% complete @ 2012-02-22 23:07:01 (10 seconds/pin)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[+] 7.13% complete @ 2012-02-22 23:08:26 (10 seconds/pin)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[+] 7.16% complete @ 2012-02-22 23:16:32 (10 seconds/pin)
[+] 7.16% complete @ 2012-02-22 23:17:00 (10 seconds/pin)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
...
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[+] 7.18% complete @ 2012-02-22 23:55:54 (13 seconds/pin)
[+] 7.18% complete @ 2012-02-22 23:56:07 (13 seconds/pin)
[+] 7.18% complete @ 2012-02-22 23:56:26 (13 seconds/pin)
[+] 7.18% complete @ 2012-02-22 23:56:49 (13 seconds/pin)
[+] 7.18% complete @ 2012-02-22 23:57:17 (13 seconds/pin)
[+] 7.18% complete @ 2012-02-22 23:57:48 (13 seconds/pin)
[+] 7.18% complete @ 2012-02-22 23:58:17 (13 seconds/pin)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[+] 7.18% complete @ 2012-02-23 00:02:25 (14 seconds/pin)
[+] 7.18% complete @ 2012-02-23 00:02:57 (14 seconds/pin)
[+] 7.18% complete @ 2012-02-23 00:03:29 (14 seconds/pin)
[+] 7.18% complete @ 2012-02-23 00:04:01 (14 seconds/pin)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
...
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[+] 7.18% complete @ 2012-02-23 00:24:33 (15 seconds/pin)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
...
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[+] 7.18% complete @ 2012-02-23 00:47:44 (17 seconds/pin)
[+] 7.18% complete @ 2012-02-23 00:48:03 (17 seconds/pin)
[+] 7.18% complete @ 2012-02-23 00:48:34 (17 seconds/pin)
[+] 7.18% complete @ 2012-02-23 00:49:06 (17 seconds/pin)
[+] 7.18% complete @ 2012-02-23 00:49:37 (17 seconds/pin)
[+] 7.18% complete @ 2012-02-23 00:50:08 (17 seconds/pin)
[+] 7.18% complete @ 2012-02-23 00:50:40 (17 seconds/pin)
[+] 7.18% complete @ 2012-02-23 00:51:11 (17 seconds/pin)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
[!] WARNING: Failed to associate with 00:25:9C:32:19:E7 (ESSID: IHTFP)
...

Also note that the status report is growing. It starts off at 3 seconds/pin and 
grows to 17 seconds / pin.

Original comment by josh.bia...@gmail.com on 23 Feb 2012 at 11:52

GoogleCodeExporter commented 8 years ago 
Same issue here.

INTEL 3945ABG - Driver: iwl3945

[!] WARNING: Failed to associate with FC:75:16:AE:FC:24 (ESSID: TALKTALK-AEFC)

I tried fake associate using aireplay as someone suggested and then ran reaver 
with --no-associate

I now get 
[+] Waiting for beacon from FC:75:16:AE:FC:24
[+] Associated with FC:75:16:AE:FC:24 (ESSID: TALKTALK-AEFC)

And thats it, nothing else happens, it freezes here.

there is NO MAC filtering and I have very strong signal strength.

Any ideas?

Original comment by pulseh...@googlemail.com on 25 Feb 2012 at 1:22

GoogleCodeExporter commented 8 years ago 
try with reaver -i mon0 -c (channel) -b (bssid) -vv --no-associate

it will be works.

Original comment by chlwlal...@gmail.com on 13 Apr 2013 at 11:13