You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 6, 2021. It is now read-only.
This could be a problem if the server wont remember that it launched a DoS attack on a certain wireless point using a certain interface, and then we try to call another function on that same interface.
We should have a global kind of way of tracking EVERYTHING so that if an interface is busy, it can be marked as so and the option for disabling the running process should be there to, which means we need to track both the status of interfaces and their respective jobs. (wlan0 is ddosing, wlan1 is scanning, wlan2 is down, so on)