Closed hari01584 closed 2 years ago
I made the same pull request as you before, but the cause of this error is something else. It occurs when monitor mode is already enabled on an interface. If you run airmon and monitor mode is not enabled on the interface, the error does not occur. However, the monitor enabled interface is never set back to normal even when __aexit__ is called, which leads to the error the next time airmon is used.
@hari01584 @Tank-Missile This PR should come from develop branch, I changed the base and I'm merging it, thanks a lot! I'm curious as what your use case is, re-using the airmon object in the same session, thanks!
It was giving error in aexit of Airmon initilization, this was due to the fact that there was no separate Airmon ng monitor interface, instead it is same as original interface name, did some typo to reflect it, please review