aircrack-ng 1.2 r2 and reaver router association issues?

Wondering if anyone else has run into this problem......

On netbook I have no issues using reaver. Works as expected.

On laptop with new aircrack (wlan1mon) reaver often outputs failed to associate, and gets stuck there. At first I thought it was random. But then as it happened more I tried to troubleshoot the problem a little.
Same equipment
Same target router
Same distances
Works as expected on netbook, and worked on laptop b4 upgrading aircrack-ng

So the error reaver gives is "failed to associate"....... Lucky reaver has the -A option (let outside program handle association)

If I use aireplay-ng 1st. and let it connect with the access point, then use reaver -A. It works as expected.

Wondering if anyone else noticed this?

setup:
awus036hna - atheros chipset
awus036h - realtek chipset
netbook - old aircrack
laptop - new aircrack

you can try using the mac of netbook in laptop

If u mean switch wifi usb between laptop and netbook, then yes tried it.

I even can boot the laptop with usb thumb drive that has old version aircrack and it will have no association issues. Only variable seems new Aircrack-ng / airmon-ng.....
but until some else has issue, might be something I'm doing wrong.

Interestingly, until two days ago I had always run the laptop with a kali persistent usb. Upgraded Aircrack-ng on that usb and started having association problems. Anyway decided to steal some hdd space from the windows installation, and install kali on hdd of laptop. So have clean install on laptop harddrive now. Kali comes with new aircrack by default. Having the same problem.

Same issue here, decided to give it a run after i read this post, and have tested with all reaver versions from 1.3 on kali. And on openwrt ar71xx platforms, new aircrack somehow interferes, but association will eventually fail or succeed but after 2+ minutes or so. But if i revert back to aircrack 1.2 rc1 or even 1.1, reboot, then it all works fine, and with the use of airmon-zc.

i will be further investigating the issue.

Ok great, I'm not nuts. Hope u figure something out......

Can u post the revert steps please.

although i did not noticed association problems, something seems to be out-of-wack.

same hardware, same reaver 1.4, different Kali versions.

Test1

Kali 1.0.7

Code:

root@kali:~# reaver -i mon0 -c 11 -b 90:F6:52:XX:XX:XX -vv Reaver v1.4 WiFi Protected Setup Attack Tool Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <[email protected]> [+] Switching mon0 to channel 11 [+] Waiting for beacon from 90:F6:52:XX:XX:XX [+] Associated with 90:F6:52:XX:XX:XX (ESSID: XX) [+] Trying pin 12345670 [+] Sending EAPOL START request [+] 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 [+] Trying pin 12345670 [+] Sending EAPOL START request [+] Received identity request [+] Sending identity response [+] Received M1 message [+] Sending M2 message [+] Received M3 message [+] Sending M4 message [+] Received WSC NACK [+] Sending WSC NACK [+] Trying pin 00005678 [+] Sending EAPOL START request [+] Received identity request [+] Sending identity response [+] Received M1 message [+] Sending M2 message [+] Received M3 message [+] Sending M4 message [+] Received WSC NACK [+] Sending WSC NACK [+] Trying pin 01235678 [+] Sending EAPOL START request [+] Received identity request [+] Sending identity response [+] Received M1 message [+] Sending M2 message [+] Received M3 message [+] Sending M4 message [+] Received WSC NACK [+] Sending WSC NACK [+] Trying pin 11115670 [+] Sending EAPOL START request [+] Received identity request [+] Sending identity response [+] Session saved.

wee! works!!

Kali 1.1.0a updated

Code:

root@Linksys:~# reaver -i wlan1mon -c 11 -b 90:F6:52:XX:XX:XX -vv Reaver v1.4 WiFi Protected Setup Attack Tool Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <[email protected]> [+] Switching wlan1mon to channel 11 [+] Waiting for beacon from 90:F6:52:XX:XX:XX [+] Associated with 90:F6:52:XX:XX:XX (ESSID: XX) [+] Trying pin 12345670 [+] Sending EAPOL START request [+] 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 [+] Trying pin 12345670 [+] Sending EAPOL START request [+] Received M3 message [+] Sending WSC NACK [+] Sending WSC NACK [!] WPS transaction failed (code: 0x03), re-trying last pin [+] Trying pin 12345670 [+] 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 M1 message [+] Sending M2 message [+] Received M1 message [+] Sending WSC NACK [+] Sending WSC NACK [!] WPS transaction failed (code: 0x03), re-trying last pin [+] Trying pin 12345670 [+] Sending EAPOL START request [+] Received M3 message [+] Sending WSC NACK [+] Sending WSC NACK [!] WPS transaction failed (code: 0x03), re-trying last pin [+] Trying pin 12345670 [+] Sending EAPOL START request [+] Received identity request [+] Sending identity response [+] Received identity request [+] Sending identity response [+] Received M1 message [+] Sending M2 message [+] Received M3 message [+] Sending M4 message [+] Received M3 message [+] Sending WSC NACK [+] Sending WSC NACK [!] WPS transaction failed (code: 0x03), re-trying last pin [+] Trying pin 12345670 [+] Sending EAPOL START request [+] 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 [+] Nothing done, nothing to save. [+] 0.00% complete @ 2015-05-09 14:56:14 (0 seconds/pin) [+] Trying pin 12345670 [+] Sending EAPOL START request [+] Received M3 message [+] Sending WSC NACK [+] Sending WSC NACK [!] WPS transaction failed (code: 0x03), re-trying last pin [+] Nothing done, nothing to save.

no worki.

Test2

Kali 1.0.7

Code:

root@kali:~# reaver -i mon0 -c 1 -b 90:F6:52:XX:XX:XX -vv Reaver v1.4 WiFi Protected Setup Attack Tool Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <[email protected]> [+] Switching mon0 to channel 1 [+] Waiting for beacon from 90:F6:52:XX:XX:XX [+] Associated with 90:F6:52:XX:XX:XX (ESSID: Xxxxxxxxxx) [+] Trying pin 12345670 [+] Sending EAPOL START request [+] Received identity request [+] Sending identity response [+] Received M1 message [+] Sending M2 message [+] Received M3 message [+] Sending M4 message [+] Received WSC NACK [+] Sending WSC NACK [+] Trying pin 00005678 [+] Sending EAPOL START request [+] Received identity request [+] Sending identity response [+] Received identity request [+] Sending identity response [+] Received M1 message [+] Sending M2 message [+] Received M3 message [+] Sending M4 message [+] Received WSC NACK [+] Sending WSC NACK [+] Trying pin 01235678 [+] Sending EAPOL START request [+] Received identity request [+] Sending identity response [+] Received M1 message [+] Sending M2 message [+] Received M3 message [+] Sending M4 message [+] Received WSC NACK [+] Sending WSC NACK [+] Trying pin 11115670

wee!!!

Kali 1.1.0a updated

Code:

root@Linksys:~# reaver -i wlan1mon -c 1 -b 90:F6:52:XX:XX:XX -vv Reaver v1.4 WiFi Protected Setup Attack Tool Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <[email protected]> [+] Switching wlan1mon to channel 1 [+] Waiting for beacon from 90:F6:52:XX:XX:XX [+] Associated with 90:F6:52:XX:XX:XX (ESSID: Xxxxxxxxxx) [+] 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 [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [+] Received identity request [+] Sending identity response [+] Received identity request [+] Sending identity response [+] Received M1 message [+] Sending M2 message [!] WARNING: Receive timeout occurred [+] Sending WSC NACK [!] WPS transaction failed (code: 0x02), re-trying last pin [+] Trying pin 12345670 [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [+] Nothing done, nothing to save.

no joy.

Very systematic approach......

One of the reasons my franken script beta testing is sporadic.

yes well, Slim might be able to run two (2) different version of Aircrack-ng internally (within FrankenScript_Portable), so that might solve some issues until they fix it.

And btw the Wash RSSI (AP signal strength) works in Kali 1.0.7. So I'm starting to wonder just how much was lost since then, and what for? Really, should we start a list of pros and cons? I'm all for progress, but it has to be exactly that, progress. If that progress brakes everything then I will naturally start asking questions. There might be older problems that were unresolved also, like the handshake capture issue, that seems to be more difficult then it was... so really I'm going to start asking why.