Hi ee10.
No it isn't possble. Searching, comparing, ignoring ESSIDs costs too much cpu cycles. To went into an allready initiated authentication process we must be extreme fast (faster than the ap!).
But there is a build in automatic. If we retrieved a M2 from a client, matching to our M1, wlandump-ng (bleeding git) stops answering this client (in this case we use the mac for this session).
but keep in mind:
- many clients use random generated mac's
- wlandump-ng use random generated mac'c
that means:
if such a client restarts or wlandump-ng restarts, we got new random generated mac's
No it isn't possble. Searching, comparing, ignoring ESSIDs costs too much cpu cycles. To went into an allready initiated authentication process we must be extreme fast (faster than the ap!).
But there is a build in automatic. If we retrieved a M2 from a client, matching to our M1, wlandump-ng (bleeding git) stops answering this client (in this case we use the mac for this session).
but keep in mind:
- many clients use random generated mac's
- wlandump-ng use random generated mac'c
that means:
if such a client restarts or wlandump-ng restarts, we got new random generated mac's