-
```
What steps will reproduce the problem?
1. Deauthentication not work
What is the expected output? What do you see instead?
Couldn't determine current channel for mon0, you should either force the…
-
```
What steps will reproduce the problem?
1. Deauthentication not work
What is the expected output? What do you see instead?
Couldn't determine current channel for mon0, you should either force the…
-
```
What steps will reproduce the problem?
1. Deauthentication not work
What is the expected output? What do you see instead?
Couldn't determine current channel for mon0, you should either force the…
-
```
What steps will reproduce the problem?
1. Deauthentication not work
What is the expected output? What do you see instead?
Couldn't determine current channel for mon0, you should either force the…
-
```
What steps will reproduce the problem?
1. Deauthentication not work
What is the expected output? What do you see instead?
Couldn't determine current channel for mon0, you should either force the…
-
```
What steps will reproduce the problem?
1. Deauthentication not work
What is the expected output? What do you see instead?
Couldn't determine current channel for mon0, you should either force the…
-
```
What steps will reproduce the problem?
1. Deauthentication not work
What is the expected output? What do you see instead?
Couldn't determine current channel for mon0, you should either force the…
-
```
What steps will reproduce the problem?
1. Deauthentication not work
What is the expected output? What do you see instead?
Couldn't determine current channel for mon0, you should either force the…
-
In the future, you can add features such as:
- PMKID capture
- WPA/WPA2 handshake capture and parsing
- Deauthentication attacks using various methods
- Formatting captured traffic into PCAP for…
-
**Describe the bug**
The deauthentication process is not consistent when used with local-connector (default). On 10 attempts, I have seen 1 attempt to succeed.
**To Reproduce**
Steps to reproduc…