iwlwifi driver : WPS transaction failed (code: 0x4)

[GoogleCodeExporter]

i didn't find information for my card with this driver,

i am on fedora 16 64 bit, kernel 3.2.1, driver iwlwifi for Intel 6300N 

in previous kernels the old driver iwlagn was used with this card, not anymore 
and i have yet to see oher reports with this driver.

injection works, tested with aircrack-ng suite.

My probem is this error message turning in loop : 

[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x4), re-trying last pin

If you have advice or something i can do to help further debuging please let me 
know

Original issue reported on code.google.com by sheepdes...@gmail.com on 17 Jan 2012 at 10:53

[GoogleCodeExporter]

oh forgot to tell, i use last trunk

Original comment by sheepdes...@gmail.com on 17 Jan 2012 at 11:05

[GoogleCodeExporter]

This issue has cropped up before; try using the --win7 option. If that still 
doesn't work, please provide a pcap file of the failed attack.

Original comment by cheff...@tacnetsol.com on 17 Jan 2012 at 12:46

[GoogleCodeExporter]

--win7 did not solve the problem,
i have a pcap file but fail to find a way to attach it to this post... sent by 
mail

Original comment by sheepdes...@gmail.com on 17 Jan 2012 at 1:40

[GoogleCodeExporter]

I haven't gotten the email yet.

Original comment by cheff...@tacnetsol.com on 18 Jan 2012 at 1:00

[GoogleCodeExporter]

Soory, was sent to reaverwps@googlecode.com, i resent it to yours

Original comment by sheepdes...@gmail.com on 18 Jan 2012 at 8:47

[GoogleCodeExporter]

It looks like the error code in the AP's NACKs indicates a CRC failure, which 
should not happen. Though you can't always trust the error codes some vendors 
put in their NACKs.

It looks like this is a Buffalo router? I know they support AOSS, which from my 
understanding was supposed to be compatible with WPS, but I have not tested 
them myself. I suppose it's possible this may be a driver issue, but I doubt it 
considering the packets seem to be injected OK; I suspect it is more likely an 
AP issue. Do you have another AP you can test to see if you get the same 
problems?

Original comment by cheff...@tacnetsol.com on 18 Jan 2012 at 2:12

[GoogleCodeExporter]

I did a new attempt today with an other AP and th last release of reaver. On 
this new AP i get ann error 0x03 now . not the 0x04 from the last one

with and without --win7 the result is same :

# reaver -vv -b XXXXXXXXXXX --win7 -i mon0

Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner 
<cheffner@tacnetsol.com>

[+] Waiting for beacon from XXXXXXXXXXXXXXX
[+] Switching mon0 to channel 11
[+] Associated with XXXXXXXXXXXX(ESSID: XXXXXXXXXXXXX)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
[+] Trying pin 12345670

I redid the test on previous AP with this new releaase and on this AP i 
continue to have the 0x04 error

i mailed the pcap file of this new test

Original comment by sheepdes...@gmail.com on 23 Jan 2012 at 8:36

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

i also tried the  --no-nacks command but get the same result : looping 0x03 
errors

Original comment by sheepdes...@gmail.com on 23 Jan 2012 at 8:48

[GoogleCodeExporter]

Im having similar issues with the iwlwifi drivers. Injection definitely works 
cause I'm able to crack WEP no problem, but with reaver all I get is 
authentication errors and timeouts. Here are some of the messages

reaver -i mon0 -b 00:25:9C:42:6A:28 -vv -w -c 11 -f -N

[+] Switching mon0 to channel 11
[?] Restore previous session for 00:25:9C:42:6A:28? [n/Y] n
[+] Waiting for beacon from 00:25:9C:42:6A:28
[+] Associated with 00:25:9C:42:6A:28 (ESSID: Lab)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[!] 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
[!] WARNING: Receive timeout occurred
[+] 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 identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[!] WARNING: Failed to associate with 00:25:9C:42:6A:28 (ESSID: Lab)
[+] 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
[!] 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

Is it just incompatibility with these drivers?

Original comment by ben.of.a...@gmail.com on 2 Oct 2012 at 2:03

[GoogleCodeExporter]

I have the same issue with iwlwifi driver

Original comment by lazak...@gmail.com on 11 May 2015 at 5:37