> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/hacking-wifi/wpa-wpa2-psk-network-attacks/client-disruption-tests.md). # Client Disruption Tests WPA/WPA2 client disruption and resilience tests. These pages group active wireless tests that can affect association, airtime, or client connectivity.


Targeted Deauthentication Attack	Validate client resilience with scoped deauthentication testing.	Targeted Deauthentication Attack
Global Deauthentication Attack - Broadcast MAC Address	Document broadcast deauthentication behavior and impact.	Global Deauthentication Attack - Broadcast MAC Address
CTS Frame Attack - Network Bandwidth Hijacking	Analyze CTS control frames and medium reservation abuse.	CTS Frame Attack - Network Bandwidth Hijacking
Beacon Flood Mode Attack	Assess fabricated beacon broadcasts in a test network.	Beacon Flood Mode Attack
Disassociation Amok Mode Attack	Test disassociation behavior against approved client devices.	Disassociation Amok Mode Attack
Michael Shutdown Exploitation - Remote Router Shutdown	Assess legacy TKIP countermeasure behavior and router stability.	Michael Shutdown Exploitation - Remote Router Shutdown

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hacking-notes.jord4n.pro/hacking-wifi/wpa-wpa2-psk-network-attacks/client-disruption-tests.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

:bolt:

Targeted Deauthentication Attack

:tower-broadcast:

Global Deauthentication Attack - Broadcast MAC Address

:tower-broadcast:

CTS Frame Attack - Network Bandwidth Hijacking

:signal:

Beacon Flood Mode Attack

:link-slash:

Disassociation Amok Mode Attack

:power-off:

Michael Shutdown Exploitation - Remote Router Shutdown