Hacker Wiki

Hacking The Planet since 2004

User Tools

Site Tools

You are here: start » aircrack-ng_deauthentication
aircrack-ng_deauthentication

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
aircrack-ng_deauthentication [2019/03/21 00:24] – created hacktheplanetaircrack-ng_deauthentication [2024/09/04 18:20] (current) – external edit 127.0.0.1
Line 49: Line 49:
   * You will notice that the number in the example above is lower then 64 which is the number of packets sent.  It is not unusual to lose a few packets.  Conversely, if the client was actively communicating at the time, the counts could be greater then 64.   * You will notice that the number in the example above is lower then 64 which is the number of packets sent.  It is not unusual to lose a few packets.  Conversely, if the client was actively communicating at the time, the counts could be greater then 64.
   * How do you use this information?  This gives you a good indication if the client and or AP heard the packets you sent.  A zero value definitely tells the client and/or AP did not hear your packets.  Very low values likely indicate you are quite a distance and the  signal strength is poor.   * How do you use this information?  This gives you a good indication if the client and or AP heard the packets you sent.  A zero value definitely tells the client and/or AP did not hear your packets.  Very low values likely indicate you are quite a distance and the  signal strength is poor.
 +
 +===== Usage Tips =====
 +
 +It is usually more effective to target a specific station using the -c parameter.
 +
 +The deauthentication packets are sent directly from your PC to the clients.  So you must be physically close enough to the clients for your wireless card transmissions to reach them.
 +
 +
 +===== Usage Troubleshooting =====
 +
 +===== Why does deauthentication not work? =====
 +
 +There can be several reasons and one or more can affect you:
 +
 +  * You are physically too far away from the client(s).  You need enough transmit power for the packets to reach and be heard by the clients.  If you do a full packet capture, each packet sent to the client should result in an "ack" packet back.  This means the client heard the packet.  If there is no "ack" then likely it did not receive the packet.
 +  * Wireless cards work in particular modes such b, g, n and so on.  If your card is in a different mode then the client card there is good chance that the client will not be able to correctly receive your transmission.  See the previous item for confirming the client received the packet.
 +  * Some clients ignore broadcast deauthentications.  If this is the case, you will need to send a deauthentication directed at the particular client.
 +  * Clients may reconnect too fast for you to see that they had been disconnected.  If you do a full packet capture, you will be able to look for the reassociation packets in the capture to confirm deauthentication worked.
aircrack-ng_deauthentication.1553127868.txt.gz · Last modified: (external edit)