-
Notifications
You must be signed in to change notification settings - Fork 402
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
Constant deauth in MacOS #275
Comments
some routers do that, i haven't yet figured out why. maybe try with another type? |
Have tried with several routers now, but the results are all the same. Most of the routers are running WPS version 2.0. Could this possibly be the cause? |
no, that's not related. maybe the mac driver adds some invalid stuff to the packets, causing the routers to force a deauth. apparently mac monitor drivers are pretty buggy, so far there's only one apple device known working, iirc macbook white (2004) which @DJDan owns |
I get the same type of response on linux but without So maybe the AP deauthenticate & disassociates the client after the very first authentication failure I have also tried sending aireplay-ng fake association before running reaver to no avail. My suggestion is that the many similar issues open are at most the same thing. |
could you sniff with a second antenna when you associate to the AP using wpa_supplicant or anything that works, and compare what they do differently ? |
When attempting to use Reaver on macOS:
I have tried moving closer to the router, too.
Are there any other mac compatible pieces of software that I can use to handle authentication? (aireplay-ng isn't supported, it seems)
The text was updated successfully, but these errors were encountered: