-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
wifi.assoc appears to be broken #535
Comments
not sure i follow, when you executed
now, if that's the only visible AP in that moment, that's normal ... what was the output of wifi.show? from your own logs, i can see that only that AP was discovered:
so what did you exactly expect to happen? |
Sorry, I'll try to be more clear: the association request is never actually sent from the interface. I've confirmed this with Wireshark running on another machine. |
Additionally, if you run |
i'll try to test this but it's unlikely i will be able to reproduce as it works every time for me |
If there's any additional debug information I can provide, I'm willing to try anything. |
ooops, i was actually able to reproduce this, let's see if i can fix :D |
it appeared to be a bug i introduced recently, fixed now, will release as precompiled in a couple of weeks approximately |
Thanks very much! |
wifi.assoc appears to be broken. No packets are sent after the command is issued, and no APs are associated.
Environment
Please provide:
bettercap -version
).Go version if building from sources.
n/a
Command line arguments you are using.
root@kali:~# bettercap -iface wlan0 -debug
bettercap -debug ...
).Steps to Reproduce
wifi.recon on
and wait until at least one AP is discoveredwifi.assoc all
to attempt to associate and capture a PMKIDExpected behavior: I expected an association request to be sent and (maybe) a PMKID to be captured.
Actual behavior: The association request is not sent, and it seems to hang after the first attempt. No request is actually sent (that I can see, I ran Wireshark on another interface, and the bettercap interface does not send any traffic).
I've reproduced this issue on two laptops (with multiple different wifi adapters with different chipsets), and in a VMware Fusion VM with an Alfa AWUS036H attached.
--
♥ ANY INCOMPLETE REPORT WILL BE CLOSED RIGHT AWAY ♥
The text was updated successfully, but these errors were encountered: