-
Notifications
You must be signed in to change notification settings - Fork 405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error Code 0x02 #319
Comments
did you read the troubleshooting guide in the wiki ? |
Yeah I did. Did I miss something I should have figured out myself (sorry if I did)? The AP requests the identity of the client, and the client responds, then does an extended response when it does not see an answer from the AP. Then all of a sudden the AP sends a failure. I know from Stefan Viehböck's paper that we tell the AP that we are attempting to become the registrar (which I believe to be different than how a normal client would authenticate with WPS - they'd become the enrollee correct?). Does the fact that the AP responds with a failure right after we state we are the registrar mean that the AP does not support this method (and thus the attack)? I ensure a few times that the WPS PIN method was enabled on the AP. Thanks for your help! Just trying to figure out when I can discount WPS as a valid attack method, and when I should pursue it. |
reaver sends a NACK because it runs into the configured timeout. i guess you should try to set a higher timeout with the appropriate command line option |
Hey guys,
Not sure what this error code means...but I continually get it when trying different APs that I have enabled WPS on. The one from the output below is running WPS 1.0. I've tried letting Reaver associate, and I have tried using aireplay to do the association. Any insight into what the potential problem could be would be great. I am using an Alfa AWUS036H. I also have the Wireshark dumps available if needed but I couldn't glean any real issues from that either. Just the AP eventually sending an EAPOL Failure. Thanks!!
The text was updated successfully, but these errors were encountered: